With LayoutNG NGInlineNode doesn't require up-conversion to utf-16 for BiDi resolution for latin1 content. However the shaper still does.
Harfbuzz has support for shaping latin-1 content. Adding a latin-1 path could not only reduce memory overhead but also increase performance somewhat for latin-1 content.
Whether this is worth doing is debatable.
Comment 1 by sheriffbot@chromium.org
, Feb 21 2018Status: Untriaged (was: Available)