[tex-live] Issue with \textgreater and lualatex

[jfbu]

Thanks David,

Of course I now recall I had this bit of info at back of my head.
(but only use the front part)

On first sight modifying all {} into \/ at the upstream project (Sphinx),
for those kinds of escape from ascii should make it.

Best,

Jean-François


Le 16 juil. 2018 à 08:34, David Carlisle <d.p.carlisle at gmail.com> a écrit :

> luatex list would be better but...
> 
> This is unrelated to \textgreater, it is a documented feature that
> braces have do not affect ligaturing in luatex.
> 
> Using {} is not reliable in classic tex either (a change between the
> earliest and later editions of the texbook was to change the
> suggestion to use {} to \/ for breaking ff ligatures) It does or does
> not break the ligature depending on whether the word was considered
> for hyphenation.
> 
> You could use \mbox{\textgreater}  or \textgreater\/\textgreater or ....
> 
> 
> 
> On 16 July 2018 at 00:45, jfbu <jfbu at free.fr> wrote:
>> Hi,
>> 
>> apologies if wrong list, but I am online for a short wile and
>> wasn't sure where to post.
>> 
>> This MWE
>> 
>> \documentclass{article}
>> 
>> \ifdefined\directlua
>> \usepackage{fontspec}
>> \else
>> \ifdefined\XeTeXinterchartoks
>> \usepackage{fontspec}
>> \else
>> \usepackage[T1]{fontenc}
>> \fi\fi
>> 
>> \begin{document}
>> % uniquement avec lualatex donne »
>> \textgreater{}\textgreater{}
>> 
>> % ici aussi donne »
>> {\textgreater}{\textgreater}
>> 
>> \end{document}
>> 
>> 
>> produces similar result with pdflatex and xelatex
>> but not with lualatex which applies a ligature.
>> 
>> Surely this has been raised somewhere, but is there
>> a fix in mark-up which would be engine independent.
>> 
>> This is a real life issue arising in indexing of
>> Python's >>> prompt with the > being escaped into
>> TeX macro \textgreater{} by some documentation
>> production tool, and then LuaLaTeX gives bad result.
>> 
>> Best,
>> 
>> Jean-François
>> 
>>