2 ms·
It’s neither: it’s that our tooling and manual of style[1] is only developed for our specific conventions for English text. Other people have attempted to start
by robin_reala 3y ago
It’s neither: it’s that our tooling and manual of style[1] is only developed for our specific conventions for English text. Other people have attempted to start alternative projects but getting that set of standards together takes time and effort, and like you say 380k people isn’t that many.
If you do decide to start something then SE’s tooling supports a --white-label flag when creating a skeleton, which would at least get the first few productions off the ground.
[1] https://standardebooks.org/manual https://standardebooks.org/manual
- kjartanThor 3y agoThank you for this, are your tools licensed in such a way that it would be ok to extend and adopt them so that they can be used for other languages?
- robin_reala 3y agoThe code is GPL-3 and the templates are CC0: https://github.com/standardebooks/tools/blob/master/LICENSE.md https://github.com/standardebooks/tools/blob/master/LICENSE.... Feel free to ask on the mailing list if you have any questions, more likely to be picked up there than in a random HN thread :)