On Sat, Oct 26, 2013 at 9:59 PM, Kent A. Reed <kentallanr...@gmail.com>wrote:
> <...>
> Funny, though, I didn't get a hit on lines 657 and 668 in this file
> grep'ping on 'G10 L2'. Aha! We know what that means. Sure enough, there are
> multiple nonbreaking spaces in line 657 and in line 668. The multiple
> occurrences account for the repetition in error messages, although there
> isn't a one-to-one match with the "MalformedUTF8-sequence" messages,
> presumably due to the way the parser eats its input.
>
> I edited the file to replace those nonbreaking spaces (vim command :as
> reports they are ASCII decimal 160 or hex a0; in UTF-8 they would be
> \xc2\xa0) with spaces (ASCII decimal 32 or hex 20) and rebuilt the docs.
> Voilà.
>
I should clarify the parenthetical comment. The files actually do contain
the 2-byte UTF-8 code for nonbreaking space (\xc2\xa0). It's vim which
reports in ASCII as if the character is a single byte (\xa0).
Checking the asciidoc FAQ, I see answer #45 says to use character reference
entity   for nonbreaking space (after all, it is *ascii*doc). It also
says one "can try the predefined {nbsp} attribute reference."
Guess what---both recommendations work! I build the docs twice, once with a
fresh copy of gcode.txt edited to replace the nonbreaking spaces in the
G-code example lines with   and again replacing them instead with
{nbsp}. All English-language pdfs built in both cases. In both cases, the
build then broke on the first French pdf, Master_User_fr.pdf.
I stand by my recommendation not to use the nonbreaking space character
directly. Let the markup do its job.
Regards,
Kent
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
