Hi Friedel, Thanks for your comments. Yes, I agree that it'd be the best way to switch the style from msgid_comment to msgctxt. I also confirmed that msgctxt works ok in OmegaT.
So now, I'd like to suggest to switch OO.o po files in sunvirtuallab to msgctxt. If there is any objection, I'm going to apply the new style from the next Pootle update. If you have any concern or comment, please let me know. Thanks for all your help, Aijin F Wolff 쓴 글: > > I think msgctxt might be the best way to go, except if some team really > wants to support some tool that doesn't yet support it well. From my > understanding, the current versions of OmegaT will already work better > with the msgctxt-type files, simply because the msgid will now always > just contain the text for translation. This should enable the normal > translation workflow of PO files in OmegaT, and should mean that the TM, > etc. should work properly. (Of course, there might still be issues more > generally about PO support, but at least it should be better than with > the msgid comments). Unless anybody objects, I think going with msgctxt > should be a good goal for just about everybody. I understand that Ain > (not Aijin:-) has also already migrated that way. > > I think it is also worthwhile noting that the msgid comment was > introduced by KDE before msgctxt existed, and now even the KDE project > does not use it anymore. Although the Translate Toolkit and Pootle > support it quite well, I think, most other tools that don't support it > yet, probably never will, as these type of files will probably gradually > disappear :-) > > Friedel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
