On Wed, 10 Mar 2010 02:59:41 +1300
Amos Jeffries <squ...@treenet.co.nz> wrote:

> My problem #2 is partly about needing to store man page translations 
> (with system Locales) and these web-format translations side by side
> for each language.
> ie
>   s...@latin/sr-Latn.po, s...@latin/sr_SP.po s...@latin/sr_SB.po
>   s...@cyrillic/sr-Cyrl.po, s...@cyrillic/sr_SP.po s...@cyrillic/sr_SB.po

Pootle supports two directory schemes (we call them tree styles). GNU
and the horribly named Non-Gnu

GNU style means files are named after language codes. it is usually a
single directory.

po/foo/
      foo.pot
      ar.po
      af.po
      s...@latin.po
      ...

if it involves multiple templates then each extra template file gets
it's own directory and it looks like this (note template and
subdirectory can be named anything, they don't have to match)

po/foo/
     manual/
         manual.pot
         ar.po
         af.po
         s...@latin.po
         ...
     foo.pot
     ar.po
     af.po
     s...@latin.po

for Non-Gnu each language gets a subdirectory, files could be called
anything but they tend to have a name that reflects where the
translation strings came from, templates should reside in the
templates directory. like

po/foo/
     templates/
            main.pot
            manual.pot
            ...
     ar/
        main.po
        manual.po
        ...
     af/
        main.po
        manual.po
        ...
     s...@latin/
        main.po
        manual.po

we realize these do not conform to the way every single project works,
but they cover the vast majority of them.

you can use symlinks to adapt your current structure, but Pootle won't
be aware of the symlinks and so can't imitate them when adding new
languages. it will have to be a manual process.

if I understand correctly you are relying on the difference between
POSIX locales and web locales to keep two different translation files
side by side while still being named after the language code. I don't
think this is a good idea in general (adds confusion where things are
unnecessarily confusing already), and we are unlikely to ever support a
scheme like this.

cheers,
Alaa

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle

Reply via email to