The French PO file was put on the Wiki this week-end.
http://wiki.wordpress.org/index.php/fr.po
Feel free to proofread/comment/criticize/modify...
Going the Gettext route is in my opinion the best way.
I'm waiting for the other POT files... ;)
This is really nice: the first POT file has the strings that show up to the reader, inlcuding titles in achor tags. Very nice.
it's official i'm a bimbo.
how do i get into the wiki to leave a swedish translation .po.
any and all tips gratefully received.
-father of pip.
See WordPress Localization. This isn't quite ready for translators yet. We're still marking and tweaking strings.
Ryan is right. Sorry to jump the gun, I'm just a little excited.
Ah, still tweaking ?
Well, hopefully there will be a warning when the POT files are deemed "complete".
Ok, I'll hold fire on the sv translation until an anouncement regarding a finalised pot is made.
cheers-r.
ps.
how do you lay them up on the wiki? - r.
Hey allusion, I didn't even see your first post. I thought people just noticed the POT files and started commenting. We've marked strings in index.php, wp-comments.php, wp-comments-popup.php, and everything I could find in wp-includes. I haven't marked anything in admin yet. If someone wants to take a shot at marking strings in the source, go for it. allusion's been revamping the options pages lately, so I've avoided marking them. But, I think he is done. Matt, should we start marking the admin interface and the options pages?
Go for it.
Although nothing but a text editor is required to translate Wordpress, having the gettext tools can be handy. They allow you to easily merge new strings from the POT into your PO and create MO files for testing. If you run Linux or BSD, gettext comes with your distribution. For Windows, go here. gettext is also available for OS X. Darwin is BSD after all. I'm investigating setting up a web-based PO translation tool like Kartouche. It uses PHP and MySQL. It may be overkill for a one POT file project like Wordpress, however.
Oops, forgot to login. That was me.
We've started marking strings in the admin interface. There's still more yet to do, but here's the latest POT for everyone to look over.
Thanks rboren, just what I was looking for
French PO updated accordingly, awaiting reviews, proofreading, comments, flames, praises, whatever suits you...
http://wiki.wordpress.org/index.php/fr.po
afternoon all,
working on the latest aditions to the .pot for the swedish localization. here's a question:
(tags are stripped)
Usual settings for an article: (These settings may be overidden for individual articles.)
rather than just assuming that article is synonymous with post i'm asking if it is?
cheers-father of pip
Just a quick not about the .pot (and hence wp)
this:
msgid "GMT time is:"
is incorrect grammar, 'time' is superfluous, 'is' suffices.
cheers-father of pip.
ha!
nobody's perfect:
msgid "GMT time is:"
forgot backticks.
cheers-fp.
added se.po to the wiki.
will update as furtherstrings are added.
if youare or know of a swedish user with time to kill, pop over to cast a beady.
cheers-r.
I recommend that everyone get a copy of poedit. It is a cross-platform PO editor and validator. A Windows download is available here.
poedit will merge new strings from the POT file into your PO and produce a MO file that you can save to wp-includes/languages so that you can see your translation in action. When using poedit, please fill in the "Project Info" page available via the "Catalog->Settings" dropdown menu. Most importantly, you need to set the country, language, and character set. In almost all cases, the character set should be utf-8.
Also, when translating a string that has one or more "%s" format specifiers in it, your translated string must contain all of those "%s" somewhere. If there are two %s in the english string, there must be two %s in your translation of that string. poedit will give you warnings for any strings that do not have the proper number of %s.
BTW, once you save the .mo file produced by PO edit, copy it to the wp-includes/languages directory of your WP installation. After that, set the $locale line at the top of wp-includes/wp-l10n.php to your locale rather than en_US. For example:
$locale
= 'fr';
This will tell WP to load wp-includes/languages/fr.mo
Anyone knows of poedit or equivalent for Mac OS X ?
fatherofpip : regarding your question in http://wiki.wordpress.org/index.php/se.po :
"Questions arising during the .se translation:
One main one as yet, the use of 'post' and 'article'
as noun and both 'publish' and 'post' used as verb.
If the devs have no issue with it I'll be unifying
usage for a clearer translation for the Swedish text."
I had the very same concern, but chose to translate both "post" and "article" into the same "billet" in fr.po (http://wiki.wordpress.org/index.php/fr.po), without asking as it seemed obvious enough to me. Same with "publish" and "post" which I translated into "publier". Of course, if the WPTeam insists on having a distinction, I'll correct my translations to separate meanings...
Note aux français qui lisent : ma traduction n'est pas définitive ni parfaite, et forcément sujette à débat. N'hésitez pas à émettre un avis! :)
rboren:
1) I'll download poEdit and will link the .mo file near (or from) the .po file once it's done (not before this week-end), but we have to make sure the .po files are on the wiki in order to allow reviewing from other people.
2) What should we as package name in "Project-Id-Version: PACKAGE VERSION\n" ? "WordPress 1.2" ? Same for the few first lines of the file.
3) Is the POT file in its final stage ? ;)
michel_v, MrPeer, MaximePiché et les autres, si vous pouviez jeter un oeil à fr.po...
@xibe
i've pretty much decided to unify post/article as 'artikel' and post/publish as 'publicera'; post in swedish can mean mail and post (as in a db), publish and article seem to jell with wp blurb a touch more.
as you say, none of the translations are perfect and most translations benefit from 'two headsa re better than one'.
-fatherofpip
fatherofpip : I just took a quick glance at se.po, and I think there is one thing you missed. I might be wrong about it, but that's how I understood the POT file, so there:
It seems all lines must be at most 80 characters long. If your line (including msgstr) is <80, then you can use
msgstr "my short translation bla bla", but
but if it's >80, then go
msgstr ""
"my looooooooooooooooong translation"
"is gonna be finished when"
"i’m done"
...with the last " of each line being at most the 80th character.
I guess using a PO editor would help in better maintaining the file, rather than going all Notepad on it.
Can the devs confirm this ?
Also, I stumbled upon this in se.po:
#: wp-admin/post.php:727
msgid ""
"<h3>WordPress bookmarklet</h3>\n"
"You can drag the following link to your links bar or add it to your "
"bookmarks and when you \"Uttrycka det\" it will open up a
(...)
msgstr ""
"<h3>WordPress bokmärkesverktyg</h3>\n"
"Du kan dra och släpp följand länk på din browser, på länkraden, eller spara den i "
"favoriter/bokmärke. När du \"Press it\" öppnas ett popup
(...)
Didn't you invert "Press it" and "Uttrycka det" here ? ;)
cheers
certainly did-nice catch :-)
didn't know about the 80ch. limit i'll be fiddling with poedit this afternoon on a break and i'm sure it'll pop up there.
thanks for the heads up.
cheers-fatherofpip.
just been tinkering with poedit, sweet, very sweet.
brought in the latest .pot barebones and started reworking the translation. in the status at the bottom it counts off the tokens (42 bad tokens reduces as they're translated) though gives only a total rather than line specific counts. only he says. useful for keeping tabs. can't find any reference to line length in poedit itself and no warnings popped up on test line translations.
@rboren, can you confirm or deny the 80 character max for line length ?
i'll finish off the .po in the program, drawing in new strings as they're posted (neat little option under 'catalog' in the menu) trying the .mo in the latest nightly.
another neat little thing is the ability to make individual strings fuzzy if the translation is suspect, gets highlighted in yellow and bumped to the top of the list.
there's no auto save, but do it yourself and discover the added benefit of all translated strings being moved down the order, leaving work to do free, except bumped fuzzies.
bumped fuzzies??
time to go.
cheers-fatherofpip
80 characters per line is not a hard limit, but it is nice to keep lines under 80. Let's try to stay under 80 and break long lines into multiple lines.
I'll be changing some of the strings that have multiple %s in them. I need to switch to %1$s, %2$s, ... so that translators can change the order the %s occur in the string. See here and here for details. This won't affect many strings, but be on the look out for changes.
hi.
ok, i'll check the 80 character breaks when the job's done, seems logical.
here's a taster of wp in swedish. open the comment for a bit more. i'll provide a user login for a peep at the backend when i get a moment.
.mo's get ftp'd as i finish a session.
cheers-r.
Awesome.
Since this thread discusses two different translation frameworks and has gotten rather unwieldy, let's continue over here.
« Previous 1 2 3 4 Next »
This topic has been closed to new replies.