Hi Jonas,<div><br></div><div>this looks like an interesting project. I will have a closer look at it.</div><div><br></div><div>Thank You</div><div>Felix</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Nov 8, 2012 at 4:40 PM, Jonas Smedegaard <span dir="ltr"><<a href="mailto:dr@jones.dk" target="_blank">dr@jones.dk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Quoting Felix Dietze (2012-11-08 16:04:15)<br>
<div><div class="h5">> Dear po4a team,<br>
> I'd like to renew the workflow of the rulebook of the international<br>
> unicycling federation. It's a big document (~100 pages) with competition<br>
> rules for unicycling. It is constantly changing, because the sport is very<br>
> young and developed a lot. Sadly there is no space for experimental rules<br>
> that need to be tested first.<br>
> Right now it is written in MSWord, passed around by email and the<br>
> translations are not coordinated very well. This worked out for the last<br>
> 10 years, but I think today we can do much better.<br>
> How I think it should work:<br>
> - Many people should be able to write differnt parts of the document at<br>
> the same time<br>
> - People need to know what changed at which time, so we need version<br>
> control<br>
> - There should be versions with experimental rulesets for testing<br>
> competitions<br>
> � - If an experimental rule works out, it can be merged into the master<br>
> document<br>
> - The translation should be done collaboratively by the community<br>
> - people should be able to view the current versions (including<br>
> translations) online and/or print them<br>
> - If a change to a master/experimental document is made, the translation<br>
> system is automatically updated, so that the community can start to<br>
> translate changes immediately. (No regular admin interaction)<br>
> Here are my ideas so far:<br>
> - Rewrite the whole thing in LaTeX (can render to HTML or PDF)<br>
> - Put it in a git repository and manage experimental versions as branches<br>
> - With every commit render the pdf and html versions.<br>
> - Translate it (and also the experimental branches) collaboratively with<br>
> po4a and Pootle and also render the translated documents automatically<br>
> I think this could solve the issue. But before we start to work I want to<br>
> know if this is the right approach. Latex and git are no problem. But for<br>
> the translation I'm not sure.<br>
> With a new commit in git, we could trigger a po4a-updatepo for the changed<br>
> latex files in every branch. But is it possible to automatically reinject<br>
> them into Pootle? How do the translations flow back from Pootle to the<br>
> build system. If a new language is set up in Pootle, how does it create<br>
> new documents? Can we do version control for the languages to be able to<br>
> jump back to an older version of a document with proper translation?<br>
> I guess you can answer these questions easily and support us to set this<br>
> up properly.<br>
<br>
</div></div>Not really what you ask, but related: If there is little need for rich<br>
markup of collaboratively edited content (as opposed to possibly<br>
less-collaborative styling), I dearly recommend that you have a look at<br>
Pandoc, and track not LaTeX but Markdown as master centent format.<br>
<br>
I was somewhat involved in the development of the<br>
<a href="http://islandsofresilience.eu/" target="_blank">http://islandsofresilience.eu/</a> and for that threw together a structure<br>
that supported both online annotation, online wiki-like editing (in<br>
multiple branches if you like, each hosted on separate subdomain) and<br>
offline git-based markdown editing. And then separate HTML5/CSS3 and<br>
LaTeX styling for web and print outputs, respectively.<br>
<br>
Our project did not involve l10n (and for second round of public review<br>
the content authors chose a different administration approach than my<br>
framework), but such addition should be possible: po4a supports Markdown<br>
(I wrote that ;-).<br>
<br>
Sources for my work is here:<br>
<a href="http://source.epfsug.biks.dk/?p=resilience.git" target="_blank">http://source.epfsug.biks.dk/?p=resilience.git</a><br>
<br>
<br>
Hope that is of some use/inspiration.<br>
<span class="HOEnZb"><font color="#888888"><br>
- Jonas<br>
</font></span></blockquote></div><br></div>