- This topic has 43 replies, 3 voices, and was last updated 15 years, 10 months ago by
.
-
Posts
-
Anyway… Slimbox2 looks awesome in Spanish! I have it over at my blog and it works like a charm – recognizes the WP language, picks the strings, shows ’em… Great! Thanks, malcalevak, for your hard work making it all come together! I hope the plugin now gets more used among Spanish speakers, too, and that other translators chip in.
Added later: spoke probably too soon… I was looking at the version that I had "hacked" manually, including the strings literally with sanitized HTML entities. Well, it’s still looking nice.
It looks the same, to the best of my knowledge anyway, in the localized plugin. I haven’t released it because I was going to add another option to enable or disable caching of the autoload script, but I haven’t decided if I’m going to keep it in or not.
I think for now I’m going to cut it (and disable caching) until I understand JS caching a bit more, especially since the autoload script is the least logical to cache.
So I should have the localized release, as well as your translation, out later tonight (EST).
Ok, I was a bit late getting around to it, especially when you consider the coding was essentially done half a week ago, but v0.9.4 with localization support has been released!
It works!!! Wonderful. Probably because I had the English version running, uploading the new version with Spanish didn’t entirely flush the previously active English values but after revisiting all options and updating them, the whole thing came up beautifully. To wit: <a href="http://nv1962.net/2009/01/24/probando-wp-slimbox2-en-espanol/">el demo</a>! (<s>not keeping the pics up beyond the weekend, it’s just to show it works</s> – ah why not… So there, a demo in Spanish.)
Question though: why put images in separate folders? Since the language ones are identified by the suffix, and their names are "hard set" in the .mo and .po files as well, they could very well sit in the same images folder as the English versions, no? Not really a problem, but it might be confusing to have separate image folders for each and every language… Just a thought.
Most importantly: <b>THANK YOU</b> for making Slimbox2 ready to speak Spanish, and whichever other language that comes its way!
It’s a productive day today – just earlier, I managed to make the <a href="https://geek.hellyer.kiwi/forum/http://localhost/phpBB3/viewtopic.php?p=3417#p3417">MLNP work in Spanish</a>, too… Woohoo!
Added PS: The "Update options" button still shows in English. Oh well.
I decided on separate image folders to make it easier for people to delete the images they didn’t want. I suppose I could’ve also required image names have the language image identified by a suffix, making it easier to sort without directories, but this way just seems a bit less cluttered to me. Now, if we had say… 10 languages, instead of just 1 additional language, if someone wanted to declutter their folder they’d just select all the folders that weren’t for their language and delete.
I would’ve preferred to actually put the images in with the PO and MO files, but that folder didn’t (to the best of my knowledge) allow you to put each language package in a separate sub-folder.
Admittedly, 90% of users aren’t likely to even look at the folders, if it works for them, and it’s in their language, they’ll probably be content.
Also, the default plugin values are only created if you’re installing the plugin fresh. I can’t think of any functional way to get around that, but it’s minor.
And you’re right about the "Update Options"…not sure why that is, the PO has the translation, and I’m pretty sure it’s coded correctly. I’ll have to figure out what’s up. Thanks for pointing that out.
I figured out the "Update Options" problem. Somehow I forgot to add the textdomain. I’ve added it back in, but figured it was so minor it didn’t really warrant an official new release.
For those who’ve already downloaded 0.9.4.1 and really want it, they can manually update, for the rest they’ll download the fixed version.And I just noticed that your localized images aren’t showing up (but they are in my version).
Looking at your CSS and JS, they appear to be old versions. You aren’t by any chance using some sort of local caching, or something, are you?Yes I am: WP Super Cache. I’ve just cleared the cache (again, just in case) but I’m not sure how that interferes with showing the JS images… I’ve just checked on 3 different machines, they show the "correct" stuff. Um… Aren’t <i>you</i> perchance looking at cached content? To be absolutely certain I’ve changed the images (you should see 12 now) but on my end it shows up fine – in Spanish, with assigned Prev/Next keys… Weird.
It’s showing correctly now. If it was caching the old JS and CSS then the code that points to the new images wouldn’t load. It’s also possible I’d cached an old version of the autoload script, since when I flushed the local script it was showing too (that’s part of why I felt the need to disable caching of it, at least for now).
Ugh… And that’s where I find a typo… Enclosed corrected version, for the next upstream – with my apologies.
(Added later: it’s also not so good to forget to make the .mo file and include it – fixed now)
Assuming I did it all correctly, the latest developmental version: here[/url:2fngo1wl]
Should function and support RTL languages, provided the proper language variable (LTR) is set. It’s also got your ES typo corrections, uses Slimbox 2.02, and resolves the tiling issues in IE6 when you don’t move the mouse.If someone can give it a shot and let me know if it works for you I’d appreciate it.
Looks like <a href="http://nv1962.net/2009/01/24/probando-wp-slimbox2-en-espanol/">it’s working fine</a>! Unfortunately, I can only show the Spanish version…
- You must be logged in to reply to this topic.