Difference between revisions of "Xml files"
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
tar xvfz [[Media:Legend_page.page|Legend_page.page]] | tar xvfz [[Media:Legend_page.page|Legend_page.page]] | ||
| − | + | Note that option 'z' might not be necessary if your browser recognizes ''page'' files as compressed ''gz'' files and decompresses it silently. Anyhow it produces a file ''contents.xml'' which can be viewed by any Internet browser (e.g. firefox[http://www.mozilla.org/firefox|firefox]). | |
<SciFigs> | <SciFigs> | ||
| Line 28: | Line 28: | ||
... | ... | ||
| − | + | The encoding of this file is UTF-8 which may not be directly editable in a text editor that does not support Unicode. Also some ''bash'' command lines (e.g. grep, awk, sed,...) might not support Unicode. To convert it to ASCII (): | |
Revision as of 16:30, 9 March 2010
Many files exported and imported in Geopsy softwares are based on XML structures. For instance, (listed with their common extension):
- page
- mkup
- layer
- cpanel
- ctparser
- gpy
- dinver
- param
- target
Those files are compressed TAR archives containing at least one file called contents.xml.
tar xvfz Legend_page.page
Note that option 'z' might not be necessary if your browser recognizes page files as compressed gz files and decompresses it silently. Anyhow it produces a file contents.xml which can be viewed by any Internet browser (e.g. firefox[1]).
<SciFigs>
<libVersion>2.3.0</libVersion>
<type>Page</type>
<GraphicSheet>
<LegendWidget objectName="object">
<objectName>object</objectName>
<printX>1</printX>
<printY>1</printY>
<anchor>TopLeft</anchor>
...
The encoding of this file is UTF-8 which may not be directly editable in a text editor that does not support Unicode. Also some bash command lines (e.g. grep, awk, sed,...) might not support Unicode. To convert it to ASCII ():
