You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
prop2po (http://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/prop2po.html) produces a completely different po than serge when processing properties files
More specifically the comments are treated differently
What .properties flavor is serge using (translate toolkit has these flavors: flex, java, mozilla, java-utf8, skype, gaia, strings)?
To be even more specific to be a comment in serge it needs to start with #.comment=
We added our own comment prefixes to be able to specify not only comments, but also context for each string. Having said that, it makes sense to add support for any generic comments (comment lines that have no special prefix can be treated as simple comments). For backward compatibility, this feature will be turned off.
prop2po (http://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/prop2po.html) produces a completely different po than serge when processing properties files
More specifically the comments are treated differently
What .properties flavor is serge using (translate toolkit has these flavors: flex, java, mozilla, java-utf8, skype, gaia, strings)?
To be even more specific to be a comment in serge it needs to start with #.comment=
And looking at this document from the http://docs.oasis-open.org/xliff/v1.2/xliff-profile-java/xliff-profile-java-v1.2.html they also consider any properties comment as comments
The text was updated successfully, but these errors were encountered: