xgfmerge(1) [debian man page]

XGFMERGE(1)						      General Commands Manual						       XGFMERGE(1)

NAME

       xgfmerge - merges two Xgridfit program files

SYNOPSIS

       xgfmerge [options] file-a file-b [...]

DESCRIPTION

       Xgfmerge  merges  two or more Xgridfit program files, where file-a is a program generated automatically from an existing font using TTX and
       ttx2xgf, and file-b and any other files in the list contain other programming for the font.  Xgfmerge outputs  the  merged  programming	to
       stdout.	To capture the output in a file, use this syntax:

	    $xgfmerge -o merged-file.xgf file-a.xgf file-b.xgf

       Note: To merge Xgridfit instructions with those already in a font, the best method is now to run Xgridfit in merge-mode (option -m).

OPTIONS

       -c     Look  for  a  <default  type="compile-globals"/>	element  in  each  file after the first in the list. If value="no" then ignore all
	      <default>, <control-value>, <function>, <macro> and <pre-program> elements in the file.

       -h     Display a help message.

       -n     Merge <no-compile> elements from all files. <glyph> elements with duplicate "ps-name" attributes are ignored.

       -o file
	      The file to write the output to. If this option is not used, output is written to stdout.

       -p     When a <pre-program> element in a file other than file-a is available, use it instead of the one from file-a. If this option is  not
	      present,	xgfmerge  merges  the programming in the <pre-program> of file-a with that in the <pre-program> of whichever file is being
	      merged at the moment.  The result is unlikely to be good if a single run of xgfmerge merges the contents	of  more  than	two  <pre-
	      program> elements.

       -s     Sort <glyph> elements in the output file into alphabetical order.

       -v     Verbose output: xgfmerge tells you what it is doing at each step.

       -x     Resolve  XIncludes  before  merging  all	files in the list except for file-a. Any XIncludes from file-a.xgf are stripped out of the
	      files before this operation is performed. If XInclude is used to bring global  elements  (<control-value>,  <function>,  etc.)  into
	      these files, it is probably a good idea to use the -c option as well.

FILES

       /usr/share/xml/xgridfit/util/merge.xsl
	      An XSLT script that performs the merge.

       /usr/share/xml/xgridfit/util/xinclude.xsl
	      An XSLT script that strips out unwanted XIncludes.

       /usr/share/xml/xgridfit/util/sort-glyphs.xsl
	      An XSLT script that sorts glyph elements in a file.

       /usr/share/xml/xgridfit/utils/add-blanks.sed
	      Does some formatting of the output.

SEE ALSO

       xgridfit(1), ttx(1), ttx2xgf(1).

AUTHOR

       Xgfmerge was written by Peter Baker <psb6m@virginia.edu>.

       This manual page was written by Peter Baker

								    2009-12-18							       XGFMERGE(1)

XML2PO(1)							  [FIXME: manual]							 XML2PO(1)

NAME

       xml2po - program to create a PO-template file from a DocBook XML file and merge it back into a (translated) XML file

SYNOPSIS

       xml2po [OPTIONS] [XMLFILE]

DESCRIPTION

       This manual page documents briefly the xml2po command.

       xml2po is a simple Python program which extracts translatable content from free-form XML documents and outputs gettext compatible POT
       files. Translated PO files can be turned into XML output again.

       It can work it's magic with most "simple" tags, and for complicated tags one has to provide a list of all tags which are "final" (that will
       be put into one "message" in PO file), "ignored" (skipped over) and "space preserving".

OPTIONS

       The program follows the usual GNU command line syntax, with long options starting with two dashes (`-'). A summary of options is included
       below.

       -a, --automatic-tags
	   Automatically decide if tags are to be considered "final" or not.

       -k, --keep-entities
	   Don't expand entities (default). See also the -e option.

       -e, --expand-all-entities
	   Expand all entities (including SYSTEM ones).

       -m, --mode=TYPE
	   Treat tags as type TYPE (default: docbook).

       -o, --output=FILE
	   Print resulting text (XML while merging translations with "-p" or "-t" options, POT template file while extracting strings, and
	   translated PO file with "-r" option) to the given FILE.

       -p, --po-file=FILE
	   Specify a PO FILE containing translation and output XML document with translations merged in.

       -r, --reuse=FILE
	   Specify a translated XML document in FILE with the same structure to generate translated PO file for XML document given on command
	   line.

       -t, --translation=FILE
	   Specify a MO file containing translation and output XML document with translations merged in.

       -u, --update-translation=LANG.po
	   Update a PO file using msgmerge.

       -l, --language=LANG
	   Explicitly set language of the translation.

       -h, --help
	   Show summary of options.

       -v, --version
	   Show version of program.

EXAMPLES

   Creating POT template files
       To create a POT template book.pot from an input file book.xml, which consists of chapter1.xml and chapter2.xml (external entities), run:

			       /usr/bin/xml2po -o book.pot book.xml chapter1.xml chapter2.xml

       To expand entities use the -e option:

			       /usr/bin/xml2po -e -o book.pot book.xml

   Creating translated XML files (merging back PO files)
       After translating book.pot into LANG.po, merge the translations back by using -p option for each XML file:

			       /usr/bin/xml2po -p LANG.po -o book.LANG.xml book.xml
			       /usr/bin/xml2po -p LANG.po -o chapter1.LANG.xml chapter1.xml
			       /usr/bin/xml2po -p LANG.po -o chapter2.LANG.xml chapter2.xml

       If you used the -e option to expand entities, you should use it again to merge back the translation into an XML file:

			       /usr/bin/xml2po -e -p LANG.po -o book.LANG.xml book.xml

   Updating PO files
       When base XML file changes, the real advantages of PO files come to surface. There are 2 ways to merge the translation. The first is to
       produce a new POT template file (additionally use the -e if you decided earlier to expand entities). Afterwards run msgmerge to merge the
       translation with the new POT file:

			       /usr/bin/msgmerge -o tmp.po LANG.po book.pot

       Now rename tmp.po to LANG.po and update your translation. Alternatively, xml2po provides the -u option, which does exactly these two steps
       for you. The advantage is, that it also runs msgfmt to give you a statistical output of translation status (count of translated,
       untranslated and fuzzy messages). Additionally use the -e if you decided earlier to expand entities:

			       /usr/bin/xml2po -u LANG.po book.xml

SEE ALSO

       msgmerge (1), msgfmt (1)

AUTHOR

       This manual page was written by Daniel Leidert daniel.leidert@wgdd.de for the Debian system (but may be used by others). Permission is
       granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 any later version
       published by the Free Software Foundation.

COPYRIGHT

       Copyright (C) 2005 Daniel Leidert

[FIXME: source] 						    2005/02/10								 XML2PO(1)