Javier Bezos

@car222222 Let’s consider an `l`-column: ```tex \hskip\tabcolsep {\hskip 1sp\ignorespaces\@sharp\unskip\hfil} \hskip\tabcolsep \hskip -.5\arrayrulewidth \vrule width\arrayrulewidth \hskip -.5\arrayrulewidth ``` There are 4 logical element in a row: * The column separation (lines...

@car222222 I’ve made a few patches for the standard `tabular`, as well as for `array` and `colortbl`. Before proposing a change, I’d like to see what other related packages do.

@Udi-Fogiel Interesting idea, which I'm going to explore.

@Udi-Fogiel So far, all my tests work. I don't like to make changes hastily, so I'll continue exploring and testing for a few more weeks. I never liked `\bbl@nextfake`, which...

The problem is Amiri uses the Private Use Area. Once the box is built, there is no information about the direction of the glyphs. If the direction is set explicitly...

Yes, I know (and these are great news), but I just got back from a trip. I still have to look at it.

> What you are seeing is the way luaotfload handles glyph indices that don’t directly map to Unicode code points, Amiri itself does not use any PUA. I see. Thank...

Or a flag with a lua property meaning ‘already processed with bidi’.

Yes, I know, but as far as Unicode is concerned, the initial, medial, final and isolated forms of a letter are the same character, and at this point of the...

And it's applied at the right place, before the font layout, so the box is correct. The problem is the bidi algorithm is applied _again_ when the box is unboxed,...