Johannes Neumeier
Johannes Neumeier
Sure, either way would work. A "reroll" button per feature, or a "lock-unlock" per feature. Thinking back on this issue I think one of the biggest problems or use cases...
On that note, it _would_ be nice to know the exact page(s) and maybe even #sections of wikipedia referenced. Some languages/scripts have several relevant pages etc. For a changing medium...
In as far as they are part of the official orthography I am in favor of this. After all, the database is not collecting design requirements but orthographies.
Also relevant for https://github.com/rosettatype/hyperglot/pull/114
> I will also move them to sources: Just to be 100%, you're suggesting renaming `source:` to plural `sources:`, yes? Okay by me, probably needs a few spots updating in...
I can't pinpoint the commit where we changed how `hyperglot-save` parses the characters, but di/trigraphs are as of this writing retained as they are in the character lists, so this...
Related to this as well: `hyperglot-save` retains the order of characters in `base` (I vaguely remember _this_ being the trigger why we changed the saving implementation), so there likely are...
See #172 for some discussion related to including upper case variants of digraphs; it's sort of unclear if the "uppercase" variants of digraphs should be double upper (like in `squ`)...
Very interesting, thank you @moyogo! On 1) I agree... the use of the jdotless in the example likely stems from a designer centric view where that letter would be the...
Could use same approach as #86 as different CLI command or part of `hyperglot-data ...`