Hi there, I wonder If anybody else has the ocassional problem with editing her/his GNUtunesDB.xml.
Since it is XML and the encoding is UTF-8 you don't have any problem as long as your system is completely UTF-8 compliant. I however have a mixed iso-8859-1 iso-8859-15 and UTF-8 mess and some of the editors that I like to use are not very smart about handling the character encoding. It would be very easy to convert everything outsite the ascii range to the XML escaped version. So say, instead of some garbage you'd see "ś" where a "Latin Small Letter s with Acute" is. Pro: GNUtunesDB.xml becomes a pure ascii file. No more editor/viewer issues. Contra: The GNUtunesDB.xml becomes slightly bigger and for people with a clean UTF-8 toolchain it becomes a little less readable. (Note: You can still edit the file and insert native UTF-8 as you please.) Any thoughts? cheers -henrik _______________________________________________ Bug-gnupod mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/bug-gnupod
