The current state of French documentation is disastrous. There will be a
lot of work to recreate the cross-references. Index names can not remain in
English in French doc.
Translations recreated by Google on 60% _fr files are completely ridiculous and
close to the zero level of technical documentation.
We have retained the Lyx file, they will save us. We are motivated and we
will remake a true documentation in asciidoc.

Francis


2011/11/7 Kim Kirwan <k...@kimkirwan.com>

> Hi Kent,
>
> I have enjoyed your posts for a long time, it's good
> to finally have this opportunity to write back. So thanks
> for your help, we appreciate it very much. I do not claim
> to be an Asciidoc expert and am struggling along with
> everyone else to get used to the new changes, and to wait
> for the experts to apply bug fixes.
>
> I'll fix the images:: problem, if someone hasn't already.
> Note that image:: usually gets two colons but sometimes
> one, depending on the desired effect.
>
> Could you give more info on the "no ID" errors?  I'm not
> clear on this one.
>
> As far as the Spanish (_es.txt) and German (_de.txt) files
> being all or mostly in English, this is normal, since they
> were created as editable documents for the convenience of
> the volunteer Spanish and German editors by copying the
> English docs as the master reference docs.
>
> The French docs (_fr.txt) are more of a mix of French and
> English since some of the French docs were already in
> existence and I kept as much as possible, and then copied
> any new English chapters over to the French.
>
> German translators are invited to edit the _de.txt docs.
> Spanish translators are invited to edit the _es.txt docs.
> French translators are invited to edit the _fr.txt docs.
> Always using the English docs (.txt, no suffix) as the
> master reference docs, so that everything stays in sync
> as much as possible.
>
> Thanks again for your help, Kent. I look forward to
> hearing more from you.
>
> Kim
>
>
> On 11/06/2011 07:31 AM, Kent A. Reed wrote:
> > Gentle persons:
> >
> > I don't feel comfortable trying to upload edited doc files to git.
> >
> > I'd like to report the errors I find in some economical fashion. Shall I
> > do it here? the bug tracker?
> >
> > I have in mind reporting errors in the form of edit lists
> >
> >      e.g., gcode/main_es.txt: all references 'images::images/..." should
> > be 'image::images/..."
> >
> > It looks like all the "no ID" errors found in my build of the docs
> > reside in localized text files but not their counterpart English text
> > files and will require individual repairs.
> >
> > Regarding the localized documentation, I misdirected attention by
> > mentioning I thought the Makefile looked funky. Be that as it may, it
> > looks like it is correctly pulling in localized text files. However, I
> > find that many of these localized text files have not been translated
> > from English. As a result, the manuals are a curious mixture of
> > languages. For example, the Spanish User Manual is in English up to
> > Chapter 16 and then is in Spanish.
> >
> > Regards,
> > Kent
> >
> >
> >
> ------------------------------------------------------------------------------
> > RSA(R) Conference 2012
> > Save $700 by Nov 18
> > Register now
> > http://p.sf.net/sfu/rsa-sfdev2dev1
> > _______________________________________________
> > Emc-developers mailing list
> > Emc-developers@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/emc-developers
> >
> >
>
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to