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

Re: Can release-notes be checked out from cvs?



On Sun, Mar 18, 2007 at 12:33:27PM +0300, Yuri Kozlov wrote:
> 2007/3/17, Jens Seidel <jensseidel@users.sf.net>:
> >> Updated Russian release-notes is attached.
> >
> >It seems the old version (encoded in UTF-8) was not buildable with an
> >unhacked debiandoc-sgml version!? Why did nobody noticed it?
> Actually, the encoding for Russian release-notes was a koi8-r in the
> old version.

You're right, but the header contained utf-8 twice.

> About debiandoc-sgml 1.1.101. I installed this testing version and
> not found UTF-8 patches from #389065. Why ?

Please check again. Note that specifying -l ru option to debiandoc-sgml
tools still assumes classical KOI8-R encoding. Use ru_RU.UTF-8 as
language specifier for UTF-8. (See
/usr/share/perl5/DebianDoc_SGML/Locale/Alias.pm for default settings.)
The problem is that the build host still does not support UTF-8, so we
need to restrict to classical encoding. Similar problems exist with po4a,
which is outdated on the build host as well.

> >Why did your translation miss the information which was fixed already in
> >the past?
> I using a po4-a, which working with release.en and not with release.ru from
> cvs. I already did changes in the translator_russian.add and the
> version header will be included now.

Does this mean you have a PO file? I strongly suggest you send it as
well, so that it can be committed. The license of the Release Notes is
currently unclear (#332782) but all free licenses require free access to
the source code.

Also further changes to release-notes.ru.sgml would (could) be missing
after further updates as well.

> >PS: I hope I fixed it right. Don't know why, but vim fails again to view
> >the file correctly, even after :set encoding=koi8-r or/and :set
> >fileencoding=koi8-r.
> Yes, all correct. Thank you.
> 
> For vim:
> :e ++enc=koi8-r release-notes.ru.sgml

Thanks a lot, this worked. I'm still confused why fileencoding=koi8-r
does not work (but I found this now in the vim help as well).

Jens



Reply to: