New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

difficulty using glyphs in the Corporate Use or Microsoft Symbol Areas #7

Closed
mewtant opened this Issue Sep 30, 2018 · 6 comments

Comments

Projects
None yet
3 participants
@mewtant

mewtant commented Sep 30, 2018

With version 2.9 of luaotfload, it has become more difficult to use glyphs in the Corporate Use and similar areas. For example, the \fontchar macro no longer gives the desired result. See https://tex.stackexchange.com/q/453224 for more details.

@u-fischer

This comment has been minimized.

Show comment
Hide comment
@u-fischer
Owner

u-fischer commented Sep 30, 2018

@u-fischer

This comment has been minimized.

Show comment
Hide comment
@u-fischer

u-fischer Oct 1, 2018

Owner

Same problem reported by Claudio Beccari:

\documentclass{book}

\usepackage{libertine}

\begin{document}

First hit this key sequence:\LKeyShiftX{H}

Then hit these keys one by one:
\LKey{E}\LKey{L}\LKey{L}\LKey{O}\LKeySpace\LKey{W}\LKey{O}\LKey{R}\LKey{L}\LKey{D}

And finally hit the \LKeyEnter\ key.

You should now see the phrase ``Hello world'' on your screen.

\end{document}

Current Output:

image

Expected Output

image

Owner

u-fischer commented Oct 1, 2018

Same problem reported by Claudio Beccari:

\documentclass{book}

\usepackage{libertine}

\begin{document}

First hit this key sequence:\LKeyShiftX{H}

Then hit these keys one by one:
\LKey{E}\LKey{L}\LKey{L}\LKey{O}\LKeySpace\LKey{W}\LKey{O}\LKey{R}\LKey{L}\LKey{D}

And finally hit the \LKeyEnter\ key.

You should now see the phrase ``Hello world'' on your screen.

\end{document}

Current Output:

image

Expected Output

image

@u-fischer

This comment has been minimized.

Show comment
Hide comment
@u-fischer

u-fischer Oct 1, 2018

Owner

The generic fontloader moved "all private chars in the font to a dedicated private range" and so broke the access of this glyphs. If this change is permanent all packages and documents which access such glyphs will have to adapt their code.

Currently available work-arounds

use older fontloader

[run]
fontloader= fontloader-reference-2018-07-20.lua;

with a lua function

\documentclass{book}

\usepackage{fontspec}
\setmainfont{Coelacanth}
\newcommand\byunicode[1]{\directlua{
      for k, v in pairs(fonts.hashes.identifiers[font.current()].characters) do
          if v.unicode == #1 then
              tex.print(utf.char(k))
              break
          end
      end
 }}


\begin{document}

\byunicode{62860} \byunicode{\number"F58C}

\end{document}
Owner

u-fischer commented Oct 1, 2018

The generic fontloader moved "all private chars in the font to a dedicated private range" and so broke the access of this glyphs. If this change is permanent all packages and documents which access such glyphs will have to adapt their code.

Currently available work-arounds

use older fontloader

[run]
fontloader= fontloader-reference-2018-07-20.lua;

with a lua function

\documentclass{book}

\usepackage{fontspec}
\setmainfont{Coelacanth}
\newcommand\byunicode[1]{\directlua{
      for k, v in pairs(fonts.hashes.identifiers[font.current()].characters) do
          if v.unicode == #1 then
              tex.print(utf.char(k))
              break
          end
      end
 }}


\begin{document}

\byunicode{62860} \byunicode{\number"F58C}

\end{document}
@u-fischer

This comment has been minimized.

Show comment
Hide comment
@u-fischer

u-fischer Oct 3, 2018

Owner

I uploaded a new version to ctan, it should be available tomorrow. If you want to try directly: Both the texmf-tree and the zip in the dev-branch contain the new files.

Owner

u-fischer commented Oct 3, 2018

I uploaded a new version to ctan, it should be available tomorrow. If you want to try directly: Both the texmf-tree and the zip in the dev-branch contain the new files.

@ArTourter

This comment has been minimized.

Show comment
Hide comment
@ArTourter

ArTourter Oct 3, 2018

That fixes it for fontawesome. Thanks!

ArTourter commented Oct 3, 2018

That fixes it for fontawesome. Thanks!

u-fischer pushed a commit that referenced this issue Oct 3, 2018

u-fischer pushed a commit that referenced this issue Oct 3, 2018

@mewtant

This comment has been minimized.

Show comment
Hide comment
@mewtant

mewtant Oct 6, 2018

Thanks for fixing this so quickly! The updated luaotfload works perfectly.

mewtant commented Oct 6, 2018

Thanks for fixing this so quickly! The updated luaotfload works perfectly.

@mewtant mewtant closed this Oct 6, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment