-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Thank you, Martin, this makes sense now. (although Arabic (and Hebrew, and some others) is maybe an example we should treat with care - they write from right to left, and this could cause some layout problems... but without a translator, there's probably little danger...)
Maybe we should take the languages Inkscape already supports as the set to use? (although I still fear this *could* become a maintenance nightmare with outdated translations in languages only very few people would need - restriction to some core isn't necessarily a bad thing... but of course, we wouldn't push a volunteer away, who wants translate to some rare language)
Maren
Am 15.02.2015 um 19:44 schrieb Martin Owens:
Hi Maren
It would come into it's own when we have a new translator who wants to translate say arabic. We wouldn't have to edit the settings file in the repository and forward patch it, it's a very risky way to enable a new language.
Martin,
On 15 February 2015 at 10:48, Maren Hachmann <maren@...68...>
wrote:
Hi Martin,
why do we need more languages than we have translators? For the docs? For cmsrosetta? Or do we have many visitors who don't understand the page? Or for preventing further restarts, in case a translator for a new language comes along? We wouldn't have any translations... and no translators for them. Most of them would be English fallback anyway...? And would we be able to handle RTL languages?
Could you give us some cool use example for the additional languages?
Regards, Maren
Am 14.02.2015 um 23:30 schrieb Martin Owens:
Hey WebDevs,
Now that Maren has fixed the language selection issues we were having/ Both the redirect on missing pages and the error with news and search page urls with new languages.
We have the opportunity to configure a short admin side list of languages. This is more of a feature request/definition but it would work like this:
A list of all languages, their english names and their translated names (just in case they're missing from the core pot) a checkbox for if we want them to be hidden from the menu. We can do this where we want auto detection to pick a language, but not display every language possible in the menu.
(or we could have a 'more languages...' link at the bottom)
The service would still need restarting to take advantage of the new language, much in the same way as menu updates have to refresh the cache.
Thoughts?
Martin,
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media,
is your
hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and
more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media,
is your
hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more.
Take a
look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs