On 10/27/2013 3:47 PM, Jeff Epler wrote:
> Yes, the last time I looked at this all non-ASCII characters caused this
> problem, including characters required to write proper French and
> Spanish docs, as well as other characters like the trademark and
> copyright symbols.

My personal recommendation for English-language versions is to not use 
any non-ASCII characters but instead use proper numeric character 
references (NCR) and/or character entity references (CER) just as in 
SGML, HTML, and XML documents.

An easy rule to remember would be, if the character can't be entered in 
a single key stroke using an ASCII keyboard, then use the proper 
NCR/ECR. Just because many O/Ses provide tricks for embedding non-ASCII 
characters isn't a good enough reason to do it.

Unfortunately, this is a onerous solution for non-English versions. I 
don't know the answer there, but at least they get to start from clean 
ascii files. Getting away from ASCII editors and using XML/SGML-aware 
editors would help.

>
> While I could push a commit to change all the non-breaking spaces to
> literal spaces, it feels like this does not solve anything.

I'm not convinced that many of the non-breaking spaces in the docs 
sources are necessary, but assuming they represent the author's intent, 
I think the solution I already demonstrated with NCR/CER is the better 
choice.

But that's just me. I suffered through all this character encoded crap 
when I was the editor of IGES and STEP documentation back in the 
1980s-1990s. It's a pain to get submissions from dozens of authors and 
try to make sense of them.

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

Reply via email to