Closed jeremypw closed 1 month ago
I really feel that this should be reworked to take into account two things for i18n:
ngettext()
One can't assume that every language will do a "$PREFIX$UNIT"
Do you mean that some languages will have "$UNIT$PREFIX"? That can be handled by the translation can't it? If you mean some languages will have a completely different single word for e.g. "centimeter" then that is a harder problem. We cannot really provide separate translations for all possible combinations.
One has to take plural into account and use ngettext()
The information in brackets "(
Closing as outdated and stalled.
Fixes #552
Rather than using the context translation function
NC_()
to mark array initialisers as translatable (which does not seem to result in any new entries in the.po
files for some reason), the more usualN_()
function is used and the context provided withTRANSLATOR
comments.Missing translation functions on the output are provided. The possibility of translating the SI prefixes is also implemented.