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

Request on English documentation and different pinyin in font #2

Closed
NightFurySL2001 opened this issue Jun 21, 2020 · 11 comments
Closed

Comments

@NightFurySL2001
Copy link
Contributor

Is it possible to make English documentation?

Also, how do this font deal with words with different pinyins?

@MaruTama
Copy link
Owner

I am sorry for being late to contact you.

Is this that requested the following documentation?
HOW_TO_MAKE.md

"Also, how do this font deal with words with different pinyins?"

What is this mean? Is "different pinyin" 多音字?

@NightFurySL2001
Copy link
Contributor Author

NightFurySL2001 commented Jul 18, 2020

Thank you for your reply.

Yes, but it would be great if there is English translation for others to use. Documentation usually refers to all documents that are provided for the software, in this case it'll be all the .md files in this repo.

What is this mean? Is "different pinyin" 多音字?

Yes I'm referring to 多音字.

Recently there has been a repo that makes bopomofo with newer OpenType technology, BPMF IVS. It utilize the IVS (ideographic variant selector) in Unicode to change between different pinyin (eg providing 4 glyphs: zháo zhāo zhe zhuó for 着) and also put the variant glyphs in stylistic set (SS01-04). You can visit that repo and check how it works. BPMF IVS has a pinyin standard in bopomofo, so that all fonts generated with that program can be used interchangably without losing the tonal marks (if using IVD). Is it possible to recreate it in this program? (and maybe use the same pinyin standard, which will make conversion between bopomofo and hanyu pinyin a ton easier by just changing fonts)

@MaruTama
Copy link
Owner

MaruTama commented Aug 2, 2020

That's a good idea.
We will soon translate all .md files in this repo into English.

This font does not yet support different Pinyin words.
I am thinking of implementing it using the ligature function.
Implement the ligature #1

@NightFurySL2001 NightFurySL2001 changed the title Request on English documentation Request on English documentation and different pinyin in font Aug 2, 2020
@NightFurySL2001
Copy link
Contributor Author

NightFurySL2001 commented Aug 2, 2020

Thanks. I appreciate the translations :D

Is it possible to generate the different pinyin glyphs with different glyphs name first? The linking (or ligature) can be done later by using glyph names in OpenType e.g. Adobe Feature file (.fea). A simple tutorial for .fea files which can be imported into FontForge is available at OpenType Cookbook.

@MaruTama
Copy link
Owner

MaruTama commented Aug 2, 2020

Is it possible to generate the different pinyin glyphs with different glyphs name first?

I don't have the definite answer yet.

Thanks for the link.

@NightFurySL2001
Copy link
Contributor Author

Got it. You're welcome.

I think HOW_TO_MAKE.md would be a good item to start translating as I guess it provide the steps on how to make the font. Maybe you can make a new HOW_TO_MAKE_EN.md and link them up.

@MaruTama
Copy link
Owner

The English version of HOW_TO_MAKE.md has been created.
Thanks for your help!

@NightFurySL2001
Copy link
Contributor Author

You're welcome. I'll move the pinyin issue back to #1 .

@NightFurySL2001
Copy link
Contributor Author

(There's still more MD files to translate yet... lol)

@MaruTama MaruTama reopened this Sep 25, 2020
MaruTama pushed a commit that referenced this issue Aug 20, 2023
* Create .github/workflows/python-app.yml (#1)

* Update python-app.yml (#2)

* Update python-app.yml

* Update python-app.yml

* Update python-app.yml

* Update python-app.yml

* Upload build font from Github Actions
@MaruTama
Copy link
Owner

MaruTama commented Aug 23, 2023

I've translated the document in its entirety.
 -> #11
I will close this issue.

@NightFurySL2001
Copy link
Contributor Author

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants