Creating a translation of Tiki Wiki is a really arduous task, more like a project (I have spent more than half a month already, almost fulltime).
No one will want to do this more than once, at least I don't. The problem is, that in order to render a good translation, you have to see a text in it's context. The task is so tremendously labour intensive, because you have to backtrack clicking everything, activating everything, then deactivating everything, trying to provoke all errors etc. pp. et. al.
Now comes the problem of Tiki improvements. With every new release of Tiki, from the smallest bugfix to the biggest new release of a LTS possibly comes new text. And even correcting a single character that was part of a typo immediately leads to the translation vanishing into thin air because the pattern matching of tra() won't catch it any longer. The translation remains in the language file, but is never displayed again.
So everything will have to be re-checked., time and again.
Since Tiki Wiki does not have one file of text that resides in constants, you cannot simply generate a diff to see what has changed, and thus needs new (or altered) translations.
Therefore a tool would be necessary that extracts all text to be displayed. That tool could then also look up if there are pre-existing translations of those strings, and present them, too. As a side effect, such a tool could help developers to guard their code against strings NOT passed into tra() or tr (which makes translating them impossible).
In the first stage, such a tool could simply produce one file as output, in later development could be interactive. Such a tool would be a necessry prerequiste for version advancement of Tiki, because without it, all (!) translations are rendered into "status unknown" with any change of code.
Side remark: Such a tool does not necessarily have to be part of Tiki. It could make development easier it at first it would be stand-alone.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
Unable to connect to show.tikiwiki.org. Please let us know of the problem so that we can do something about it. Thanks.