First of all, this is a bit of a side issue since as noted any reasonable current package that's translated with po-debconf is going to use proper utf-8 fields. Steinar H. Gunderson wrote: > Well, debconf-copydb does: > > - Read in first and second config.dat. > - Read in first and second template.dat. > - Make a new second config.dat, writing all the data from RAM. > - Make a new second template.dat, writing all the data from RAM. > > All this is done via the normal reading functions, which parses everything > over to cdebconf's internal C structs (AFAICS). How should cdebconf keep > track of all this information (which I guess is what you mean by "not > corrupting") without adding almost full support for it (modulo charset > conversion) everywhere? This looks like a quite extensive change to me. The easiest way would probably be to not track the information and store (and output) the field as utf-8 without doing any transcoding. This is not exactly what debconf does, but fields that do not define an encoding are basically using an undefined encoding and it's ok if cdebconf assumes it's really utf-8. If this causes a mojibake then the right way to fix it is to make the package define an encoding. The debconf spec does allow for Description-ll fields so even if they're not well defined cdebconf should not ignore/strip them. -- see shy jo
Attachment:
signature.asc
Description: Digital signature