Issue41

Title Designer loses custom xml encoding= attribute and defaults back to utf-8 on save.
Priority bug Status testing
Superseder Nosy List btami, jcater
Assigned To jcater Topics gnue-designer

Created on 2005-12-01.09:51:45 by btami, last changed 2009-10-16.22:02:59 by reinhard.

Messages
msg129 (view) Author: jcater Date: 2006-04-03.18:54:54
Subversion revision 8348
Modified:
   trunk/gnue-designer/src/base/Document.py
Log:
Since SAX won't let us access the encoding used for a document, but rather converts to unicode, we now always write out XML in UTF-8 encoding.

issue41 testing

msg109 (view) Author: btami Date: 2006-03-31.06:38:33
As i read, we can't handle this in SAX (SAX has no way to introspect encoding
from xml header), so we can consider require all .g* to be in UTF-8.
msg101 (view) Author: jcater Date: 2006-03-30.20:37:45
Note to self: investigate using (xml.sax.saxutils.XMLGenerator) instead of using
print commands to output our XML.
msg100 (view) Author: jcater Date: 2006-03-30.20:36:37
I am at a loss as to how we can properly do this using the SAX reader.  It
converts any XML it reads into Unicode, and recommends any output using the UTF-8. 

I've read this, which follows the same route: 

 * http://www.xml.com/pub/a/2002/11/13/py-xml.html
msg39 (view) Author: btami Date: 2005-12-01.09:51:44
Designer loses custom xml encoding= attribute and defaults back to utf-8.
If you manually specify in your GFD file, for example:
    <?xml version="1.0" encoding="iso-1859-2"?>
then save it, the form will be written as:
    <?xml version="1.0"?>
This will affect our international customers.
History
Date User Action Args
2009-10-16 22:02:59reinhardsetassignedto: jcater
nosy: + jcater
2006-04-03 23:54:56jcatersetstatus: chatting -> testing
2006-04-03 23:54:56jcatersetmessages: + msg129
2006-03-31 06:38:33btamisetmessages: + msg109
2006-03-30 20:37:45jcatersetmessages: + msg101
2006-03-30 20:36:37jcatersetstatus: unread -> chatting
messages: + msg100
2005-12-01 09:51:45btamicreate