Thanks!
I agree that flags do not correspond exactly to languages. They are
though widely used, and they do work a lot of the time. Your language
selector though looks more professional, and it doesn't have the
problems that flags have. We have not had the problem before, but now
that we do, I think that we should change to yours.
+1 on making the change.
We have a do-ocracy which means that 'doer decides' in a lot of cases
where it is not all that clear what to do. So if you want to make the
change now, you can. However....
It would mean changing translation banners in a lot of places. See for
example where the German flag is used. Over 100 pages:
https://alphamanual.audacityteam.org/man/File:Flag_of_Germany_small.png
So I suggest that for now you only use your new template on your new
zh_CN pages. On the English version of the FAQ and on any other page
you translate, I suggest that for now you use both the flags and your
new template.
Later on we will look at finding a way to automate the update of
language selection banners to use your template so that it does not have
to be done by hand. That won't happen until after 2.2.1 is released.
How does that sound?
Thanks a lot for your work on getting the FAQ into Chinese, and for
working on the detail of flags to get it right. It's appreciated.
--James.
On 11/12/2017 3:49 AM, mkpoli wrote:
There is a try.
https://alphamanual.audacityteam.org/man/Template:I18n_box
mkpoli <[email protected]>于2017年11月10日周五 上午6:01写道：
This is an issue found when I'm translating FAQ.
*Apparently, languages, scripts and nations are not one-to-one
corresponding.*
e.g
1. 23 languages in India.
2. Simplified Chinese (script) in Standard Mandarin (Putonghua,
language) in mainland China
3. Traditional Chinese (script) in Standard Mandarin (Guoyu, language)
in Taiwan
So if mark a language as a national flag, it will risk confusing and
potential political problems.
*Should Audacity provide country-specified contents, so that it can use
flags?*
I don't think so. Audacity is a tool that can be used around the world
with no (or maybe a little?) confusion by area.
*What about marking them in English, like English, German, Chinese
(Simplified), Hebrew....etc.?*
It's better than flags, but not best, since:
1. If there is someone finding difficulty reading English, they may
also have problems finding the English names of their language,
2. It's unnecessary for an English speaker to know about those words,
if they want, they can go to Wikipedia.
3. It's unnecessary for a developer. They can draw an image of
multilingual stats by looking at codes and file structure.
*What is the best practice?*
See those links:
1. https://en.wikipedia.org/wiki/Main_Page
2.
http://www.flagsarenotlanguages.com/blog/best-practice-for-presenting-languages/
*How-to, or my advice.*
In Audacity wiki, current multilingual system is using links to the page
as flags, like this
- [[Image:Flag_of_Croatia_small.png|link=FAQ:About Audacity/hr|ČP:O
Audacityju]]
- [[Image:FrenchFlagSmall.png|link=FAQ:About Audacity/fr|FAQ : À
propos d'Audacity]]
- [[Image:Flag of Germany small.png|link=FAQ:About
Audacity/de|FAQ:Über Audacity]]
- [[Image:Flag_of_italy_small.png|link=FAQ:About
Audacity/it|FAQ:Circa Audacity]]
- [[Image:Flag_of_Portugal_small.png|link=FAQ:About
Audacity/pt|FAQ:Sobre o Audacity]]
- [[Image:Flag of Spain small.png|link=FAQ:About Audacity/es|FAQ:Sobre
Audacity]]
- [[Image:Flag of China small.png|link=FAQ:About
Audacity/zh_CN|FAQ:About Audacity]]
I think it is possible to batch processed to local names, directly.
Maybe something like a box like in Mediawiki (link:
https://www.mediawiki.org/wiki/Project:About).
Regards,
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-translation mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/audacity-translation
