Francis,
If you intended your work to be in the next release you need to push to
the 2.5 branch. I see you have been pushing to master... git is push up
not trickle down. Just a little heads up my friend.
John
On 11/7/2011 5:20 AM, Francis TISSERANT wrote:
The current state of French documen
Kim, Michael, Francis, John, et al.:
I should say something about myself first of all so you'll have a better
understanding of what I hope to contribute.
I have always been good at working methodically and seeing patterns. I
read carefully and notice things that seem not quite right. (A
psycho
Kent,
Also, I do the following to get all the output put into a text file so
nothing is missed as it scrolls off.
make >> /home/john/Desktop/make.txt 2>&1
John
On 11/6/2011 7:31 AM, Kent A. Reed wrote:
> Gentle persons:
>
> I don't feel comfortable trying to upload edited doc files to git.
>
>
Kent,
You have to do a make clean to see all the errors.
John
On 11/6/2011 7: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 trac
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 documentat
how are translators supposed to notice that the corresponding english document
has changed?
comparing? looking at git history?
-m
Am 07.11.2011 um 02:10 schrieb Kim Kirwan:
>
>
> As far as the Spanish (_es.txt) and German (_de.txt) files
> being all or mostly in English, this is normal, sinc
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
fo
If you are actually fixing things - patch files are good
if you are suggesting changes the maillist is fine.
Chris M
> Date: Sun, 6 Nov 2011 08:31:03 -0500
> From: knbr...@erols.com
> To: emc-developers@lists.sourceforge.net
> Subject: [Emc-developers] How shall I report suggeste
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 'image
