2009/9/17 Uwe Fischer <uwe.fisc...@sun.com>: > Hi Martin, > > I trust that Slovenians can make it happen! Don't give up, just re-use the > old translations wherever only spaces got added or removed. > Hello, Uwe,
There is only one Slovenian working on the translation of OOo, and that is me, since several versions already. :( > I will try to find the cause of the additional space characters inside long > xml constructs later today. > So, to answer my question, addition of a space after Option in that example is a mistake? Several changes like that occurred with m57. > You may translate or neglect the <emph>-->menuitem changes as you like. In > the final Help page that the user gets to see, there is no difference > between the two tags. Don't know what the translation syntax checker will > return, however. So, to answer my question - is the <emph> --> <menuitem change (that has already taken place with m57 and has been left in in m59) final and won't be reverted back in post-3.2 builds and those changes will not be made automatically in the localization teams' SDF files as discussed in this mailing list? Or do you expect translators to edit changes manually just for 3.2 - and then do the automatic stuff? The first option means we the translators have no choice but to start manually changing those strings, which can lead to errors etc. and a lot of manual work for 3.2, where deadlines are becoming questionable. The other option means that if we try to make 3.2 happen as fully localized versions our manual work will be almost in vain in regard to post-3.2 builds. Just trying to get the clear picture, so I can decide how to organize my schedule. Thanks, m. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
