[Qt5-feedback] Translation in Qt5

[Konstantin Tokarev]

29.06.2011, 23:53, "David Faure" <faure at kde.org>:
> On Wednesday 29 June 2011, Konstantin Tokarev wrote:
>
>>  29.06.2011, 23:15, "David Faure" <faure at kde.org>;:
>>>  On Wednesday 29 June 2011, Konstantin Tokarev wrote:
>>>>   29.06.2011, 03:30, "John Layt" <jlayt at kde.org>;;:
>>>>>   * Qt Linguist is in "maintenace mode", no planned updates, other tools
>>>>>   are better
>>>>   What tools?
>>>  The large number of tools based on gettext, I suppose. Like lokalize,
>>>  poedit, gtranslator, and I presume there are commercial tools as well.
>>  IMHO, lokalize and poedit are nothing better than Linguist
>
> Let's not get into such a discussion, the main point isn't that anyway. The
> main point about tools, IMHO, is that for commercial Qt users in particular,
> it's much much easier to subcontract translations by giving po files to a
> translation company, they know that format, they have worked with it for
> years, than trying to find a translation company who has heard about .ts
> before, and who manages to use linguist instead of the tools they have much
> experience with.

I'm in doubt if commercial users which outsource localization to other companies
are vast majority of Qt users.

> I know that Qt has some conversion tools between ts and po, but still, I have
> heard this argument quite a few times when visiting customers: the non-
> standard format for translation files does not make things easy for them.
>
>>>>>   * In Qt5 should remove forced context from Qt to restore compatability
>>>>>   with all other translation systems.
>>>>   Automatic context is a great feature of Qt translation systm, please
>>>>  don't remove it.
>>>  What is great about it? IIRC it's typically set to a C++ classname, and
>>>  translators don't typically know these names at all.
>>  Linguist uses it, and it makes translation easier
>
> Easier how? How does a translator know what to do with
> VisitorPatternImplementationBackend as context?


OK, easier when used with piece of mind. Class which you have mentioned should
not contain translatable strings because it's something model-level.

-- 
Regards,
Konstantin