[Eddie]

Originally Posted by Dennis

Well, here is food for thought: you might be correct that 1/6 of the internet population is a native English speaker. You can also consider that 8/10 of the internet population understands English. (interesting reading on the subject: http://www.cs.tut.fi/~jkorpela/lingua-franca.html)

So whether you like it or not, English is considered the standard language of the internet. By using English you will appeal to the largest chunk of the population.

There's no doubt that English is modern lingua franca. My only complaint is that other languages should not be ignored.

Originally Posted by Dennis

Now on to why we don't include localized templates. Where would this end? Consider this: we, as the crew, have to maintain the code and the templates. If we add just a couple of localized templates for the major languages we have to maintain them. I speak my languages fairly well, but there is no way I can maintain a Chinese or Spanish template. I hear you thinking: why not ask someone to do it for you? Yeah, great thinking there and certainly a possibility.

However, consider the time we need to approach each template maintainer, process the changes and update the template. Not to mention the time we probably need when a user contacts us with suggested translations for a template, which we also have to relay to the maintainer.

I understand it's not that easy. But as I understand, new release (1.X) is made approx. once a year. During beta stage (or when strings are considered frozen), somebody sends mail to language maintainer to update translation. If translation is not updated, it will not be included (although as you say, this is not so easy, but it's going to be fixed). Simple, effective. There's little work for you, developers. Just send one email and then accept translation updates. Once a year.

Originally Posted by Dennis

All in all this took about two months to collect all the translated files. As far as I'm concerned this isn't working. So what are we going to do? Well, one thought I have about it is to ship Pixelpost only with the English language. What will happen to the other languages? Good question: this is going to be the responsibility of the community. The community will maintain and make language packs.

This is also possible way. I plan to make (and maintain) independent package with fully translated czech interface (with little or no code changes).

Originally Posted by Dennis

This also has to be done for templates. Because I for one (and I reckon I don't stand alone on this) have no interest in a couple of dozen templates which I don't use.

I talk only about two templates included in official releases.

Originally Posted by Dennis

Also the remark you made earlier concerning the standard phrases in a template could be a real disaster template-wise. You need to have tags for every phrase, which have to be replaced by the core code, making the code slower and certainly does not make making a template easier (because of all the tags you have to use).

I talked about adding 10 - 20 more tags, IMHO there won't be big performance loss But if performance really matters, it would be easily compensated (e.g.) by replacing ereg_replace with str_replace where ereg_replace is not neccesary