I agree. However, there are Gettext users/programmers who believe that msgctxt should only be used for context, and not for helpful comments. Helpful comments are then placed in the message header.
So personally I think OmT should display the entire message/string (including its individual headers) but make only the translatable text translatable.
But yes, support for msgctxt will be useful (it is likely to be used a lot more in future, replacing ugly hacks used by various projects to include helpful stuff in a place where a translator might see it).
-- Samuel/leuce
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: NO
I agree. However, there are Gettext users/programmers who believe that msgctxt should only be used for context, and not for helpful comments. Helpful comments are then placed in the message header.
So personally I think OmT should display the entire message/string (including its individual headers) but make only the translatable text translatable.
But yes, support for msgctxt will be useful (it is likely to be used a lot more in future, replacing ugly hacks used by various projects to include helpful stuff in a place where a translator might see it).
-- Samuel/leuce
context is now used for multiple translation support.
>context is now used for multiple translation support.
Couldn't it be added to the comment, too?
Didier
Currently it is added to the comments pane as
"Path: xxxxxx" (where xxxxxx is the context)
>Currently it is added to the comments pane as
>"Path: xxxxxx" (where xxxxxx is the context)
We can consider it is implemented and close it, then?
Didier
It does appear indeed in the Comment pane. I close as implemented.
Didier
Turns out that "msgctxt" is somehow recognized by OmegaT.
Last edit: Hb 2019-03-04