[GRASS5] documentation encoding

[Glynn Clements]

Jean-Denis Giguere wrote:

> > > I have started some work on translation of documentation. I think that 
> > > using utf-8 instead of latin-1 for encoding could help much translation 
> > > effort. If everyone use the same encoding, it will also help dealing 
> > > with special characters like & et > issues.
> > 
> > The encoding should be appropriate for the specific locale. E.g. Alex'
> > Russian translations all use KOI8-R, which is the encoding which is
> > most commonly used in Russia (far more common than ISO-8859-5 or
> > UTF-8).
> > 
> > In spite of the hype, UTF-8 is far from being in widespread use. It's
> > widespread support (in libraries and applications) springs more from a
> > desire by programmers to avoid having to deal with encoding issues
> > than actual usage.
> 
> Is it not a good reason ? I think docbook is a very good choice for
> documentation. There are useful tools to translate this format. POT and
> PO files are easy to manage and help to keep documentation translation up
> to date. How can you deal with translation template (.POT) if each
> translator work with his own encoding. It can be painful to maintain
> translation if we don't have common tools. 

The POT files should be in US-ASCII.

-- 
Glynn Clements <glynn.clements at virgin.net>