W3C home > Mailing lists > Public > www-i18n-comments@w3.org > September 2014

Re: navigation-select

From: Richard Ishida <ishida@w3.org>
Date: Mon, 29 Sep 2014 12:12:44 +0100
Message-ID: <54293EAC.6000203@w3.org>
To: Gunnar Bittersmann <gunnar@bittersmann.de>
CC: www-i18n-comments@w3.org
Thanks for these suggestions. Sorry, as usual, for the delay (due to a 
panic to get Encoding to CR to the exclusion of almost everything else, 
then travel, then sickness, then catchup.)

On 27/08/2014 12:07, Gunnar Bittersmann wrote:
> IMHO, the bullet points under “Key disadvantages of using select …”
> should be reversed, “users cannot see or access the links straight away”
> being the most important, while font issues are not that much of a
> problem on today’s systems.


> »»
> <meta name="description" content="C I18N article: …" />
> ««
> It should be 'W3C' in the beginning of content attribute value.


> »»
> to provide in page links
> ««
> Shouldn’t this be spelled with hyphen?
> to provide in-page links


> The text graphic “☐☐☐ (Japanese)”
> http://www.w3.org/International/questions/images/select-no-glyphs.gif
> contains English text which is problematic for translations. I will
> attach a text graphic with “Japanese” translated into German to my
> translation, but other translators have not.
> So in translations it gives the wrong message, just like the sentence
> below states: “Note, also, that names in the language of the current
> page should really be translated for every page where they appear – if
> you leave them in English it may give the wrong message.”
> A solution would be a graphic with just the 3 empty boxes and the text
> put inline right behind:
> <blockquote><img …> (Japanese)</blockquote>
> (I wonder if blockquote was the appropriate mark-up here.)

Converted to figure.

> Or use Unicode characters for the 3 empty boxes. Either way, translators
> would translate “Japanese” as they should.

I converted to text, as you suggested.

> As I wrote on 2010-10-01 02:11+02:00:
>> Under “Ordering” there should be listed another option: by language
>> tags. Not only the very W3C i18n site uses this ordering, but also
>> Wikipedia. So it’s already known to a lot of users, hence might even be
>> best practise.

I added the following paragraph:

"This page and Wikipedia list language alternatives by (English) 
alphabetic order of the associated language tags. So, for example, 
German (de) comes before English (en), and Spanish (es) comes before 
French (fr). This assumes that the user can either find his language 
easily by scanning (which is the case for this page) or knows the tag 
for their language and can guess easily enough that that has been used 
for the ordering."

Good suggestions. Thanks.

Would you like to refactor your translation per the above changes and 
resend to me. I'll try to upload it quickly, once i get the new version.

Received on Monday, 29 September 2014 11:13:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:20:17 UTC