undefined | Better HN

0 pointsTeMPOraL9y ago0 comments

> AFAIK localising "formatting literals" is the more normal method, it avoids redundancies as you don't need two different systems

I never understood why people think this is a good idea. The exact same sequence of letters in an English phrase, which you would like to use instead of IDs, can mean two different things in two different places - and those two different meaning could have different forms in other languages. Denormalizing translation database like that seems semantically incorrect (and strikes me as programmer laziness).

I agree that in general, more granular is worse for translations - there's too much risk your split will pierce the contextual whole that's required for some translations.

0 comments

2 comments · 2 top-level

rocqua9y ago

I'd expect this to happen when there is a split in the original case as well. E.g. you need to translate the template and the names. They are split in the original already, so they are translated as a split.

The same contextual issue then arises in the original, but apparently the designers thought the trade-of was worth it.

masklinn9y ago

> I never understood why people think this is a good idea.

It makes for a more readable, comprehensible source and searchable source. It's also often possible to dispatch on location additionally to text (PO files store both).

j / k navigate · click thread line to collapse