Comment form can't be translated

[Eddie]

Hi, I noticed, that although much of comment handling can be internationalized, at least comment form can't be (strings like "Add comment", "Save user info" etc.) I wonder why? This is not template specific and most of templates will use it. It wouldn't be very hard to add few variables ...

[Dkozikowski+]

These are template specific.

templates/simple/comment_template.html

[Eddie]

But why? Every template (which contains comments) have some sort of this. It's strange that one part of comment system can be translated and the other can't.

[Dkozikowski+]

Everything can be translated just not everything is contained within a language file.

[Eddie]

I thought that language file should contain phrases common for all (or most) templates. And comment form is surely *very* common component. I dare to say it is used in all templates.

90% of people use Pixelpost out of the box and do not use customized templates (moreover, there aren't all language versions of all templates).

[Dkozikowski+]

There is no need for every variable to be within a language file.

The only variables Pixelpost places within the language file(s) are the ones that would require you to edit core pixelpost code if such a file never existed.

So, Pixelpost provides the users with a simple method of localizing the core pixelpost code via a language file and any other translations that are not contained within the core code will be found inside the template files.

[austriaka+]

Eddie, you are right, most people use Pixelpost out of the box but most people using Pixelpost are native English ;-)

To be honest, people using Pixelpost are supposed to do some slight changes within their templates which come as basic examples for a good design and nothing more.
It is not difficult to change some text within a html file, it is not only "Add comment" or "Save user info" but also things like "browse", "about", "home" or "I will eventually put some information about myself or my photography here. For now, please just enjoy the photos."
So all static text blocks are to be changed within the templates and all phrases generated by Pixelpost can be changed within the language files.

[Eddie]

Originally Posted by austriaka

Eddie, you are right, most people use Pixelpost out of the box but most people using Pixelpost are native English ;-)

That's hard to prove ...

Originally Posted by austriaka

So all static text blocks are to be changed within the templates and all phrases generated by Pixelpost can be changed within the language files.

I understand this attitude, but I'm not sure it's the right way.

Of course, there is possible workaround. If I translate official templates (horizon and simple), would be possible to include them into official release? I looked into sources and there seems to be mechanism to use localized version of template.

[GeoS+]

Originally Posted by Eddie

Of course, there is possible workaround. If I translate official templates (horizon and simple), would be possible to include them into official release? I looked into sources and there seems to be mechanism to use localized version of template.

The best would be to post it in Extend section of site as translated template files are not part of main distribution.

[Dennis+]

I agree with GeoS on this one. Translated templates are not part of the distribution. As for the decision to use default English, this is because the main language on the internet is English.