Jason
Forum Replies Created
-
Forum: Requests and Feedback
In reply to: Localization: Help Needed!Well, things have paused temporarily because there’s been a little bit of discussion… everyone just wants to be sure that this is done the right way the first time.
Forum: Requests and Feedback
In reply to: Sub-Categories, at last, BUT….Just about finished with fixing the admin to use arrays instead of the DB. Once I’m statisfied it works, we’ll be all set.
TechGnome: Are you still experiencing slowdown from sub-cats? Looks to me like you’re back at .5-.6 seconds.Forum: Requests and Feedback
In reply to: Sub-Categories, at last, BUT….My testing of Miles and the nightly are as follows:
Miles: avg 0.027 seconds
nightly: avg 0.032 seconds
Of course, this is my test install which has only the default entry. I’ll work on doing some more in depth testing once I’ve added some dummy entries.Forum: Requests and Feedback
In reply to: Sub-Categories, at last, BUT….Seems the “none” option got lost for parent category… shouldn’t be too hard to fix.
I’ll take a look at the exclude problem this evening.
As for queries, we’re working at keeping them as low as possible…Forum: Requests and Feedback
In reply to: Localization: Help Needed!Hi all!
Quick update about localization. I talked with Matt last night, and he really likes the idea of localization, but he also sees the danger any sort of split could pose. For that reason, he’d like to get the groundwork for localization rolled out quickly, without a split
After tossing around a few ideas, the ultimate decision has been to go with a custom function (wp_translate) so that future changes to translation can all be handled in one spot. wp_translate will work with localization files that will (unfortunately) differ a bit from those currently being worked on in the wiki.
What does this mean? Well, the localization files in the wiki are good starts, and work can continue on them, but they will have to be converted to the new format at some point, so taking a break for a few days might be a good idea. Before conversion to the new format happens, though, I’m going to finish up the functions needed for translation and start swapping out the english from the current CVS versions of files. As soon as I have the beginnings of a new english localization file ready, I’ll make it available so translation can begin.Forum: Requests and Feedback
In reply to: Localization: Help Needed!Ok, I can see where you’re coming from, jules, and you have some good points. I think what we need is for the developers to let us know what they want to do.
Forum: Fixing WordPress
In reply to: Empty Categories are visible in miles 1.01I think the fix has finally been checked in, so the next release/beta/nightly should have it, I think…
Forum: Requests and Feedback
In reply to: Localization: Help Needed!gugus: The problem of setlocale could be avoided like this:
DO include wp-config-extra.php’s day names and month names in the translation files, ESPECIALLY (or only?) for languages that are less likely to be available for setlocale (such as Schwytzer Dytsch).
Then, make the use of setlocale an advanced option available in the backend, specified by the user, defaults to none. People who enable setlocale can use strftime, the rest still use date.
As for organizing a split, I think we’d have to talk to photomatt about that.Forum: Requests and Feedback
In reply to: Localization: Help Needed!Seems to me there should be a split here: 1.0.1 (after list_cats is fixed) should be used for localization, while regular development continues. Once localization is finished, the localized version should be caught up to the regular version, and then further development continued on the localized version.
As for including time/date formatting and wp-config-extra.php’s day names and month names in the translation files, I’ve created a custom WP-time/date formatting function that would eliminate the need for wp-config-extra.php’s translations. Basically, the custom function would allow you to use the formatting styles for either date() or strftime(), the latter being preferable for localized versions because with setlocale() in the localization file it would mean automatic translation of day/month names. I’ve mentioned it to photomatt, so maybe “1.0.1 Localized” is the place to roll this out.Forum: Fixing WordPress
In reply to: Empty categories visible in 1.0.1It’s a bug that will be fixed in the next release… it may already be fixed in the nightlies…
Forum: Requests and Feedback
In reply to: Localization: Help Needed!New wiki pages: lang_de and WordPressLocalization
Forum: Requests and Feedback
In reply to: Localization: Help Needed!Otsukare: Looking at the files, it seems there are a few things you are skipping/not translating. Is there a reason for this, or have you just missed some things?
Forum: Requests and Feedback
In reply to: Localization: Help Needed!I already started on a German localization, so I’ll just roll it into this project. 🙂
Forum: Fixing WordPress
In reply to: Problem with pagingdebwire: I know it says so in the wiki, but maybe posts_nav_link doesn’t go in the loop. Tried that?
Forum: Fixing WordPress
In reply to: 1.01 showing *all* category titles, even empty oneThis is a bug (empty cats showing, no entry count, no last post date), and I’m about to submit the fix for it.