[vbox-dev] The documentation is translated into French

[Jean-Philippe MENGUAL]

Hi,

Wouldn't be possible to include in the release process the translation? It would
be, for instance, possible to say that the release comes max 24h (but more generally
12h max) after the orjginal release. The thing is: I update the translation of
the manual and the changelog on the ply. So, once we want to release, I can be
up-to-date in only some hours (less than 5 in the week-end, 12h in the week).

Alternatively, we can decide that French manual is only online. It'd allow you
to release and me to translate the latest changes, after release, 24h after it
max, then we would release the up-to-date release of the manual/changelog online.

It implies that I subscribe too to the rss of the changelog to have changes in
real time. Additionally, we could be more efficient if I could commit on svn in
fr_FR dir. It'd speed up the delay of translation integration for the steps of
last changes.

These are my ideas I share with you.

Best regards,


On Wednesday 20 Feb 2013 à 14:41:56 (+0100), Klaus Espenlaub wrote:
> On 19.02.2013 22:36, Jean-Philippe MENGUAL wrote:
> >Hi,
> >
> >I probably have not translated the contents of the changelog. Because I don't
> >know how it is generated. How is it generated the changelog and is it possible
> >to translate it?
> 
> The changelog is at the moment only available in English (it's
> intentionally separated out from the rest of the manual). The
> problem there is that we need to be able to make changes on a very
> short notice (sometimes minutes before the final build), which makes
> translations very difficult. The effect would be that the
> translations often lack important information.
> 
> If anyone has good ideas to resolve this - tell us :)
> 
> Klaus
> >
> >I wait for your feedbacks.
> >
> >Sincerely,
> >
> >JPM
> >
> >
> >On Wednesday 13 Feb 2013 à 19:55:25 (+0100), Klaus Espenlaub wrote:
> >>On 13.02.2013 18:58, Sérgio Basto wrote:
> >>>Hi,
> >>>On Seg, 2013-02-11 at 15:48 +0100, Klaus Espenlaub wrote:
> >>>>https://www.virtualbox.org/vbox/log/trunk/doc/manual?format=rss&limit=300&mode=stop_on_copy
> >>>
> >>>This link doesn't work
> >>>I see https://www.virtualbox.org/browser/vbox/trunk/doc/manual
> >>>but not rss form
> >>
> >>Sorry about the incorrect URL. The correct one is
> >>
> >>https://www.virtualbox.org/log/vbox/trunk/doc/manual?format=rss&limit=300&mode=stop_on_copy
> >>
> >>>Seems that only timeline could have rss
> >>>https://www.virtualbox.org/timeline?ticket=on&repo-kBuild=on&repo-kStuff=on&repo-vbox=on&max=50&authors=&daysback=90&format=rss
> >>>
> >>>
> >>>Never understand why this trac don't have the links and possibilities
> >>>like others , I have to see in other trac what are the commands and copy
> >>>to VirtualBox trac.
> >>
> >>Me neither, have to ask someone who's currently on vacation why so many
> >>useful features are suppressed. They're all there, just hidden. I guess
> >>that it was an attempt to reduce the server CPU load, which should be
> >>far less of an issue since the migration.
> >>
> >>>we on rpmfusion already export french UserManual
> >>>
> >>>rpm -ql VirtualBox | grep UserManual
> >>>/usr/share/doc/VirtualBox-4.2.6/UserManual.pdf
> >>>/usr/share/doc/VirtualBox-4.2.6/UserManual_fr_FR.pdf
> >>
> >>I guess that's the previous (incomplete) translation. Jean-Phillipe's
> >>new translation is for VirtualBox trunk, so has already some content
> >>which doesn't apply to 4.2.x.
> >>
> >>Really looking forward to having the French manual as part of the next
> >>major release, and once we streamlined the processes more I hope it's
> >>actually possible without significant further effort to "backport" the
> >>translation to 4.2.x.
> >>
> >>We're appreciating every contribution which improves VirtualBox and
> >>provides value to its users, from translating the GUI or manual to
> >>providing well-done packages.
> >>
> >>Klaus