Thank you! Is it with bbPress 1.0 possible to register users with Swedish names like Göran?
Answer to my post about Swedish names: https://bbpress.org/forums/topic/swedish-names-for-users-wanted#post-39020
In the translation I want to change a word. It states:
“Registrera dig eller logga in – sullat bort lösenordet? ” where the word “sullat” is very unusal and not understandable to many people. How can I replace it with “tappat” ?
I managed to find the word “sullat” in sv_SE.mo and changed it to “tappat”, saved the changed file and uploaded it and it worked fine.
But when a new user get the password the text looks like this:
“Ditt användarnamn är: åke-örjan
Ditt lösenord är: ••••••••••”
It seems ok in the sv_SE.mo file but is not ok when it reaches the user. What is the problem and how can it be fixed?
.mo files cannot be directly edited, you need to use a tool like poedit http://www.poedit.net/ to correct the .po file and then compile it to .mo
I opened the .mo file and changed “sullat” to “tappat” in it using a text editor and saved the change and uploaded it and ir worked. It should perhaps not have been possible but it was!
The second part of my question now seems strange since I pasted what in my e-mail looked like Ditt användarnamn är: Gran Lindgren but it displayed correctly here!
Editing the .mo file directly is possible but hardly recommended. I’ll make sure to change “sullat” to “tappat” my next update of the files though.
The ä things are called HTML character entities. I use them to make sure the correct characters will show up regardless of character encoding difficulties. However, not all (but most) e-mail clients parse this HTML, so they may show up in their &-form. Have you experienced this?
This language file causes RSS for forums not to work. And also translations for month, days, years, seconds etc.. doesn’t seem to be translated at all. :f
Running bbPress 1.01.
http://www.callofduty.se/forum/
@tommiehansen: You’re right about the RSS feeds. Strange… I will look into it. Broken RSS feeds are not OK!
However, my time units are translated and the translation file definitely includes translation of those. You seem to have customized the Kakumei theme for your forum – are you sure that the months etc are wrapped in the translation function; __() or _e()?
RSS problem fixed: it did not approve of the HTML entities. Considering Göran’s problem above, I thought it best to simply replace all HTML entities of åäöÅÄÖ with their “real” characters. It works for me, and you people can download it at http://dropbox.jobjorn.se/bbpress-sv_SE.zip
@plrk: Got your E-mail. I actually do have this thread as a favorite, thanks anyway for the update though! (I wished this forum had the E-mail notification option…)
It works! Thanks!
However my time-relevant php aren’t translated still. The strange thing is that those functions aren’t touched at all. I’ll have to dig again to see if there are any errors related to the __ -stuff. One would think the default theme wouldn’t have any problem with the translations(?) 
My theme is based on the default theme, and it works like a charm… It could be that you have based your theme on an older version of Kakumei that did not use the translation functions everywhere.
Yeah, probably. I’m trying to figure out now how to translate the topic_time(); -function. The _e(‘Some Text’) is quite understandable, don’t get how to translate a function yet though. I’ve never messed around with translations at all (obviously).
Dear plrk I downloaded your latest .mo-file and it solved my problem with ugly letters for Swedish characters. Thank you!
It is still “sullat” but I now know how to change that. And did so. However I also have English words for months. I do not know how to change that.
My almost good enough forum is at http://www.32astolf.se/forum/
@Göran: It’s “great” that you have the same problem. Then it probably isn’t some server config hidden away somewhere and the problem will probably be solved pretty soon. 
Edit: Hm.. when i try to edit the languagefile with Poedit and choose to save it i get 3 fatal errors;
23:04:20: F:Skrivbordetsv_SE.po:191: message catalog has plural form translations...
23:04:20: F:Skrivbordetsv_SE.po:2: ...but header entry lacks a "plural=EXPRESSION" attribute
23:04:20: F:Skrivbordetsv_SE.po:191: message catalog has plural form translations...
23:04:20: F:Skrivbordetsv_SE.po:2: ...but header entry lacks a "nplurals=INTEGER" attribute
23:04:20: F:Skrivbordetsv_SE.po:617: 'msgstr' is not a valid PHP format string, unlike 'msgid'. Reason: In the directive number 1, the character 'a' is not a valid conversion specifier.
23:04:20: msgfmt: found 3 fatal errors
Maybe it’s related?
Update 2:
Tried a Bulgarian translation and it did translate time. It must be something with 1.0+ that isn’t in 0.9 language wise.
It was simply wrong in the id for the translations. I noticed it when i compared it to the bulgarian translation with a little help of EditPlus. I also changed some misspellings and added some of my own flavour to it all.
Changes:
– Time format numbering fixed
– Wrongly entered php-variables fixed
– Tråd / Trådar / Tråden > Ämne / Detta ämne (or ‘ämnet’) / Ämnen
– Posta / Postad etc. > Skriv, Skrivet etc.
– Fräschhet > Färskhet
– Titel > Rubrik
– Tagg / Taggar > Etikett / Etiketter
…and some other stuff.
Download:
http://www.callofduty.se/0-gzgrejjer/bbPress_swedish_language_files_by_plrk_and_tommie_hansen.zip
.
NOTE to others. You must change lines for the time specific translations. I’ve tried several of other translations that doesn’t do it correct either.
Example; Year = bb-includes/functions.bb-core.php:385
You can use the linked langage .po-file or check the Bulgarian one out for further reference. It easiest to check the .po-file for line references with a text editor like EditPlus, TextMate or Notepad.
Thanks Tommie! My forum looks better and better thanks to you and plrk.
A small suggested change in the registration form: “Position” should be changed to “Plats”.
I use bbPress 1.0.1. To make it possible for users to register with Swedish or other non-acii names I use Cyrillian Nickname http://bbpress.ru/downloads/plugins/
To prevent spam robots I also use Human Test available at https://bbpress.org/plugins/topic/human-test/ I have translated the few phrases in the plugin. Write me a pm if you want it (I tried to make it available at my site but could not place a php-file there. Should it be zipped?)
I have incorporated Tommie’s metadata changes into the translation file I’ve made (and changed “sullat” to tappat”). Both .po and .mo files are still available at http://dropbox.jobjorn.se/bbpress-sv_SE.zip
There are a few differences between my translation file and Tommie’s – mainly, his file uses “etikett” and “ämne” where I use “tagg” and “tråd” (the corresponding english words are “tag” and “topic”/”thread”). There are a few other differences, too.
I’ve uploaded a diff file for the really curious: http://dropbox.jobjorn.se/tommievsplrk.diff
Hello, I have a working translation for bbPress 1.0.2, and Im having the topic_time() issue too.
It doesnt translate into my local language, even though months, days etc, are translated in the lang file.
When I use _e(‘something to translate’) everything is fine, but calling directly topic_time() doesnt translate anything.
How do I wrap topic_time() into _e() ? or… what is the correct way to translate time?
Dukessa: unfortunately, _e() (and __()) attempts to translate the string it is given – which means that if you try to call “_e(topic_time())”, it will be interpreted as “_e(“August 12, 2009″)” (or whatever topic_time() outputs). The solution is to put translation functions inside the topic_time() function. Note however, that that would indeed translate “August” into “Augusti”, but it won’t fix the order (it’ll still go “month day, year”) nor the capitalization (in Swedish, months are spelled with lowercase first letter unless in the beginning of a sentence). In WordPress, the order problem is solved by an admin setting for the date format, but the capitalization issue remains.
I hope that explains it. If I have the time some day, I’ll try to submit a patch for it to be fixed in the next version.
