Hi,

You can try to remove this character and have your text translated in EXCEL

Copy your text in the first column in Excel, click on the A to select the column, click on top menu DATA , select Text to columns, select Delimited

then click next, remove the check mark on the TAB choice add one on the Other enter your | for separator

You will have now in A1 ( [AWAITING_AUTHORISATION]:Needs Authorisation) in B2 [AUTHORISATION_ADDED]:Authorisation Added ..

Click on the 1 to have the line selected, do ctrl-c, click on cell A2, click on top menu Home, icon past select transpose

If it word you can delete the line 1

 You can reuse the text to Columns again with : as separator

at the end in A1 you will have ( [AWAITING_AUTHORISATION]) and in B1 (Needs Authorisation) and save the file in XLSX

In Passolo you can use the excel parser. In the Properties of Passolo you will need to click on Options...

and specify your ID column to A and your source text column as B

If the translation is in column B

In excel

When your translation will be completed you can add again the | characters by

add in the column d1 =concat(A1,":",B1,"|")cut and past this in all lines

cut and past all the result in a notepad file and your will have the same format at then end.

good day

There is no problem to achieve this by adding a new break rule to the Default language in SRX that inserts breaks when the vertical bar character | appears.

Please check that segmentation is activated in the options of the Java source file and that the new break rule is correctly stored.

That's what I did. But it doesn't seem to save the new rule. If I open SRX again after creating and saving the rule, the rule is gone again.

I'm working on the latest version as well. No idea why the new rule is not saved.

Dear Michaela,

you could also create a Txt parser in Passolo, that extracts the texts very neatly, see my screenshot. Note the regular expressions in the screenshot.

Hope this helps,

Robert

It is possible to write a text file parsing rule with regular expressions but I would never recommend it to users. There are too many special use cases in Java Properties files that will cause problems when using the text file parser like

• Lines concatenated with \ cannot be imported properly
• Redaing lines containing Unicode escape sequences \uxxxx
• Writing translated files with Unicode escape sequences \uxxxx
• Writing translated files with placeholder where the apostrophe must be doubled

And the initial problem segmenting entries at the | character will remain.