Re: Weird space character

On Fri, Oct 18, 2019 at 10:03 AM Terry Brown wrote: "Vanilla" LaTeX systems tend to use `pdflatex` to process things, and don't > understand unicode inputs without extra fiddling. If you use XeTeX > (`xelatex`), it assumes unicode by default and makes things simpler - in a > lot of cases it can

Bob H: would distinct Leo IDs help with #1348?

#1348 has been closed, but I'm not sure of its status. gnx clashes are a recurring theme when using Leo (or the bridge) to spawn many other copies of Leo quickly. I am wondering whether these clashes might be avoided if Leo would use a

Re: Weird space character

"Vanilla" LaTeX systems tend to use `pdflatex` to process things, and don't understand unicode inputs without extra fiddling. If you use XeTeX (`xelatex`), it assumes unicode by default and makes things simpler - in a lot of cases it can be a drop in replacement. I think TeXLive supports either,

Leo 6.1b1 coming Friday, October 25

Leo 6.1 b1 will go out the door next Friday. Barring significant problems, Leo 6.1 final will be released the following Friday, November 1. For the past several weeks I've been wondering whether to set the release date for 6.1b1. I'm glad I didn't: it allowed lots of time for testing, new bug

Re: Weird space character

On Fri, Oct 18, 2019 at 7:50 AM Rob wrote: > I re-read the error message in the LaTeX processor and perhaps I should > clarify. > > Keyboard character used is undefined in inputencoding`utf8'. > > Reviewing the documentation for that package (inputenc) suggests the error > is because there is no

Re: Discuss: what should Leo's sphinx commands do?

When I use sphinx, step one is to always create a directory for the project. I then run sphinx-quickstart to create the conf.py and the _build and _static directories. The ideal for my workflow would be to start with an @sphinx node that would do all that for me. ie. in the headline @sphinx

Re: Weird space character

I re-read the error message in the LaTeX processor and perhaps I should clarify. Keyboard character used is undefined in inputencoding`utf8'. Reviewing the documentation for that package (inputenc) suggests the error is because there is no corresponding glyph to map to output. So, it's

Discuss: what should Leo's sphinx commands do?

I am working on the sphinx and sphinx-with-preview commands. These commands convert one or more @sphinx trees into *sphinx input files*. The commands then call the *sphinx-build* tool to create one or more *sphinx output files*. These two sphinx commands are similar to the corresponding adoc

Re: Weird space character

On Thu, Oct 17, 2019 at 9:21 PM Rob wrote: My LaTeX processor choked on 2 instances of an unknown UTF8 character. > Probably came into Leo when I copied from somewhere else (perhaps an MS > Word document). > I'm not sure there is such a thing as an "unknown" UTF8 character. Leo is quite