17 Mar
2020
17 Mar
'20
4:15 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi Slavek,
seem comments mixed below.
Cheers
Michele
--1. What is suitable for translating?
Although the keyword list seems reasonable, I have doubts about "Icon". The
icon name is often the same as the
application name. This could result in the icon name being translated inadvertently.
What is your opinion?
I had the same doubt when looking at the abakus PR you prepared. I don't think Icon
needs to be translated.
--2. How to structure translation templates?
If you worked in TWTW, you probably know that the translations here are structured into
two levels - project =>
component. Where the component corresponds to one particular translation template. We
used the projects for the
basic division - dependencies, main modules (individual projects), libraries,
applications.
The question is how to generate POT templates for desktop file translations? Here are
some fundamentally different
options:
a) Create a separate POT template for each desktop file => advantage - it will be very
clear, disadvantage - there
will be many new components. However, each with a small number of strings.
b) Incorporate desktop files translations as part of existing POT templates for
individual components
(applications) => advantage - there will be only a few new components, disadvantage -
there will be less clarity,
this may prevent correct translation of the strings in the desktop file if the same
string in another context is
used inside the application.
c) Merge templates of multiple desktop files into one common template => advantage -
no too many new components
arise, disadvantages same as for b) with higher risk of collision of identical strings
with different context.
As we discussed on IRC earlier, it seems option a) is the only viable one. Although I am
not in favor of having
hundreds of small .po files, that seems to be the only solution that allows for
context-dependent translation of the
same strings in different contexts.
--3. How to structure components for desktop file
translations?
If there will be a separate templates for translating desktop files, then there are two
possible ways to integrate
them into TWTW:
a) Add as additional components to existing projects => advantages - translations will
be close to the applications
to which they belong, disadvantages - the number of components in projects will
increase.
b) Create a separate project for all desktop file translations => advantages - no
increase in the number of
components in existing projects, disadvantages - some TWTW checks will not be able to be
applied because the
application and its desktop files will be different projects.
Option a)
--4. How to organize translation files in source git
repositories?
Currently, the organizing of the translation files is inconsistent. Therefore, it seems
appropriate to harmonize
the layout of directories with translations.
Here are a few of the variations used: + po/<lang>.po +
po/<lang>/<app>.po + translations/<lang>/<app>.po +
translations/<lang>/messages/<app>.po
For desktop file translations, all languages are required to be located in the same
directory, named in
accordance with the language. For example:
+ po/desktops/<desktop-name>.pot +
po/desktops/<desktop-name>/<lang>.po
Do you prefer the directory name "po" or "translations"? In this
directory, it seems to me a good breakdown by
purpose - "messages", "desktops", because this will allow in the
future to add "docs", "manpages". The structure
could look like this:
po/desktops/abakus.desktop.pot po/desktops/abakus.desktop/<lang>.po
po/messages/abakus.pot
po/messages/abakus/<lang>.po
What is your opinion?
How about this?
translations/desktop_files/pot/<all pot files of the module>
translations/desktop_files/<lang>/<all po files of the module for the
language>
translations/messages/pot/<all pot files of the module>
translations/messages/<lang>/<all po files of the module for the language>
Additional point mentioned in abakus PR: in the pot file we are losing the context of the
string, for example if it is
a GenericName or Name or anything else. Would be better to add as part of the comment for
each string.
Extra point: how about translation of strings in .ui files?
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEjhl1z5vbYB3YbFTiKnW3yore1c8FAl5wTuUACgkQKnW3yore
1c+t0Q//QwoV0iICO+CFKo5tsCOM7lD6Id8PBS+nC+w2L1besXRFPBqiv2vMiQBP
QhvtO1vLB3QhaWLoRak4sVz1clrumlNt/xDwIpXBOtcyMdcjLJUEtZRVLS2snfIc
OP+CAadmxL67fJFYh//BcaqvWs75MEWYhmGxMQ8FpQIKFMVDDQBsdJfsS9/gvGZq
NiBvXjKmCuzLE6R7RaWsY3815X9W9PKz1rrFplN1unI6Psq8o/WEdwnOehX5+akX
G5QLkepaZnY6QwRR1WrZUwdaJsWH0clsp7PaQV/cetyv1Udy0UfbWw8/Vk6O7Kkk
3kdVc+sMIT5I6y2lcbnaEvyHqwNPWvMIeOKMtPzctPjv/4D8QmIWY6zy9+N9BJj5
2yVwCrG9HvrYadJqdqujR//gmvVU8bEGLXvNE7oLefuQOJoDqZAwFR5GHeSaQAvg
kQ1zWFTQlRWr7KfIKDC9OSoJKPYUnfq+pR5pISiPbioFJyk9L2+HpzbxwrNcWDqW
ZaRr5slTJBnNQ9/5yhb8QTkwfKFbPATQsxaOU0VvsuUmkN3153ksZmJ5WVCVeUVy
gkY1EaZ5EUhYQT18einiY+ykoMsg6iu2Q1bc6X5wkjQfkOdCvMSA9gDec2vS49mr
i2EYgQOVs0uRLWiqZCD0ON3S9D5AvroR1SX2hxJefpn9JZgW284=
=6Ozh
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting