Probably easiest way is to handle a file like this as a regex filetype.  There's a really old post here that will be helpful:

Regards

Paul

Hello again, the filter is working but accents are coming out are converted: clé API' is converted to clé API'
which I solved by resaving the file in ANSI format. Thanks

However there is a strange thing happening: there is a difference between straight single quotes (') and curly single quotes - this seems not to be the same character

Regarding this thread: I am translating php from English to French. The file layout looks like below:

'zlec_Nazwa' => 'Time limit for complete',

The translated text 
'zlec_Nazwa' => 'Date d'échéance',

The problem is ' symbol in French text between d and échéance. This symbol destroys the coding because it closes the phrase. How can I  translate a php file in trados studio so that the generated translated file is properly created? Can you help please :)

First, you should use a typographic apostroph in French.

Second, it seems, that you should create a special file type for your php, where parts '...' => ' will be made untranslatable. Usint the regex text file type the opening pattern here would be ^'.+?' => ' and the closing pattern ',
This way when opening the file only "Time limit for complete" would be visible and nothing within this segment would break any phrases.

Karol Dobryniewski

If I understand you correctly, you are looking for a way to have a single quote in the php string. The answer is that you have to escape the single quote. The simple way would be to write \' instead of ', or to instruct Studio to do so. (https://stackoverflow.com/questions/6269188/how-do-i-escape-only-single-quotes)

However, one of the participants of the source mentioned this:

Replacing with ' should work. I don't think you can make Studio do this for you, you would have to do this with some kind of regex search and replace in Notepad++ or similar.

The HTML file types offer entity conversion, which is what you are looking for. Unfortunately, the HTML file types don't allow for regex to identify the translatable text.

You can make it work, but it depends a bit on how your actual source file looks:

It will initially look like this:

Then you can change the non-translatable text into tags using the data protection suite:

Nota bene that the MT results were odd and the tags were not generated correctly, I don't know why and don't have time to figure out, unfortunately.

You set in character conversion that you want the apostrophe character to be encoded as numeric unicode. The, after translation, you unprotect your files and generate target translations. The output looked like this for me:

Quite convoluted, but possible.

I would treat it as text file and post-process it, as stated above.

Daniel

Karol Dobryniewski

If I understand you correctly, you are looking for a way to have a single quote in the php string. The answer is that you have to escape the single quote. The simple way would be to write \' instead of ', or to instruct Studio to do so. (https://stackoverflow.com/questions/6269188/how-do-i-escape-only-single-quotes)

However, one of the participants of the source mentioned this:

Replacing with ' should work. I don't think you can make Studio do this for you, you would have to do this with some kind of regex search and replace in Notepad++ or similar.

The HTML file types offer entity conversion, which is what you are looking for. Unfortunately, the HTML file types don't allow for regex to identify the translatable text.

You can make it work, but it depends a bit on how your actual source file looks:

It will initially look like this:

Then you can change the non-translatable text into tags using the data protection suite:

Nota bene that the MT results were odd and the tags were not generated correctly, I don't know why and don't have time to figure out, unfortunately.

You set in character conversion that you want the apostrophe character to be encoded as numeric unicode. The, after translation, you unprotect your files and generate target translations. The output looked like this for me:

Quite convoluted, but possible.

I would treat it as text file and post-process it, as stated above.

Daniel