Denis Barbier wrote: > > After some discussion on IRC, here's the updated patch. > > > > --- cdebconf-0.102.orig/src/template.c 2005-09-21 19:07:46.000000000 +0200 > > +++ cdebconf-0.102/src/template.c 2006-06-19 20:54:35.000000000 +0200 > > @@ -354,7 +354,7 @@ > > free(orig_field); > > return NULL; > > } > > - cp = strstr(altlang, ".UTF-8"); > > + cp = strcasestr(altlang, ".UTF-8"); > > I am not sure that this is desirable, next time you will encounter "utf8" > instances, and maybe other names too (except that I cannot find another > one ;)) I don't know of any such instances.. > > + /* Plain debconf supports undefined character sets, on the > > + form "Description-nb_NO: ", which is valid if the text is > > + ASCII (but debconf still uses that syntax regardless of > > + validity if the application does not specify a character > > + set). To avoid losing these fields, we simply read them > > + in as if they were UTF-8 fields, as valid ASCII is always > > + valid UTF-8 as well. > > Ditto, this is supported by debconf for compatibility reasons, but we > should try hard to get rid of undefined encodings wherever possible. Getting rid of them by deleting them out of the debconf database when copying other info into there with debconf-copydb is undesirable. -- see shy jo
Attachment:
signature.asc
Description: Digital signature