Hello,

I just started translation to german.

I'm new to poedit and translating Wordpress so I got stucked on some parts ...

First thing leading to confusion is, that some of the translation have to be done within the config at the dashboard (for the line with date, Tags, Comments, ...) and some in the .mo file.

wouldn't it be better if the parts like "One comment", "% comments", "Comments are closed.", dateformat could be done once in the .mo?

You could see the progress at www.lelei.de if you like.

I'll focus on translating the frontend - wich isn't very much ... but it is splitted to the language file and the online config ...

Looks good...

I guess you had to change the post footer info on the theme options page and couldn't include them in the .mo file

I just realized that the comment options in bfa_theme_options.php aren't localized yet, that's probably the redundancy you mean? I'll put that on my todo list for 3.2 together with "Yes" and "No" etc. in the theme options.

So... at this stage a German user would have to manually edit the default (English) comment links in post footers on the theme options page.

Many parts like the "Comments", "One Comment", .... isn't even in the languag file - it is only in the online configuration.

Is their a way to export/import the "online config", cause I have several blogs I would basicly rund with the same config ...

There is no import/export function for the theme options yet. You could export the whole blog via the Wordpress export function, that would include the options but also the content

I have a problem to translate following:

%1$s to %2$s

it means like

x comments to title

How do I mange it to get

Ein Kommentar zu title
X Kommentare zu title

At that point you should just translate the "to" part of %1$s to %2$si.e.

%1$s zu %2$s

the contents of the variables would be translated separately (they should appear somewhere in the translation file)

At least that's how it's supposed to be, and as far as I understand

I see - I only have trouble with more than 1 comment

PHP Code:

<?php // Comment Area Title 
    printf(__('%1$s to %2$s', 'atahualpa'), comments_number(__('No Comments', 'atahualpa'), __('1 Comment', 'atahualpa'), __ngettext('% comment', '% comments', get_comments_number(), 'atahualpa')), get_the_title());
    ?>

this is the php Part in comments.php

I translated every single "comments" in the language file.

If I change that to

PHP Code:

<?php // Comment Area Title 
    printf(__('%1$s to %2$s', 'atahualpa'), comments_number(__('No Comments', 'atahualpa'), __('1 Comment', 'atahualpa'), __ngettext('% comment', '% Kommentare', get_comments_number(), 'atahualpa')), get_the_title());
    ?>

everything is fine ... but that's not supposed to be this way?

Don't you get these strings separately in the translation file:

%1$s to %2$s

No Comments

1 Comment

% comment

% comments


The plural part is split into %comment and %comments for languages with more than 1 plural case

That solution suggested by you would mean to hardcode the German string as i understand it

Originally Posted by Flynn

Don't you get these strings separately in the translation file:

%1$s to %2$s - "%1$s zu %2$s"

No Comments - "Keine Kommentare"

1 Comment - "Ein Kommentar"

% comment - no not found

% comments - no not found

I just redownloaded all files and verified with my poedit I can not find any "% comment" or "% comments"

You're right. I am sorry for that. Looking to find a fix quickly

no worries ... I hope I will not lose my current translation ... I'm not the fit with poedit ...

I am neither. I got it to show %comment and %comments now but it's not showing the corresponding translation fields. I should have it until tomorrow

I will probably just drop that "dual plural case" option. I looked into another theme that's translated into almost 40 languages and it doesn't have that feature either even though it's translated into czech, too

now the filename is atahualpa.pot _(3.1.7) not .po anymore - does it make any difference?

while edit the atahualpa.po (I just renamed that file) I receive 3 fatal errors (without editing anything - just save as de_DE)

09:02:24: C:\Users\xyz\Downloads\Wordpress\atahualpa317\atah ualpa3\de_DE.po:10: keyword "Content" unknown
09:02:24: C:\Users\xyz\Downloads\Wordpress\atahualpa317\atah ualpa3\de_DE.po:10:10: syntax error
09:02:24: C:\Users\xyz\Downloads\Wordpress\atahualpa317\atah ualpa3\de_DE.po:11: end-of-line within string
09:02:24: msgfmt: found 3 fatal errors

File save as de_DE.mo but will not save as de_DE.mo

If I try to follow the readme-languages I stuck with point 2

2) Choose new catalog from pot file and select atahualpa.pot

I receive 7 Fatal errors ... most of them like keyword "xyz" unknown ...

Sorry I didn't check the .pot file, it seems that last minute changes were not included. I have attached a new atahualpa.pot file in this post. The .pot file is supposed to be the base file that is not linked to any specific language.

I have tested the attached .pot file and it seems o.k. except that it throws one error while saving for "% comments" if it's translated to "% Kommentare". Could you just save the de_DE.po regardless and see if the resulting de_DE.mo file works on a german blog?


It should work like this:

In PoEdit:

"New catalog from pot file", choose "atahualpa.pot"

Fill out "Project Info" except plural forms:
Atahualpa Deutsch or similar, Your name, Your email, German, Germany, UTF-8, UTF-8
(not sure if iso-8859-1 would be better as German "charset" but UTF-8 should cover everything?)

The other two tabs (paths, keywords) should not be required

Save as "de_DE.po" (or, whatever the Wordpress extension for the given language is: http://codex.wordpress.org/WordPress_Localization

With PoEdit's default setting this would also create a "de_DE.mo" along with the "de_DE.po" file. "de_DE.mo" is the compiled file that would be included with the theme.

Translate and click "Save" before closing PoEdit

Unlikely but just in case:

Open de_DE.po and make sure the terms don't have paths from your local computer such as
#: C:\wordpress\theme-translations\atahualpa3\_atahualpa3.1.7/comments-paged.php:3

It should be more like this:
#: comments-paged.php:3

I think I'm finished with the translation - you may have a look at www.lelei.de - what should I do with the file now?

Great, looks good. Could you send the .mo file to the email address that's in the .pot file? Also include a website URL and name (of you or your website) that I should use for the credits.

Thank you for the translation, and sorry for the trouble you had

done ... great theme

Looks good…… I want to translated your file. chinese translation

I there a german translation file availible for Atahualpa Version 3.3.2?

Thanks, curious

Not yet it seems but you could attempt to build your own, you'd need the atahualpa.pot file that is included with the theme and the free software POEdit. It is fairly easy to do.

Just started translating the theme to German manually when I wondered why 3.2 was already... so I found this forum... I'll ask curious if he is going to translate; if he is not, I'll do. This theme is too good to be discarded by anyone because it's not available in German.

I translated that theme already - but some parts are need to be changed in the backend manualy.

I fixed some little bugs in my german translation for Atahualpa 3.4.2:

Comment field: from "6. Juli 2009 bei 22:43" to "6. Juli 2009 um 22:43"

and "Bisher noch keine Kommentare zuXXXX" to "Bisher noch keine Kommentare zu: XXX"


Have fun using it!

sorry, i did not understand the point with the comment,
actually all my translation is fine - i used that pod software,
the only problem i have is, if there is only one comment, it shows:

1 Kommentar zuTitel des Posts

so that means no space between "zu" and "Titel des Posts" - looks like: zuTitel des Posts

not nice, and i did not find the place to change that,

in my de_DE.po it is like this:

#: comments-paged.php:27
#: comments.php:17
#: legacy.comments.php:24
msgid "1 comment to "
msgstr "1 Kommentar zu: "

i do not find another place ?

if more than one comment is there, everything is fine,

i am thank fool for any help on this case, maybe its not so difficult,
oh i forgot; i am using Atahualpa 3.3.2

regards from Berlin