Difference between revisions of "GnuCash XML format"

From GnuCash
Jump to: navigation, search
(Documentation references should usually link the stable branch "maint")
(Move category to top; update links;)
 
(3 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
This article collects some notes about the XML file format of GnuCash. So far it is just descriptive, and neither normative nor authoritative.  
+
[[Category:XML]]
 +
This article collects some notes about the XML file format of GnuCash. It is descriptive, and neither normative nor authoritative.  
  
 
Beginning with version 1.6, the primary GnuCash storage mechanism is an XML file. The file is optionally compressed with gzip, which is a preference that is set at <u>E</u>dit→Preferences→General→Use file compression.
 
Beginning with version 1.6, the primary GnuCash storage mechanism is an XML file. The file is optionally compressed with gzip, which is a preference that is set at <u>E</u>dit→Preferences→General→Use file compression.
  
−
There is a non-normative RELAX NG schema for the XML file format ([https://github.com/Gnucash/gnucash/blob/maint/libgnucash/doc/xml/gnucash-v2.rnc gnucash-v2.rnc]). There are also DTD schema definitions, but these are outdated and do not define the current format correctly ([https://github.com/Gnucash/gnucash/tree/maint/libgnucash/doc/xml libgnucash/doc/xml]).
+
[{{URL:git}}gnucash/blob/stable/libgnucash/backend/xml/DTD/gnucash-v2.rnc gnucash-v2.rnc] is a non-normative RELAX NG schema for the XML file format. There are also DTD schema definitions in [{{URL:git}}gnucash/tree/stable/libgnucash/backend/xml/DTD libgnucash/doc/xml], but these are outdated and do not define the current format correctly.
−
 
 
−
Please keep in mind that GnuCash series 1.8 used the libxml1 library for XML access, whereas 1.9 and later uses the libxml2 library. Some behavior regarding XML files is therefore quite different in 1.8 compared to later versions.
 
−
 
 
−
XML files written by GnuCash 1.8 versions are missing [http://www.w3.org/TR/REC-xml-names/#ns-decl XML namespace declarations] that are required by most XML processing software (see also [[FAQ#Q: How can I export data?]]). See [https://www.gnucash.org/docs/v2.6/C/gnucash-guide/appendixa_xmlconvert1.html GnuCash Tutorial and Concepts Guide, Appendix A, part 5: Converting XML GnuCash File] for the missing declarations.  From version 1.8.5 onwards, GnuCash can ''read'' XML files containing these declarations ([http://mail.gnome.org/archives/gnome-announce-list/2003-August/msg00070.html 1.8.5 release notes]). From 1.9.0 onwards, GnuCash can ''write'' the required namespace declarations as well.
 
  
 
Many elements in the XML file are identified by Globally Unique Identifiers (GUID). GnuCash includes its own GUID implementation.
 
Many elements in the XML file are identified by Globally Unique Identifiers (GUID). GnuCash includes its own GUID implementation.
  
 
==Character encoding==
 
==Character encoding==
−
GnuCash 1.8.x interpreted XML documents using a character encoding determined by operating-system–level locale settings, and so did not include an [http://www.w3.org/TR/REC-xml/#NT-EncodingDecl encoding declaration] in the opening [http://www.w3.org/TR/REC-xml/#sec-TextDecl XML text declaration]. (The locale setting here constitutes a "higher-level protocol" in W3C vernacular [http://www.w3.org/TR/REC-xml/#charencoding].)  GnuCash serializes non-[[Wikipedia:ASCII|ASCII]] octets (i.e. those with the high-order bit set) as decimal numeric character references. (E.g., an em-dash is represented as “<code>&amp;#8212;</code>”.)
 
−
 
−
On the other hand, GnuCash 1.9.0 and later writes the XML document always in UTF-8 encoding and also includes the appropriate encoding declaration in the opening XML text declaration. (I think the serialization is still done as decimal numeric character references but this has to be checked.)
 
−
 
−
For example, in 1.8.x the UTF-8 encoding of the Cyrillic capital letter “Б” is written as “<code>&amp;#208;&amp;#145;</code>”. As the following Python script shows, the UTF-8 text should be transcoded to recover the original Unicode text.  (This script uses the [http://4suite.org/ 4Suite] XML library.)
 
−
 
−
<pre>#! /usr/bin/python2.4                                                                                                                             
 
−
 
−
from Ft.Xml.Domlette import NonvalidatingReader
 
−
from Ft.Xml.XPath import Evaluate
 
−
from Ft.Xml.XPath.Context import Context
 
−
 
−
# precondition: foo.xac was created by GnuCash with LANG=en_US.UTF-8
 
−
doc = NonvalidatingReader.parseUri('file:///tmp/foo.xac')
 
−
context = Context(doc, processorNss={'cd'    : "http://www.gnucash.org/XML/cd",
 
−
                                    'book'  : "http://www.gnucash.org/XML/book",
 
−
                                    'gnc'  : "http://www.gnucash.org/XML/gnc",
 
−
                                    'cmdty' : "http://www.gnucash.org/XML/cmdty",
 
−
                                    'trn'  : "http://www.gnucash.org/XML/trn",
 
−
                                    'split' : "http://www.gnucash.org/XML/split",
 
−
                                    'act'  : "http://www.gnucash.org/XML/act",
 
−
                                    'price' : "http://www.gnucash.org/XML/price",
 
−
                                    'ts'    : "http://www.gnucash.org/XML/ts",
 
−
                                    'slot'  : "http://www.gnucash.org/XML/kvpslot",
 
−
                                    'cust'  : "http://www.gnucash.org/XML/cust",
 
−
                                    'addr'  : "http://www.gnucash.org/XML/custaddr"})
 
−
 
−
accountName = Evaluate('/gnc-v2/gnc:book/gnc:account[act:id="0d69c3557f4d9340198bfd151f9e13cb"]/act:name/text()',
 
−
                      context=context)[0]
 
−
 
−
# object of type "str" (is actually UTF-8–encoded, not latin1!):                                                                                                                       
 
−
name_raw = accountName.data.encode('latin1')
 
−
 
−
# object of type "unicode":
 
−
name_unicode = name_raw.decode('utf-8')
 
  
−
# objects of type "str":                                                                                                                           
+
With GnuCash 1.9.0, GnuCash writes the XML document using UTF-8 encoding and includes the appropriate encoding declaration in the opening XML text declaration.
−
name_koi8r = name_unicode.encode('koi8-r')
 
−
name_utf8  = name_unicode.encode('utf-8')
 
−
name_utf16 = name_unicode.encode('utf-16')
 
−
 
 
−
assert name_utf8 == accountName.data.encode('latin1')</pre>
 
  
 
==Validation==
 
==Validation==
Line 59: Line 16:
 
The RELAX NG schema file mentioned above can be used to validate an uncompressed GnuCash XML data file. This requires that you:
 
The RELAX NG schema file mentioned above can be used to validate an uncompressed GnuCash XML data file. This requires that you:
 
* save your GnuCash data file in uncompressed format
 
* save your GnuCash data file in uncompressed format
−
* use an XML validator--e.g., [https://github.com/relaxng/jing-trang Jing], which will be used in this example.
+
* use an XML validator--e.g., [{{URL:GH}}relaxng/jing-trang Jing], which will be used in this example.
  
 
As stated above, the GnuCash data file is by default stored using gzip compression. You must first save your data file in an uncompressed state. The easiest way to do this is to change the storage preference and save your file. (Remember to reset the preference afterwards).
 
As stated above, the GnuCash data file is by default stored using gzip compression. You must first save your data file in an uncompressed state. The easiest way to do this is to change the storage preference and save your file. (Remember to reset the preference afterwards).
  
 
Then download jing and run the following command
 
Then download jing and run the following command
−
  jing -c path-to-gnucash-v2.rnc path-to-your-datafile.gnucash
+
<Syntaxhighlight lang="sh">
−
 
+
jing -c path-to-gnucash-v2.rnc path-to-your-datafile.gnucash
 +
</Syntaxhighlight>
 
jing will report any validation errors it finds.
 
jing will report any validation errors it finds.
  
 
;Note:The validation should not be considered authoritative, as the schema is not updated or tested very often. So validation errors can just as easily be due to errors in the schema than due to errors in the data file.
 
;Note:The validation should not be considered authoritative, as the schema is not updated or tested very often. So validation errors can just as easily be due to errors in the schema than due to errors in the data file.
  
−
''Based on information provided by Baptiste Carvello in [https://bugzilla.gnome.org/show_bug.cgi?id=680887 bug 680887].''
+
''Based on information provided by Baptiste Carvello in [{{URL:Bugs}}show_bug.cgi?id=680887 bug 680887].''
  
 
==External links==
 
==External links==
−
* http://gnucashtoqif.sourceforge.net/ - GnuCash XML &rarr; [[Wikipedia:QIF|QIF]] conversion tool
+
* https://gnucashtoqif.us/ - GnuCash XML &rarr; [{{URL:wp}}QIF QIF] conversion tool
−
** [http://gnucashtoqif.sourceforge.net/#mozTocId164261 notes about file format]
+
*: [https://gnucashtoqif.us/#mozTocId164261 Notes about file format]
−
* [http://web.archive.org/web/20070219085556/http://edseek.com/archives/2005/08/18/gnucash-export-to-gnumeric-and-csv/ GnuCash export to Gnumeric and CSV], using [[Wikipedia:XSL Transformations|XSLT]]
+
* [{{URL:WA}}20070219085556/http://edseek.com/archives/2005/08/18/gnucash-export-to-gnumeric-and-csv/ GnuCash export to Gnumeric and CSV], using [{{URL:wp}}XSLT XSLT] -- '''Note:''' With '''GnuCash 3.2''', users can export to CSV directly from the program.
−
* Relevant mailing list threads
 
−
** [http://lists.gnucash.org/pipermail/gnucash-devel/2002-March/thread.html#5750 March 2002]
 

Latest revision as of 22:16, 8 October 2024

This article collects some notes about the XML file format of GnuCash. It is descriptive, and neither normative nor authoritative.

Beginning with version 1.6, the primary GnuCash storage mechanism is an XML file. The file is optionally compressed with gzip, which is a preference that is set at Edit→Preferences→General→Use file compression.

gnucash-v2.rnc is a non-normative RELAX NG schema for the XML file format. There are also DTD schema definitions in libgnucash/doc/xml, but these are outdated and do not define the current format correctly.

Many elements in the XML file are identified by Globally Unique Identifiers (GUID). GnuCash includes its own GUID implementation.

Character encoding

With GnuCash 1.9.0, GnuCash writes the XML document using UTF-8 encoding and includes the appropriate encoding declaration in the opening XML text declaration.

Validation

The RELAX NG schema file mentioned above can be used to validate an uncompressed GnuCash XML data file. This requires that you:

  • save your GnuCash data file in uncompressed format
  • use an XML validator--e.g., Jing, which will be used in this example.

As stated above, the GnuCash data file is by default stored using gzip compression. You must first save your data file in an uncompressed state. The easiest way to do this is to change the storage preference and save your file. (Remember to reset the preference afterwards).

Then download jing and run the following command 

jing -c path-to-gnucash-v2.rnc path-to-your-datafile.gnucash

jing will report any validation errors it finds.

Note
The validation should not be considered authoritative, as the schema is not updated or tested very often. So validation errors can just as easily be due to errors in the schema than due to errors in the data file.

Based on information provided by Baptiste Carvello in bug 680887.

External links

Retrieved from "https://code.gnucash.org/wiki/index.php?title=GnuCash_XML_format&oldid=22249"