When I open the PO file in Studio, it shows this:

So the code appears where the source text should appear, and actual translation source EN text appears on the translated section.  Is there way/function that I am unaware that can block this?  Also, I need to still block those untranslatable tags.  Can I do the setting in PO file?  

Another question... I was trying to block these tags, but after entering in the option, it still not being blocked.  Can you tell me what I can do?

Thanks!

Yuko

Try the Supertext PO file type instead of the SDL's built-in one... it has more options.
https://blog.supertext.ch/en/2016/05/po-file-type-for-trados/

Sure, I can send you the sample file.  Do you have an email address to where I can send the file to?

Let me know.

Thanks.

Yuko

Hi Yuko Baba,

In theory the PO filetype from Supertext should work, but it's failing for me in 2017 with an error message.  This is probably not surprising as the filetype was built for 2015 but I tested it there too and it also failed.

The setting you need for your file would be this one because your File has the source text (msgid) in the target slot (msgstr):

Perhaps Remy Blaettler will have some clue about the error message and comment on whether a 2017 version is forthcoming?

But in the meantime I also tested your file in POEdit and this opened the file but exactly the same as Studio with the default filter... although it did report a language error.

So, if the target text can replace the msgstr value because the msgid is really a developers string then you could use a regex based filetype for your file as it's pretty simple with only single lines (assuming your real ones are the same).  Then I get this:

I'd stress that this filetype is not suitable for all PO files, it's only good for the sample I looked at from you.  But perhaps this will help you for now?  I put the sample filetype here:

yuko_PO.zip

Regards

Paul

Hi Yuko Baba,

In theory the PO filetype from Supertext should work, but it's failing for me in 2017 with an error message.  This is probably not surprising as the filetype was built for 2015 but I tested it there too and it also failed.

The setting you need for your file would be this one because your File has the source text (msgid) in the target slot (msgstr):

Perhaps Remy Blaettler will have some clue about the error message and comment on whether a 2017 version is forthcoming?

But in the meantime I also tested your file in POEdit and this opened the file but exactly the same as Studio with the default filter... although it did report a language error.

So, if the target text can replace the msgstr value because the msgid is really a developers string then you could use a regex based filetype for your file as it's pretty simple with only single lines (assuming your real ones are the same).  Then I get this:

I'd stress that this filetype is not suitable for all PO files, it's only good for the sample I looked at from you.  But perhaps this will help you for now?  I put the sample filetype here:

yuko_PO.zip

Regards

Paul

Hi Paul,

Thank you.  Could you tell me where in Studio I can find the segment setting, so I can test and see if I can replace the target as source?  

Also, I am not too familiar how I can use the sample filetype you sent back to me.  Could you tell me how I can apply this to my project?

If nothing works, I guess I will still go to convert po to excel then translate the excel (block tags).

I am not sure why the setting is not blocking certain tags as I mentioned...  Could you please help me with that?

Thanks.

Yuko

Hi Yuko,

Unknown said:

Could you tell me where in Studio I can find the segment setting, so I can test and see if I can replace the target as source?  

You need to download and install both sdlplugin files provided for this app:

http://appstore.sdl.com/app/file-type-definition-for-po-extended/566/

Then you'll find the option here after installing:

To use the settings file I gave you go to the same Filetype Options only this time import the settings file here:

On your excel tagging, you just need a rule to specifically take out the placeables you show.  So maybe something like this:

<.+?>

Make sure you set it as a placeable and not a tag pair.

Regards

Paul