plex
plex copied to clipboard
IBM
Plex 7.0 (next)
Goals
- Able to include any Plex language for internationalization
- Able to include any additional font weights for a font family
- Able to include any additional font style variants for a font family
- Migrate to Dart Sass
Requirements
- There is a sensible fallback that uses a CDN by default
- Able to self-host font files
To-do
- [x] Update Hebrew and Arabic to use latest PostScript/Font names
- [x] Add tooling for easier/automated pre-release and release procedures
- [x] Utilize Sass modules to permit modular builds based on application requirements (weights, languages, font-face features) for Carbon languages +1 non-standard variant
- [x] Remove ie11 font files (eot/ttf/otf)
- [ ] Add semver to font files
- [ ] Same as above but for all languages
- [ ] Use @forward rule
- [ ] Add support for subsets
- [ ] Create declarations for Variable font
- [ ] Document build pipeline and release procedures
- [ ] Fix Korean asset zip for github release
- [x] Add IBM Plex Sans JP to github for release
- [x] Add IBM Plex JP sample text to IDL typetester —> “Non-Latin scripts” https://github.com/carbon-design-system/design-language-website/issues/965
@johnnyshields It's not, @BoldMonday do we have an update on the intended release date for Japanese?
@johnnyshields Our current estimate is sometime in June. The latter part of the month to be safe.
* Able to include any additional font weights for a font family
@vpicone It means that will be 9 weights (from 100 to 900) plus italics (18 styles)?
It appears that the "split" fonts are included as font files in the latest next, but they aren't declared in the CSS/SCSS. Is this because it's not done or are split fonts being phased out for 6.0?
when will Hebrew be fixed? it's been almost a year since I reported kerning issues in Hebrew and someone said that it is already fixed but no new version is published... why wait on it?
@johnnyshields Correction, it looks like we'll be able to include IBM Plex Sans JP in this release.
@elyran2 The Hebrew fixes will be resolved in the next release. @vpicone can provide a more accurate timeline. There are many updates but a few in Arabic and Hebrew are at the top of the list.
Add font ligature please, it's very nice to code with
Coding ligatures have been discussed in https://github.com/IBM/plex/issues/63
@mjabbink @katie-A-IBM my plan is to have the Japanese files released in a beta by Friday with an official release by the end of next week.
I'll update the video and remove the Noto card ASAP.
Thanks for update @vpicone I already removed the Noto Card https://github.com/carbon-design-system/design-language-website/pull/972
The only think left is to add the Plex JP in the type tester section with sample text and placement all provided here https://github.com/carbon-design-system/design-language-website/issues/965
Hi - any comment on my question above yet?
Yes, the styles will use subsets. You can see subsets in the list of items at the top of the issue.
@mjabbink @vpicone And Plex Sans Hebrew + Plex Sans Arabic updates please.
Those are not released either! Oh wow. OK, we gotta get that done.
@alisonjoseph We defiantly need to get these in this sprint.
@mjabbink Hebrew and Arabic are released under the next branch: https://github.com/IBM/plex/releases/tag/v6.0.0-next.6
They require breaking changes due to the change in family name.
@dayfuaim OSF and SCs are maybe future items but for now, those are not on the priority list. The original intent was to not include those but have always considered those for potential future enhancements.
Implement #401 please. I find markdown's headings like ##### very hard to read due to the separation in between.
I am not a programmer, so I am waiting for a Japanese monospace font that is suitable for general use and still highly legible. That's why I have high hopes for IBM Plex.
In open source projects, it is unavoidable that Japanese language support is lacking. This is because there are few Japanese contributors, and I am ashamed of that.
