# Re: LaTeX to PO, and DDP hosting for the Packaging Tutorial

```On 12/05/11 at 02:19 +0900, Osamu Aoki wrote:
> Hi,
>
> On Wed, May 11, 2011 at 06:41:21PM +0200, Lucas Nussbaum wrote:
> > On 10/05/11 at 10:24 -0400, David Prévot wrote:
> > > Le 07/05/2011 21:16, Osamu Aoki a écrit :
> > >
> > > > Since this is in LateX and po4a can support LaTeX source, once we move
> > > > this to DDP, it may be trivial to add French version :-)
> > > >  (man 3 Locale::Po4a::LaTeX)
> > >
> > > Jean-Philippe just proposed to translate it into French, and I gave a
> > > first shot to Locale::Po4a::LaTeX, result of the following command attached:
> > >
> > > 	po4a-gettextize -o definitions=perso -f latex \
> > > 	-m packaging-tutorial.tex -p packaging-tutorial.pot
> > >
> > > Where perso contains:
> > >
> > > 	% po4a: command author []{}
> > > 	% po4a: command -date {_}
> > > 	% po4a: command frame {}
> > > 	% po4a: environment axis []
> > > 	% po4a: environment frame []{_}
> > > 	% po4a: verbatim environment lstlisting
> > > 	% po4a: environment tikzpicture []
> > >
> > > I'd welcome some comment and help to provide a more friendly POT file:
> >
> > I'm wondering whether it wouldn't be better to translate on a per-slide
> > basis, rather than on a per-string basis.
> > Since the goal is to great a visual document, it is likely that some
> > fine-tuning and restructuring will be needed within some slides (to
> > avoid line wrapper, for example)
> >
> > > - kick away the “ \\hbr” and “ \\br” stuff;
> >
> > no, that's useful to make the presentation look nicer.
>
> I may be wrong ...
>
> If this is something which should be marked as non-translatable content
> or separate translation content from previous one, this may be addressed
> by customizing po4a.  This will create po4a issues like we had for
> DocBook.  So making copy of Locale/Po4a/LaTeX.pm may be an idea to
> customize po4a for DDP.
>
> > > - kick away the \mode<presentation>, \usetheme{debian} and alike;
> >
> > yes, could be moved to a separate file
>
> Then we can exclude them to get into translation.  But looses chance to
> redefine them for each language.
>
> > > - offer directly the content of pdftitle (instead of pdftitle={Debian
> > > Packaging Tutorial},bookmarks…
> >
> > I'm not sure of what you mean (I must admit I don't know po4a, despite
> > having its original dev in the office next to me).
>
> PO4a is string snippet translation tool using gettext as its backend.
> So if English makes tiny change, we can mark only that one sentence
> as fuzzy and translator can fix it.  So think this a paragraph by
> paragraph translation.
>
> Unlike manual and manpages which does not need to fit page by page
> fitting requirement, presentation slides are a bit different.
>
> > Yes, I agree to host it within DDP. Is switching to svn really a
> > requirement in the process? If we can host it on the DDP git repo, I
> > would prefer that. If we can't, never mind, and let's use svn.
>
> I say just create directory in ddp/manuals/trunk should be fine.

I would really like to stay with git, so that I can keep the history.
Would it be very complex for you if I used a git repo in collab-maint