I suggest you ...

Editor does not support direct XML encoding/decoding

When working with the editor, both source and converted value will shown encoded XML value. If your original string contains HTML or other "must be encoded" values readability is difficult and what you see can be weird.
Inside the editor, it would be nice to have original and converted values decoded and than encoded again while saving. This will improve user experience.
Suppose your original string is <strong>software<strong/>
Xlf file handle this correctly encoding it this way
&lt;strong&gt;software&lt;strong/&gt;
but in the editor you see the same ugly string.

36 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Mauro GhiniMauro Ghini shared this idea  ·   ·  Admin →

    4 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • PaoloPaolo commented  · 

        This is really a big issue! The automatic translations are unusable.

      • IKstraXIKstraX commented  · 

        It would be very useful, because if you have any markup character which are correctly encoded, it's harder to use automatic translation and if you translate strings manually you may accidentally delete one or more of those characters, making the string unreadable.
        Also using CDATA it doesn't works, showing also CDATA word inside the string to translate.

      • Philipp KursawePhilipp Kursawe commented  · 

        This is really, really annoying and makes me wonder if MSFT is using this tool themself event. Is this tool open source so we can quickly patch this?

      Feedback and Knowledge Base