There is localization available (although not for the most recent texts), cfr. http://svn.wp-plugins.org/autoptimize/tags/1.6.5/localization/. If you want to, you’re more then welcome to provide me with the po & mo-files for you language.
The fact that URL’s are somewhat … complicated is a necessity I’m afraid; we need a hash in there to make sure the aggregated CSS or JS for page A is different from the one on page K, we need .php (and not .js or .css) because there is logic in the files to handle different contexts (e.g. browsers and what they accept), cfr. the logic in the template.
here is translation to persian language link.
after i upload it to localization directory the plugin can not read it!
this problem is for all languages or it’s my mistake?
anyway it’s can be better if you add supported language to plugin description page like other plugin…
and about the css and js permalinks i just confused 🙂
but i think it’s better to keep .js and .css format…
regarding localization; I’ll check, didn’t really bother with that part of the code yet.
regarding css/js permalinks; the simple explanation: it has to be the way it is now for technical reasons 🙂
fa_IR seems to work for me, cfr. this screenshot (after adapting wp_config.php to define wplang as fa_IR off course).
I’ll make sure it’s in the next minor release and will contact you when I’ll update all translations (if that’s OK with you, off course).
no problem feel free to contact me anytime
