Some questions and some issues

[Dennis+]

klimin_a_s contacted me on ICQ with some questions about Pixelpost 1.6.

First problem: Tags with Russian symbols do not saves.

tags must have normal alphabetic names, so Russian, Polski, German are all languages effected by this. Reason: we are working on something which has the tag in the url. Special characters are not allowed in an url.

2. Second: In the comments admin area (index.php?view=comments) field "Name:" shows incorrect symbols instead of Russian sybmols. But the fields "Comment:" and "Image:" works fine...

This sounds like a language issue. Please check the russian language files.

3. Third: I plan update my custom fields addon. There are an alternative fields in the database, and I want to modify this addon to support of the bilingual feature of 1.6. How I can read information by PHP about which language is set in the current session? If the GET parameter is defined (lang=XX), then OK. But in the URL this parameter may be dismissed. How can I recognize the current language?

I'll have to come back on that one. I believe I set a cookie somewhere with the language tag. If there is no cookie, use default, else use alternative

4. Fourth: It is reasonable to make an alt. photoblog name in the options (and tag <ALT_SITE_TITLE>). But this problem can be solved in the template... But the tag <SITE_TITLE> is senseless in that case. This is a minor problem, nevertheless.

Alternative title could be considered but probably won't be done after the final release of 1.6

5. I think, the RSS-functionality will be more better if user (admin) can use all rss-styles simultaneously. Now you can select one RSS-style (Show fullzise pictures, Show thumbnails, Show text only). But if you make available using all these styles at the same time, whis will be great! For example,

http://<DOMAIN>/index.php?x=rss_thumb
http://<DOMAIN>/index.php?x=rss_textonly
http://<DOMAIN>/index.php?x=rss_fullsize

Some people likes text-only feeds, some people likes fullsize or thumbnails...

this is probably a better task for an addon

6.6. I guess, only main (non-alternative) language can be used as admin language?

It is already on our todo list. We're not sure it will make it in version 1.6 final (we need some stuff for 1.7)

[Dennis+]

About the language question:

Please check if both $_COOKIE['lang'] and $_GET['lang']

[klimin_a_s]

Originally Posted by schonhose

tags must have normal alphabetic names, so Russian, Polski, German are all languages effected by this. Reason: we are working on something which has the tag in the url. Special characters are not allowed in an url.

Ok, but the russian symbols can be used in the URLs (for example, wikipedia can recognize russian words in the URLs, for example: http://ru.wikipedia.org/wiki/Фотоблог

Originally Posted by schonhose

This sounds like a language issue. Please check the russian language files.

This is not a language issue. Why other fields shows correctly? Only field "Name" is corrupted.

See these screenshots: (both Name and Comment text lines identical):

a) Frontpage, fragment of the comment. Name=Comment.


b) Admin area, fragment of the information about comment. Note, the Name is corrupted!

Originally Posted by schonhose

About the language question:
Please check if both $_COOKIE['lang'] and $_GET['lang']

Ok, thank you!

Originally Posted by schonhose

Alternative title could be considered but probably won't be done after the final release of 1.6

Ok.

Originally Posted by schonhose

It is already on our todo list. We're not sure it will make it in version 1.6 final (we need some stuff for 1.7)

Ok.

[Dennis+]

Originally Posted by klimin_a_s

Ok, but the russian symbols can be used in the URLs (for example, wikipedia can recognize russian words in the URLs, for example: http://ru.wikipedia.org/wiki/Фотоблог

We had a chat about this:

GeoS: but this is the newest stuff related to regional domains, pretty "new" thing. I.e. you can register domain like ółęężćźżą but it is translated to a-zA-Z0-9... stuff. I havent seen URLs with non ASCII marks in it which wouldnt be translated

in Germany they tried to promote socalled "Umlaut-Domains"

so that people like me, whose familyname is not a name but a category (Müller, Meier, Schulze...) and whose familyname or other names have Umlauts, could register the corresponding domain

www.müller.de instead of www.mueller.de

in this case Microsoft IE was the best help against this bullshit, as this "browser" could not resolve these domains and so people restrained from using that...

funny, try www.müller.de , it belongs to a webdesigner, (and not to this big drugstore company "müller") ;=)
She was the fastest to register that...

but that's the first time that I see a domain like that...

[GeoS+]

All what I wanted to say is that still they are somehow stranslated.

Ive got docs about it in polish:
http://domeny.onet.pl/1209357,8481,poradnik.html

General thing which is there is:
example domain żółty.pl is translated to xn--w-uga1v8h.pl to be compatible with older webbrowsers and so on. Older browserws, like still quite popular IE 6.0, doesnt support it in URLs without additional plugins!!

Generally - still national marks in URLs are big problem.

[klimin_a_s]

The initial question was not consider a domain names <NON-ENGLISH-NAME>.XX (type #1), but the using non-english tags with Pixelpost installation (URL address like this: http://<PIXELPOST-URL>/index.php?tag=<NON-ENGLISH-TAG>) (type #2). Yes, IE6.0 haven't support of the first type of URL, but (sic!), IE6.0 can show URLs with non-english symbols of the parameters ($_GET) (second type of the URLs), for example, this URL!

So, I think, we can use tags with international symbols (theoretically).

[GeoS+]

It can just because it is:
http://ru.wikipedia.org/wiki/%D0%A4%...84%D0%B8%D1%8F

There is only one problem - in validation of tags. I was trying to get UTF8 tags validation but I didnt get success. Maybe I wasnt looking to deep. When whole stuff will be in UTF8 and only at archive in URLs there will be translation to URL compatible format (PHPs urlencode() function) then we can make one more try for it.

[Trauko]

b) Admin area, fragment of the information about comment. Note, the Name is corrupted!

Klimlin, I have the same problem, my language is spanish,




Have you found a solution?
I see data in field name of database is Ok.

Be happy, Good Pictures.

http://trauko.org/fotoblog

[Trauko]

To solve the problem, edit comments.php in folder admin

line 222 say

$name = htmlentities(pullout($row['name']));

changeto

$name = pullout($row['name']);

Be Happy

Thanks to Klimin for that fantastic Custom Field Addon
Thanks to PixelPost Team for that fantastic program