[Bug 471028] locale name should be hi instead of hi_IN

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=471028





--- Comment #5 from Jeff Fearn <jfearn@xxxxxxxxxx>  2008-11-11 18:01:37 EDT ---
(In reply to comment #4)
> (In reply to comment #3)
> > It makes language code format consistent across all languages since at the
> > minimum the two Chinese languages use 5 character codes.
> > 
> 
> But not every language has to use 5 character codes. Most of them don't have
> any variants and always will be just one language. 2 character codes are used
> for years, and it has never been problematic in any way.

He asked for a clear policy, always use 5 letter codes is clear, use 2 or 5
letter codes is less clear.

> > IMHO xx-YY for all languages is clear.
> > xx[-YY] is less clear.
> > 
> 
> But changing de facto standard (xx[_YY]) to something not used in any place
> except publican does not give you any benefits.

This has nothing to do with Publican, it's Fedora docs policy and it would make
sense to clarify this policy regardless of what tool chain is being used.

> It makes things even worse,
> because whole FLOSS world use 2 character codes (with exceptions like zh_CN or
> bn_IN, where it's really necessary), including glibc language tables!

This is the difference between producing translations for software and
translations for documentation.

The underscore should not be used for documentation translations since it is
not a valid language delimiter in XML or XHTML. The HYPHEN-MINUS is the only
valid delimiter in XML and XHTML. Using the underscore produces invalid XML and
XHTML.

See: http://www.w3.org/TR/REC-xml/#sec-lang-tag

The shell uses a different ISO standard for language delineation than is used
in XML and XHTML, publican handles this difference when producing desktop
documentation, I'm not sure what other tools chains do.

> > What happens if you have a xx language and later on someone adds a xx-YY
> > variant? I recently heard this happened to one project when es-MX was added and
> > es already existed.
> > 
> 
> Is this really a problem? In which way?

He asked for a clear policy, having mixed 2 and 5 letter codes for the same
language does not aid clarity.

> > My point being that xx[-YY] is more prone to confusion than always having
> > xx-YY.
> > 
> 
> From l10n view, it's just complicating things that always have been simple.

I don't think using hi-IN instead of hi is complex in any way.

This ticket wouldn't exist if there wasn't some existing confusion.

Cheers, Jeff.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

--
Fedora-relnotes-content mailing list
Fedora-relnotes-content@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-relnotes-content

[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Gnome Users]     [KDE Users]

  Powered by Linux