Re: Bug#283949: allow generation of plain text
On Wed, Dec 08, 2004 at 07:02:44PM +0100, Frans Pop wrote:
> > Works for Russian. The special characters are not shown, as they are
> > not available in KOI8-R - I'd propose switching to UTF-8 as soon as
> > possible.
> Could you have a look at how to set up things so the single HTML file will
> be generated in UTF-8? You seem to be better at that kind of thing than I
> am :-P
I'll look into it, this should be _sowewhere_. :)
> I guess the final file for Russian could be generated in UTF now
> (without the switch of the HTML file). However, is that what Russian
> users will expect: will they, in general, know how to recognize, open
> and read a document that is UTF-8 encoded?
The russian users are a special case. They will be the last ones to switch
to unicode, as they do not consider any advantages and only talk about
"KOI8-R works and if the 8th bit is cut off, I can still read it" and such
kind of 1980es speech. When RedHat 9.0 has been released, the first thing
the users asked was how to switch the whole distribution back to KOI8-R.
It's plain sick.
My radical opinion is to enforce UTF-8, as most distributions will be
UTF-8 based in a year (Debian will switch after sarge release, AFAIK),
RedHat and SuSE are already there. However, the Russian manual translation
won't hit the installation CDs anytime soon (there are some extra glitches
with xml2po which have to be worked on), we can just use UTF-8. If the
manual had to go to the CDs, KOI8-R could have been considered.
> If the systems of most users are set up for KOI8-R, I would suggest
> leaving the doc in that encoding.
It's relevant only for the plain text manual, which will not be available
on the CDs, the webpage is not important. So it can stay UTF-8
--
Nikolai Prokoschenko
nikolai@prokoschenko.de / Jabber: pronik@jabber.org
Reply to: