News for hackers. Stuff that matters.

A comment on Fluent 1.0: a localization system for natural-sounding translations. Parent comment

Re:Fluent 1.0: a localization system for natural-sounding tr... by ngrilly on Wednesday April 17, 2019 @09:08AM (#19682170)
The downside of using separate IDs is that the developer has to "name" each string shown in the user interface, instead of just using the source string as an ID. And as you know, naming things is hard ;-)
[ Parent | on HN ]
Re:Fluent 1.0: a localization system for natural-sounding tr... by zbraniecki on Wednesday April 17, 2019 @03:48PM (#19685836)
Yes, naming is hard, but, to quote the previous commenter "this can be worked around" - you can `slug` any string if you want to. We prefer to think of the ID as the base of the social contract between the dev and the localizer. This enables a lot of fine tuned control over string invalidation.
[ Parent | on HN ]
Re:Fluent 1.0: a localization system for natural-sounding tr... by ngrilly on Wednesday April 17, 2019 @04:04PM (#19686000)
Considering the translation ID as a "slug" is a good tip to ease choosing the ID. Thanks!
[ Parent | on HN ]