Skip to content
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

Missing fonts for Canadian Syllabics #181

Open
ribose-jeffreylau opened this issue May 8, 2020 · 8 comments
Open

Missing fonts for Canadian Syllabics #181

ribose-jeffreylau opened this issue May 8, 2020 · 8 comments
Labels
bug Something isn't working

Comments

@ribose-jeffreylau
Copy link
Contributor

Background

In this page, https://www.omniglot.com/writing/ucas.htm, one can find examples of glyphs for Canadian Aboriginal Syllabics.

Problem description

Each glyph would be rendered as a # character in the output PDF.

Expected output

Each glyph would be rendered as themselves.

Steps to reproduce

  1. Copy and paste some Canadian Aboriginal Syllabic glyphs into a Metanorma adoc file. For example, the ISO 24229 document.
  2. Compile it.
  3. See the glyphs rendered as #s.

Further information

MS Windows and macOS use the Euphemia font for rendering them.

@ribose-jeffreylau ribose-jeffreylau added the bug Something isn't working label May 8, 2020
@ronaldtse
Copy link
Contributor

The Euphemia font is available here:
https://www.tiro.com/syllabics/resources/index.html

https://www.tiro.com/syllabics/resources/compiled_data_sources/Fonts/Euphemia/%202.6.6%20Euphemia%20UCAS.zip

It come with a license so it needs to go into Fontist.

@ronaldtse
Copy link
Contributor

Added to Fontist but not yet active. I think the Metanorma document needs to declare it uses this font (for this script?)?

@ronaldtse
Copy link
Contributor

@ribose-jeffreylau after 2 years this is now possible. Can you help try this out and close if complete? Thanks!

@ribose-jeffreylau
Copy link
Contributor Author

How should one go about testing it? In the Gemfile.lock of my document (ISO 24229), I only see mn2pdf (1.42) but not mn-native-pdf.

Is it the case of adding some syllabics into one of this repo's git submodules' xxx.presentation.xml then running make all? I tried it but the syllabics didn't show in the resulting PDF.

@ronaldtse
Copy link
Contributor

mn-native-pdf is a development repository for stylesheets — it’s not a piece of software. The software is mn2pdf.

The way to test is just to add the document attribute “:fonts:” with the font names. If it installs the font, then it works, otherwise not.

We currently also lack the ability to specify a particular glyph in a particular font…

@ribose-jeffreylau
Copy link
Contributor Author

Just an update here: adding :fonts: Euphemia did not change anything. It didn't seem to be installing any fonts, at least from the metanorma command output to STDOUT.

@ronaldtse
Copy link
Contributor

Right @ribose-jeffreylau , this functionality is not working yet for 2 reasons. The font install doesn't work yet (ping @CAMOBAP on metanorma/metanorma-standoc#618), and that in the text we don't have a way to refer to a particular font yet...

@ronaldtse
Copy link
Contributor

ronaldtse commented Jul 13, 2022

As suggested by @Intelligent2013 :
#368 (comment)

To indicate font for the individual part of the text, I think we can introduce new construction:

... text [font 'Noto Sans JP']#ABC# text... 

Metanorma xml:

... text <inline font-family="Noto Sans JP">ABC</inline> text ...

Something like this will work.

UPDATE: general task specified at metanorma/metanorma-standoc#647

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants