FallenMax

5 ms·

1. 1.▲
   by FallenMax 6y ago

   Thanks for feedback! It looks like a decent lib and I would recommend anyone who need richer i18n support (like plural forms) take a look. As for a18n, it's a deliberate choice to use current format (JSON with extracted key/value
2. 2.▲
   by FallenMax 6y ago

   Update: As far as I know, this should be a subset of the PO format ( http://pology.nedohodnik.net/doc/user/en_US/ch-poformat.html... .). The file format used by a18n is JSON, where its keys are extracted from c
3. 3.▲
   by FallenMax 6y ago

   Will definitely look into .vue support! But for compile translations (per-language), I'm not so sure if added performance can justify introduced complexity (for users' build/serve workflow).
4. 4.▲
   by FallenMax 6y ago

   Not an English speaker but this is still awkward: I always think "i18n" expands to 18 characters until I see your comment and checked `"internationalization".length` in console to be 20
5. 5.▲
   by FallenMax 6y ago

   Thank you! This concern is valid. If we change original (let's say) Chinese texts in code, and re-run the CLI (wrap+extract). These happens (in my company's workflow): 1. CLI removes (oldKey -> oldValue) entry from en.json (a18
6. 6.▲
   by FallenMax 6y ago

   Great job! A multi-user translate platform is essential to the entire workflow!
7. 7.▲
   by FallenMax 6y ago

   Thank you! I'm not familiar with .po/.mo/ugettext, will take a look and answer later.
8. 8.▲
   by FallenMax 6y ago

   Thanks! Yes, Automation is what actually I thought of the 'a' in a18n :) But it's named as `a18n` for some complicated reasons: 1. It aligns well with translation function name and CLI command I want the translation function
9. 9.▲
   by FallenMax 6y ago

   Thanks!
10. 10.▲
    Show HN: a18n – Automated I18n JavaScript Solution(github.com)

    39 points by FallenMax 6y ago|25 comments
11. 11.▲
    Smart TOC – navigation menu for webpage [chrome extension](chrome.google.com)

    3 points by FallenMax 10y ago|0 comments