[spec] font convertor - Githubissues

puzrin commented 5 years ago

Dev memo, to remember important parts.

Desired features

Allow define fonts by URL.
- we need Roboto for Material UI.
- it's convenient to not store local copies of binaries
- google's fonts is nice source for start
Allow specify font params (size, weight, italic, ...)
Specify glyphs
- single glyphs (multiple times)
- remapping (how?)
- numeric range (multiple times)
- remapping (how?)
- named set (usually by language - acsii, simplified chinese)
[reserved] should be able to process kerning table & drop unused data
Easy to install & web support
- node.js + webpack or parcel.js
Possibility to process glyph lists from lv_i18n
- probably not direct part of this script, but we should verify possibility of this use case.
As usually, should allow read options from file.

CLI params.

Font params are grouped to current font until new font option found.

Common:

-s - output font size
-o - output file path
-b, --bpp - bits per pixel
-c, --compress - 'auto', compression algorythm (TBD)
- RLE in general, but details depent on bpp & font size
--format - output format, useful for debug & experiments (TBD)

Fonts:

--font - local path or URL
-r - range
- AAAA - single value, in dec or hex (0xAAAA) form
- AAAA-BBBB - range (also with dec/hex support)

TBD

Do we need options for weight/italic or those are stored in separate files?
How to define glyph codes remap?
- single: AAAA->newAAA,
- range: AAAA-BBBB->newAAA_start
how to define chars directly (without codes)
named sets (ascii, latin, cyrilic, ...)?

kisvegabor commented 5 years ago

It's not clear how to define multiple combinations of fonts + glyphs + remap in CLI.

What about using a JSON config to describe complex arguments? It would allow to easily run the script again later with same config.

puzrin commented 5 years ago

What about using a JSON config to describe complex arguments? It would allow to easily run the script again later with same config.

I'd say CLI script without all options support would look a bit "unprofessional" :). I have such ugly CLI wrappers for js-yaml & markdown-it, but always say those are for demonstration only and not officially supported.

In other words, JSON config is possible, but i'd like to try something better first.

kisvegabor commented 5 years ago

Okay, you have more experience in this regards. Let's keep the config file as plan B if there won't be a better solution.

stale[bot] commented 5 years ago

This issue or pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

kisvegabor commented 5 years ago

Not stale.

puzrin commented 5 years ago

Seems found solution for CLI. Updated first pots.

@kisvegabor Could you create repo for font convertor and give me full access there?

kisvegabor commented 5 years ago

Done: https://github.com/littlevgl/lv_font_converter

puzrin commented 5 years ago

https://github.com/littlevgl/lv_font_converter/issues/1 https://github.com/littlevgl/lv_font_converter/issues/2

puzrin commented 5 years ago

@kisvegabor please enable travis-ci for https://github.com/littlevgl/lv_font_converter