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

Re: Romanian Etch Release Notes fail to build

On Tue, Jan 27, 2009 at 10:56:48PM +0200, Andrei Popescu wrote:
> On Tue,27.Jan.09, 10:30:41, Jens Seidel wrote:
> > On Mon, Jan 26, 2009 at 09:12:23PM +0200, Andrei Popescu wrote:
> > > Please don't. We have switched all Romanian content to the new 
> > > diacritics (commabelow instead of cedilla bellow) for Lenny (or at least 
> > > all content that we were aware of), but this change requires us to use 
> > > UTF-8.
> > 
> > In this case you should also enable the required option for debiandoc-sgml
> > namely using the locale ro.utf-8 via option -l! I fixed this for you but noticed
> > that the installed version of debiandoc-sgml on the build host is too old.
> Does debiandoc-sgml need special knowledge about the ro locale? I 
> thought UTF-8 would make this unnecessary.

UTF-8 is not supported by all programs! The main problem here is LaTeX which
is based on classical (mostly 7 bit) encodings. Yep, there exist extensions
but the usage of these requires also explicit support.

> Sorry for the troubles, I really didn't expect to have problems with 
> UTF-8. Also this doesn't make sense to me. It appears to me that zh_CN 
> is also using UTF-8, how come Romanian doesn't work? 

zh_CN isn't active and doesn't build (Etch version). zh_TW is active but uses
big5 encoding. See http://packages.debian.org/etch/all/debiandoc-sgml/filelist
for supported encodings.

Remember that you can use UTF-8 in PO file as long as it can be converted
into latin2.
> Please let's use ISO-8859-2 only as a last resort. I'll try to 
> investigate this, but my debiandoc-sgml knowledge is inexistent and 
> currently I have only limited internet access.

Patching debiandoc-sgml is not useful in this case as the build host has the
stable Etch version installed. The Lenny version supports already ro.UTF-8!
Also debiandoc-sgml is more or less dead.
> If necessary you could disable Romanian until the issue is solved, one 
> way or the other.

I did so.


Reply to: