view DOCS/xml/README.maintainers @ 22772:d2469c37ee29

r22547: fix up some longer than 80 char lines , and use suggestion from Diego. r22570: dont start newline with a space and readd subdirectory r22718: add new audio and video codecs to libavcodec list r22748: add png and gif encoders, how to use them with mencoder is another question r22749: split sonic into sonic/sonicls and wma into wmav1/wmav2 r22750: add rest of lavc encoders to list (vcr1, cljr, jpegls, ffvhuff, msmpeg4v1) r22751: gsm requires libgsm so remove it r22752: aiff isnt there as well, TEST FIRST, THEN DOCUMENT COMPN! r22753: ok so cljr , vcr1 and msmpegv1 dont actually work... removed r22679: Some more details for the mga_vid section taken from drivers/README. r22686: tdfx_vid compilation has been simplified. r22695: Add a link to Attila's mga_vid port to Linux 2.6.x. r22704: 'make install' now takes care of most manual installation steps for *_vid.o.

The documentation and its translations reside in subdirectories.
When building the documentation, the toplevel Makefile goes into
the subdirectories listed in the SUBDIRS variable and executes make
in each of those directories to create the HTML documentation
in subdirectories of the 'HTML' and 'HTML-single' directories.

IMPORTANT: Do NOT place sensitive files under 'HTML' or 'HTML-single'!
	   It is for generated documentation only.
	   The whole directory tree is wiped out by the Makefile
	   when running 'make distclean' or 'make clean'.
	   Also, subdirectories are wiped out one by one before
	   creating the HTML files.

Each subdirectory must have a Makefile.  Its purpose is to include
the toplevel Makefile.inc file (with the rules to build the docs)
and add dependency information to the main target, $(HTMLDIR)/index.html.
The main target usually depends on all the XML and XSL files in the
subdirectory.  (Note that the toplevel *.xsl files are added automatically
by Makefile.inc, so you do not have to list them.)


Adding new translations
~~~~~~~~~~~~~~~~~~~~~~~

1) Create a new subdirectory and copy the XML files there. main.xml must not be
   copied, it is autogenerated.

2) Make sure to create a 'Makefile' for the translation -- you can
   use 'en/Makefile' as an example.

3) If you want to use a customized XSL stylesheet, create one and name it
   'html-common.xsl'. Also create two additional XSL stylesheets
   ('html-single.xsl' and 'html-chunk.xsl'), with content such as this:

   html-single.xsl:

   <?xml version="1.0" encoding="ISO-8859-1"?>
   <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
                version="1.0">

  <xsl:import href="../html-single.xsl"/>
  <xsl:include href="html-common.xsl"/>

  </xsl:stylesheet>

  html-chunk.xsl:

  <?xml version="1.0" encoding="ISO-8859-1"?>
  <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
                version="1.0">

  <xsl:import href="../html-chunk.xsl"/>
  <xsl:include href="html-common.xsl"/>

  </xsl:stylesheet>


   Note: You mustn't xsl:include or xsl:import chunk.xsl directly!
   Including it can (and will) break building of documentation if chunk.xsl
   is installed at a nonstandard location.

4) If you wish to change the output encoding of generated files, create
   html-common.xsl as suggested in step 4) and add strings such as these
   somewhere between the <xsl:stylesheet ...> and </xsl:stylesheet> tags
   (please, pay attention to quotes):

      <xsl:param name="chunker.output.encoding" select="'your_encoding'"/>
      <xsl:output encoding="your_encoding"/>

5) If you are using your own HTML stylesheet, edit your Makefile and set
   the HTML_STYLESHEET variable to its name. Please, don't call your HTML
   stylesheet 'default.css'.

6) In each translated file after the <?xml ... ?> tag you must put a note
   like <!-- synced with r2 -->, where 2 is the revision of corresponding
   English file (see comment at the top of file).

7) While your translation isn't finished, you can change USE_SYMLINKS
   to "yes" in your Makefile. This will help you testing your translation:
   English files will be used instead of untranslated ones, when generating
   HTML docs.

That's all, in theory.