W3C home > Mailing lists > Public > www-international@w3.org > January to March 2002

Re: Internationalization & Localization guidelines/checklists

From: Tex Texin <texin@progress.com>
Date: Tue, 08 Jan 2002 11:25:55 -0500
Message-ID: <3C3B1D93.B410D909@progress.com>
To: Tom Garland <Tom.Garland@Sun.COM>
CC: www-international@w3.org, nelocsig@egroups.com
Tom, sorry I left it off the list it was unintentional.

To the lists:
If I left off any other submissions, please let me know.

All of the OS vendors (or all that I work with) have sites for
internationalization with respect to their products.
It is also true for database vendors and the application frameworks

Maybe somebody else would like to publish a list of those sites.

They all offer advice on I18N so can be considered "guidelines". I was
looking for a document with a specific prescription of actions to take,
as opposed to the mix of background on I18N and general how-to's. And
also checklists, that one could use to review software and see if it is
complete with respect to i18n and L10N.

That said, if you can find the guidelines and checklists within any of
these sites, I would be glad to receive the URL.
Many of them were difficult to search, or I should say the most direct
queries didn't turn up what I was looking for.


Tom Garland wrote:
> For those who may have missed the original email exchanges:
> http://www.sun.com/globalization may also be helpful.
> tom

> >
> >From Kano's book (It is still online, just hard to find.):
> >
> >testing checklist
> >http://msdn.microsoft.com/library/books/devintl/S24B1_g.HTM
> >win32 checklist
> >http://msdn.microsoft.com/library/books/devintl/S24AC.HTM
> >
> >From Tiziana's site:
> >http://www.tgpconsulting.com/articles/check.html
> >
> >
> >Richard Ishida's paper "Localisation Considerations in DTD Design"
> >http://www.xerox-emea.com/globaldesign/dtds.htm
> >
> >I18n specific to XML you can look at:
> >http://www.opentag.com/xmli18nfaq.htm#loc_dtdguide
> >http://www.opentag.com/xmli18nfaq.htm#loc_docguide
> >
> >Examples of problematic XML documents (and workarounds) see:
> >http://www.opentag.com/xmli18nfaq.htm#loc_bad
> >
> >"16 steps to globalising your website"
> >http://www.etranslate.com/en/know/know.T3.html
> >
> >http://www.sapient.com/pdfs/strategic_viewpoints/globalization_a4.pdf
> >http://www.rubric.com/local/handbooks.html
> >http://www.tri.sbc.com/hfweb/marcus/hfweb00_marcus.html
> >http://www.uniscape.com/globalization/whitepaper.html
> >
> >
> >http://www.microsoft.com/TechNet/ittasks/plan/sysplan/glolocal.asp?frame=true
> >
> >The 'ITS Requirements' document may have a few things for your list,
> >it's just a draft, but I think it covers some of what you are looking
> >for. After all one of the deliverables of ITS is a set of guidelines.
> >(Requires membership in group lisa-its)
> >http://groups.yahoo.com/group/lisa-its/files/ITS-Requirements

Tex Texin                    Director, International Business
mailto:Texin@Progress.com    Tel: +1-781-280-4271
the Progress Company         Fax: +1-781-280-4655
For a compelling demonstration for Unicode:
Received on Tuesday, 8 January 2002 11:25:58 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:21 UTC