Re: [netrexx-pipelines] Migrate OS/2 pipelines to NetRexx Pipes

[René J. <rvj...@xs...>]

After trying lots of latex environments like verbatim, listings, lists and blocks, it came out that the wrong hyphen was in the *actual document source code*. As this has been converted from OS/2 to Windows to Mac and from GML to OpenOffice and LaTeX this is no big surprise. Thanks for finding it. Fixed in NetRexx 4.04.

And yes, we need to clean those things out. For the later examples, I have them in separate files and I start a bash subprocess to make sure the examples actually work. These are easy to check, but when in the document source code this is harder. I have a longer term plan to have most of the source in Markdown, so we can use pandoc to translate to LaTeX and also have html and/or eBooks in addition to the PDF. That transition seems to be a good point to write some extra pipelines to make sure our program text is Unicode clean.


René.

> On 2 Jun 2022, at 11:09, Jason Martin <agr...@gm...> wrote:
> 
> On 6/2/22 03:21, hp...@we... wrote:
>> (Am I really the first who steps into this silly trap?)
> 
> No, there are a some idiosyncrasies when using TeX or LaTeX.
> 
> The one that always gets me is quoted stuff.
> 
> When using X Windows, I like highlighting a PDF passage and popping it to the terminal without touching the keyboard.
> 
> Sometimes what appears to be a quote is really another character.
> 
> We just need to go through our documentation's source files a little closer.
> 
> We could use some people who have free time to do things like that.
> 
> 
> 
> _______________________________________________
> netrexx-pipelines mailing list
> net...@li...
> https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines