Bug#99933: Bug#174982: [PROPOSAL]: Debian changelogs should be UTF-8 encoded
On Tue, Jan 07, 2003 at 10:23:14AM -0500, Colin Walters wrote:
> On Tue, 2003-01-07 at 04:29, Denis Barbier wrote:
>
> Uploading packages with UTF-8 control fields is not ok. It will simply
> put, not work for anyone who's not using a UTF-8 terminal, which is
> unfortunately probably most of our users at the moment. Just Don't Do
> It.
>
> If you really want to help push UTF-8, apply my dpkg patch, help
> find/fix bugs in it, then start ensuring apt-get, aptitude, etc., all
> grok UTF-8.
That is what I am doing now. (Except the dpkg patch which I am going to
play with if I find some time)
>
> > [Could this discussion take place on debian-i18n?]
>
> Actually I think we should probably move to -devel, given how strongly
> this affects the system in general. Even people who maintain programs
I lost count how many times I already had this discussion on -i18n,
-devel and whatever else. The consensus was ALWAYS "OK, that is nice
but just wait until the tools support UTF-8, and besides, I do not care
about it". So we waited and waited until RedHat (much as I dislike RH,
I applaud their effor for switching into UTF-8) and it is no longer
a question of making the "proper" progressive decisions, but a questions
of not falling back too much when compared with RH.
> which care little for i18n will still have to deal with UTF-8 filenames,
> and should be UTF-8 aware in general.
>
> It looks to me like at this point almost everyone agrees with the
> content of my proposal in #99933, and we are discussing implementation
> details. Agreed?
>
I would like to. Though I am not sure about others.
>
> > A similar approach could be considered for deb control files, a new
> > mandatory Encoding field must be added to debian/control (and automatically
> > put in other files when needed), which tells encoding used by all control
> > files. Dpkg and friends may then perform automatic conversion (to UTF-8 or
> > to current user's locale) if desired.
>
> Ugh. I am generally quite opposed to adding an Encoding field, and I
> bet you'll find the dpkg maintainers are too. It should just be UTF-8,
> period. If developers really want to, they can generate control from a
> control.in file by using iconv or similar.
I completely agree.
--
-----------------------------------------------------------
| Radovan Garabík http://melkor.dnp.fmph.uniba.sk/~garabik/ |
| __..--^^^--..__ garabik @ melkor.dnp.fmph.uniba.sk |
-----------------------------------------------------------
Antivirus alert: file .signature infected by signature virus.
Hi! I'm a signature virus! Copy me into your signature file to help me spread!
Reply to: