• State Verified Answer
  • Replies 4 replies
  • Subscribers 64 subscribers
  • Views 4809 views
  • Users 0 members are here
Options

Escape character and unicode spaces not visible in Passolo

Markus Kaußen

Hey everybody, 

some Java properties contains an escape characters "\" in front of "=" or ":", e.g. "Designation\:".

In addition, a unicode space "\u0020" is part of the properties file.

When I add these files as source files, the escape character disappears in Passolo (and target file). The string \u0020 is replaced by a default space.

Coding settings are "Automatic recognition" and "Same as source file".

Any suggestions? Is it possible that these files are not Java valid and this is why Passolo is doing its thing?

Thanks Markus
Rate translation
×
Suggest better translation
×
  • 0
    There is not enough information to answer your question. Where does the escape character \ appear, in the key or in the value? You just stated an observation, but what is the problem?

    Same for \u0020. There is no difference between what you call the Unicode space and the default space. Which brings me to the question where the space appears in the value and what is the use case you are looking for.

    Unfortunately the structure of the Java properties files are not bijective and there are different valid methods to describe the same thing. A good source is docs.oracle.com/.../Properties.html

    Can you please add some more information and describe the problems that you face.
  • 0 in reply to Achim Herrmann
    Thanks, Achim for your reply.

    The escape character appears in the value. Also the unicode space.

    From our customer side, the "\u0020" must be kept in the target file. But it is not even visible for the translator because Passolo converts it to a simple space when reading the source file. I am with you: Theres no difference between \u0020 and a normal space and Passolo is doing it right. But is there a way to stopp the conversion for some unicode characters? Or must they be converted to in the source files to \\u0020?

    Same for "Designation\:"? Passolo "thinks" there is no need for escaping so it converts it to "Designation:". Right?
  • 0

    Regarding the escaped character in „Designation\:“ it is not Passolo that thinks that there is no need for escaping it, it is Oracle that has clearly documented:

     

    So again it would be helpful to get useful information about your clients use case as Oracle clearly documented that \ will be dropped before non-valid escape characters.

    Same with \u0020 where you confirmed that there is no difference to a real space. Passolo converts all \uXXXX sequences into the real Unicode characters so that translators don’t need to edit

    label=\u00C4nderungen werden in allen Datens\u00E4tzen ausgef\u00FChrt.

    and where you will never find matches in a TM.

    What should happen with

    label=This is a\u0020nice sentence.

    when it will be translated to

    label=Dies ist ja nun wirklich ein schönes Satz.

    Where do you expect the \u0020 to see?
  • 0 in reply to Achim Herrmann
    Thanks Achim for your help. Currently I do not know where these strings are used and why these characters must be available.

    But due to this is no Passolo issue, I will mark your reply as answer. Thank you for your help!