Hello Sébastien, My email server has been down since 14h today, so if you need to email me, please use: [email protected] for the moment.
If you pull down the current git repo for docs and checkout master, you will find that the directory docs/manuals/fr/ has a number of changes. - I have updated all the text to be the current English. - I have renamed all the files from xxx.tex to xxx-en.tex - In every subdirectory, I have added a "base" directory that contains the English files as of now. Those files do not have the -en postfix. - I have tested all the directories to ensure that it "compiles" correctly. - In several of the directories (console and main only I think) there is a subdirectory named "old", which contains the old files that were translated into French. For the files that were translated, this might save a lot of time. They are probably quite a bit out of date though, so they would have to be checked. Now, my idea is that everytime someone wants to translate a file, he would change its name from xxx-en.tex to xxx-fr.tex and put his name in a comment at the top of the file, then get it committed. This way, everyone will always know who "owns" each file, and it will be clear whether a file is in English or is in French (or in the process of being translated). If anyone else on this list is interested in translating any other language, please let me know, and I can do the same for those files (i.e. for Spanish or for German). Best regards, Kern On Wednesday 03 March 2010 15:48:16 Sebastien Guilbaud wrote: > > Yes, and I think I will ask you to send me a note, and I will explicitly > > mark each file each translator is working on. > > fine, i'll do that > > > By tomorrow, I will try to setup a structure where you can start > > translations. I am going to put the old French translation into a > > subdirectory of the current git repo. I am going to bring all the French > > documents still in English up to date, and I will make a "base" that has > > a copy of the English that you are starting with. This should allow us > > to track and make diffs in the English between the time you start and any > > later time. > > > > In the next couple of days, I will also try to write a little document on > > this so it will be clear to translators what should be done. > > great, I'll have time to play with git on my side, wander > around the documentation, refresh my latex skills and have > a look at linguist > > > I will also look at po4a to see if it could help us. > > it would be so great to split content/formatting, IMO > > best regards, ------------------------------------------------------------------------------ Download Intel® 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 _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
