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

Weighting for MPlus Code #3

Closed
aaronbell opened this issue Apr 29, 2021 · 10 comments
Closed

Weighting for MPlus Code #3

aaronbell opened this issue Apr 29, 2021 · 10 comments

Comments

@aaronbell
Copy link
Contributor

Hello!

Writing the script for building the fonts and had a question regarding MPLUS Code. Based on my understanding, you're looking for something like this:

Variant Latin set Kana Set Kanji Set
MPlus Code Latin MPlus Code None None
MPlus Code JP MPlus Code MPlus 1 Kana MPlus Kanji

The "MPlus Code Latin" is a variable font with weight and width axis (50 to 60), and MPlus Code JP is similarly a variable font with weight axis.

For the JP version, the current set of masters has a differing set of weights than the MPlus 1 and Kanji set do, with MPlus Code generally being lighter than the corresponding Japanese glyphs:

Screen Shot 2021-04-29 at 3 56 38 PM

Screen Shot 2021-04-29 at 4 03 25 PM

Screen Shot 2021-04-29 at 4 04 21 PM

I anticipate that you'll want the weights to align across the three scripts, so how do you want me to resolve this? Shall I generate an instance of the Kana / Kanji set that aligns with the Regular and Bold? Or do you want to leave it "as is"?

@coz-m
Copy link
Owner

coz-m commented Apr 30, 2021

Hi Aaron,

  • In the case of MPlus Code JP, I was thinking of limiting the Latin set to "code 50" so that 1 Japanese glyph corresponds to the width of 2 Latin glyphs. What do you think, Aaron? Should I have a combination of "code60" and Japanese glyphs that is easier to read even if the 50: 100 balance is lost?

  • MPlus Code is considering a 5-weight deployment from Thin to Bold. Japanese glyphs Black and Extra Bold weights are not used.

Thanks,
Coji

@aaronbell
Copy link
Contributor Author

For Code JP, I suggest using just "code 50" since the intent is to keep glyphs on a monospace grid.

As for the weights, I understand your intent—I'll export out instances of the Regular and Bold to match with the Code weighting. Thanks!

@coz-m
Copy link
Owner

coz-m commented Apr 30, 2021

Thank you for your advice. Then, as originally planned, please support only "code 50" for MPlus Code JP.

Thanks,
Coji

@coz-m
Copy link
Owner

coz-m commented May 24, 2021

@aaronbell
Thomas Linard has asked me to add 2 instances to submit the variable font to Google Fonts, but these variable fonts are generated by your script, so how to fix them? I don't understand. Will you support me?

#14

@coz-m coz-m reopened this May 24, 2021
@aaronbell
Copy link
Contributor Author

Either update the glyphs sources with the two new instances, or let me know where they should be in the weight axis, and I can update the files.

@coz-m
Copy link
Owner

coz-m commented May 24, 2021

Thomas Linard says, "So, please add an ExtraLight instance and a SemiBold instance."

@aaronbell
Copy link
Contributor Author

Yes, we need to set what the weight values will be for the ExtraLight and SemiBold instances:

MPLUS-1___Instances

Either you can do that, or tell me what you want and I'll update them.

@coz-m
Copy link
Owner

coz-m commented May 24, 2021

Hmmm, I don't understand well, but can you make settings that do not affect the current font content?

@aaronbell
Copy link
Contributor Author

aaronbell commented May 24, 2021 via email

@coz-m
Copy link
Owner

coz-m commented May 24, 2021

I'm sorry you are very busy, thank you.

@coz-m coz-m closed this as completed May 24, 2021
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