Andy,
Any chance you could just tell us the fix for RC1? I’ve spent days getting first Beta 1 and then RC 1 cleaned up for localization and redoing my language files. I’d really rather not start that process all over again with a trunk version.
A friend in Budapest and I have a Hungarian .mo based on 1.0b1 with only 2 untranslated strings, but there are so many unmarked strings in the code its hard to say how close we really are to being done. Hopefully there won’t be many new texts among the unmarked strings.
Thank you Martin – seems we share some of the same concerns. You’re working with one of the Scandinavian languages?
I’m starting again with 1.0 rc1 and will post results in trac. So far, I see many improvements in the area of localization. Thanks.
I’m assuming there’s no reason to upgrade from 1.0b1 to b2 first, rather than directly from b1 to rc1.
I’m starting again with 1.0 rc1 and will post results in trac. So far, I see many improvements in the area of localization. Thanks.
I’m assuming there’s no reason to upgrade from 1.0b1 to b2 first, rather than directly from b1 to rc1.
bp-core/bp-core-activation.php: 128, 129
bp-core/bp-core-ajax.php: 112
bp-core/bp-core-signup.php: 154, 243, 301
bp-core/directories/bp-core-directory-member.php: 105, 171
Sorry, I don’t have a good experience with the BuddyPress trac. I can stop here, if you prefer.
I have a Hungarian language install at http://unitarsalgo.unitarius-halo.net/ . I used BuddyPress 1.0b1 with WordPress MU 2.7 and bbPress 1.0 alpha. Hungarian language file is about 90% complete; I’ll make it available when its 100%. I’d say 1.0b1 was about 98% ready for use with other languages: I had to go through the files line by line to add missing get-text tags. Since I’m just finishing my 1.0b1 install, I think I’ll wait a bit before upgrading to beta 2. When I do I’ll be comparing my tweaked files to 1.0b2 files in ExamDiff to find changes I need to carry over; This time I’ll try to keep some notes so I can’t point the developers toward any remaining problems.
It is clear now that as long as I don’t try to translate the widget’s name that appears in the block header, the widget will display. Translating coded strings in the block content doesn’t seem to have any effect.
Of course, I will have to translate the widget name, but this would seem to point to where the problem is – some incompatibility between the header code and the UTF-8 coding for accented characters.
Where’s that tracker entry?
