News for hackers. Stuff that matters.

A comment on Show HN: Localization and translations should be code, not data. Parent comment

Re:Show HN: Localization and translations should be code, no... by LeviticusMB on Wednesday July 06, 2022 @10:37AM (#32001648)
That Perl reference was new to me. Very interesting. Never localized my Perl programs back in the day. But of course I should not be surprised that Perl had a solution to any given problem 20+ years ago ...

I like Fluent. It's just that ... when all the power of modern JavaScript/TypeScript (template literals/JSX/validation/custom functions) and code editors (syntax highlighting/JSDoc/references/usages) are already in place, why not use it instead of introducing a whole new layer of tooling?

[ Parent | on HN ]
Re:Show HN: Localization and translations should be code, no... by samuelstros on Thursday July 07, 2022 @04:05AM (#32011141)
I have been thinking about generating types from Fluent files. That would give you most benefits that you as developer seek from translations as code, wouldn't it?
[ Parent | on HN ]