Once again I have left out important information. This bug is
specific to creating info files. So when we go from test.org ->
test.texi -> test.info, the info file does not look right.
However, I did sort of forget that we can also go test.texi ->
test.pdf so I'll have to keep that in mind now that I've been
reminded.
Pedro Andres Aranda Gutierrez <[email protected]> writes:
That only leaves the issue of the exporter.
To tell you the truth, I wasn’t quite aware of the warnings
<blush/>. I just ‘make pdf’ and check on the resulting PDF
which seems to be generated without errors: the *Note 1:*
appears as a bold ’Note 1’ in the PDF, so there is no way to
tell…
The warning only occurs when going texi -> info. So it showed up
when running "make doc" (or whatever the command is. I'm not
going to pretend I actually do this).
I have spent like 3 hours on this and I have come with 2
solutions. Well two variations of the same solution.
Nonbreaking space: @strong{Note@U{00A0}fly me : to the moon}
Zero width space: @strong{Note@U{200B} fly me : to the moon}
Emacs seems to render NBSP as "_" and it also prevents breaking
so the zero width one it probably better.
IDK what do you guys think?
Taken with a pinch of salt (I don’t use the info file), ZWS
seems to be “better”, provided that doesn’t break the PDF.
Oh this is annoying. Now I have to ensure the texi file both
produces a nice info file and a nice PDF file. I don't want to
add any extra characters to PDF so I should add a condition that
makes the texi file look like this:
@strong{Note@inlinefmt{info, @U{200B}} fly me : to the moon}
My investigation of texinfo initially began from another thread
where someone was requesting that the texinfo files are generated
in a nice human readable way. Thankfully, this will only occur in
specific circumstances but it doesn't look too readable to me.
I think I might look into texinfo user defined macros to see if I
can remedy this situation.
