Download & Extend
Node Gallery » Issues

arabic files ???

Posted by demonrage on October 7, 2011 at 3:53am
Project:Node Gallery
Version:6.x-3.0-beta2
Component:Language
Category:support request
Priority:normal
Assigned:Unassigned
Status:active

Issue Summary

hello,

i have configured the node gallery module to suit my website needs, and i have to say its marvelous module.
but when i try to upload an Arabic named photos it results with no name at all, lets say i have a file called (عربى.jpg) it will be after upload (.jpg) witch result in a bad view and experience for the user, have i missed some configuration, please guide me>

thx

Login or register to post comments

Comments

#1

Posted by dddave on October 7, 2011 at 12:35pm
Priority:critical» normal

http://drupal.org/project/transliteration

Are you using this module? If so does uploading normally works fine (with transliteration) but only not for NG?

#2

Posted by demonrage on October 7, 2011 at 9:57pm

i think main function of (transliteration) is to convert non English character files to English one, but what i want is to keep the Arabic file names as it is (Arabic), cause i use these names to describe the photos itself.

#3

Posted by dddave on October 8, 2011 at 8:42am

#1284838: Separate gallery name and gallery URL to support non-latin names is a similar issue.

I am not sure what NG can or should do to handle those situations. This could need some input from the main maintainers. One problem is that this is basically core/fielfield default behavior.

#4

Posted by dddave on October 10, 2011 at 7:42am

Would the solution mapped out in the other issue help you?

Second question: why is this issue set against beta2?

#5

Posted by demonrage on October 10, 2011 at 9:35pm

no it doesn't solve my problem
and this is the version i already use

#6

Posted by dddave on October 11, 2011 at 7:53am

So then:
You are not using the latest aka best version of NG (but this won't save your problem most likely). But opening a support request and NOT using the recommended release can make things pretty hard. How do we know that the problem is still present in the recommended release?

Secondly: If the problem is still present in the latest release (most likely), I don't know what we could do here because this is more or less core behavior. Until one of the maintainer chimes in or someone else can map out a solution I fear you have to stand in the rain.

#7

Posted by demonrage on October 12, 2011 at 6:34pm

i have updated to latest release, same problem.
i think u r right, it could be related to the core itself, i only need someone to show me the way, where to search, what needed to be tweaked, i like rain already but not all the time :P

#8

Posted by demonrage on October 26, 2011 at 6:13am

still no clue how to do this, any ideas ??