-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Am 18.07.2017 um 22:51 schrieb Marek Marczykowski-Górecki:
> On Mon, Jul 17, 2017 at 11:25:05PM +0200, Tobias Killer wrote:
>> Hello Andrew and Marek,
>
>> In this email, there are several questions and things to say.
>
>> I've sent an initial email to qubes-translation. You may join
>> this list if you like.
>
> Thanks!
>
>> The discussions on issues on GitHub concerning localization have
>> decisions sometimes, e.g. here [1], there is a decision of the
>> scheme for filenames and subdirectories. How "undoable" are such
>> decisions? May I change the decision? For example, in this given
>> issue #1333, I'd like to use another system: Keep filenames as
>> the original ones, but precede filepaths with a
>> language-and-country-dependent directory. When transforming all
>> the links on all website and documentation pages from absolute to
>> relative ones, it'll be much easier to maintain and translate.
>
> Generally most decisions are "undoable". But it isn't always wise
> to change them, because of the effort needed to redo all the places
> where decision was applied already.
I agree.
As I can see, the post [1] follows indeed my ideas, except for the
directory name scheme. I suggest to have both language and country in
the tag, e.g. en-US, en-GB etc.. I know, en-US and en-GB differ just
slightly, but there are other examples. For example, on the Transifex
website of Qubes OS [2], there are currently both Portuguese
(Portugal) and Portuguese (Brazil) listed (and I heard that they are
very different to each other). Looks like that the country really matters.
@Andrew: What language code scheme do you have in mind? It looks like
ISO 639-1, see this list: [3].
@Andrew: It's hard for me to find a norm that specifies language tags
in combination with country. These two look good for me: [4], [5].
What do you think about it?
> In case of filenames, such a change could be probably automated
> (at least in repository, not sure about transifex).
As far as I can see now (sorry, I didn't see it until now), Andrew's
post [1] says that the filenames shall be kept. So, not a deal.
@Andrew, is there a way anybody could help you doing all these tasks
mentioned in your post there?
>
>> I'd like to get access to Transifex such that I can upload and
>> download files.
>
> Not sure about upload, but you should be able to download them,
> no? AFAIR Michael (cc-ed) have better understanding on transifex
> settings.
You're right, I can download them (sorry, I used NoScript, that's why
I didn't see it before).
The filenames seem to be somewhat weird. I hope that thing related to
these filenames can be automated.
Currently, I can't upload. But this is not urgent, now.
>
>> If you and your team don't sign commits of files in languages
>> you can't read, will it be possible to provide multilingual
>> software?
>
> This is difficult question. I'd say the same rules as for
> documentation applies here too. I.e. we may provide other language
> versions translated by the community, but the most accurate one is
> English. This should be clearly stated in documentation, and
> probably also in such translated tools.
I agree.
> Technically, this is perfectly possible, because most (all?)
> localization frameworks support shipping translations in separate
> files.
Hopefully all do. I'll deal with the software localization later.
Tobias
[1]
https://github.com/QubesOS/qubes-issues/issues/1333#issuecomment-282525224
[2]
https://www.transifex.com/otf/qubes/
[3]
https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes
[4]
http://www.lingoes.net/en/translator/langcode.htm
[5]
http://www.i18nguy.com/unicode/language-identifiers.html
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEE9VOPt2yY9xS+XKzULaXvb25AsygFAllvyLwACgkQLaXvb25A
syjuhQ/9HCFXxxC944Hkg6p7KqkJDFguOgHbpgemt3DIqqCOxxnxutpdiXs6nJzc
jrFuhk6do3CAHU8R4WCeoNo67qczzz2ayPU4LGq3UPZhcaAMSKkOxwG8JO2pAu9e
Cvi/ZcXvfuZpCCyKPR5GwpRh7kzPkZG456bsqc27OC+ThmJXegGWeNEIvgSxWyj/
yDh3PfMfRzydQm82hKxEXram6vAdZoNeVFNjmbhyfrf0zV7ripETVVz6iaMfY4kD
mIR+aIjjOpybEsbbYeoqMNwy07qtm5HagqR6lKLuczLc7cEFKoy/TzuIYOigOrAO
lk6WaCguY07BwZyUeQmenz20F9nAeft8FR/pFZtviUFVDVfnzI2rOGeR62hM1msn
CSv3gJcmZFFE03r40z6e5y5TsbWR21FfEydDq4ykJJixhmoPAxmpiv+x5+RJ+9H5
cOhY1UCJsF7A0aEQcW8j09IDHwU6KtBrNiKt6cYykCuMci281MrvKbbX8PQrHMgH
qFnhPz8QHNWUyIP2ubyv5F7JorJpwQjaiFYsbUmw5oBUk18lPkktBPHdOlcOutpG
E/LuHJKAAndjwirLLWF0SJOLrszb6zqYT0XOhfiYLBC9K2jLR506lFz8SnoxeIP0
uTQ3ob+JBxStbl+RJqde7IKOl21hO+9LfHlB2+hHYa44DNQAb8k=
=w5om
-----END PGP SIGNATURE-----