Once again I stumbled upon texts of Tikis admin GUI had resisted being translated, and later I found that nonprinting characters were hardcoded that will block tra() or tr() from pattern matching. Even spaces can block a translation. I won't make new bug reports for those, but rather use this one as sort of an umbrella bug report which I will amend with comments.
So the first new occurency of nonprinting characters that block translations is found on line 130 of /lib/prefs/tracker.php:
'description' => tr("Require users to fill in a tracker form if not done already by prompting them with a modal dialog "),
Those two spaces (yes, two, not one or three...) may look like a little glitch from a dev's perspective, but since they do not print, you cannot translate this string by copy & pasting from the GUI into custom.php giving a translation: The pattern matching cannot find it. There is a workaround, but this may not be so easy for translators with little experience and with small toolboxes (Windows comes with FAR less useful tools for this than Linux...), since if you encounter those, you have to grep through the entirety (!) of Tiki source code to find the origin of the string, to be able to look at it's source code, to be able to copy & paste from there...
filename | created | hits | comment | version | filetype | ||
---|---|---|---|---|---|---|---|
No attachments for this item |