Translating Atahualpa 3 - Please read before translating
Please send your .mo plus the .po file to the email that is included in atahualpa.pot along with URL & name for a credit link, or attach it in a post here in this thread
The .po file will not be included with the theme but I need it to do small changes if i.e. line numbers change in a new Atahualpa version. PoEdit might throw an error related to "% comments to" while you try to save the result but it should work regardless if you just ignore that and save the file. I'll try to fix that annoyance in the next release. If you're unsure as to how to name your file (Example: de_DE.po for German) see http://codex.wordpress.org/WordPress_Localization for a list of language abbreviations. Please put your .mo file into /wp-content/themes/atahualpa3/ on your Wordpress installation and test it in a blog in the respective language, i.e. do plurals and dates work? Post in this thread if you started working on translation, so others don't work on the same language. Already available:
UPDATE for 3.2: Dear translators, I've updated all .mo/.po files to match 3.2 myself, there's no need to update your files for 3.2. I will however localize the default terms in the Theme Options ("Home", "Category", "Tags", "One Comment".......) for one of the next versions, and once that is done, it would be good if you could create new .po/.mo files. |
German translation is done. As far as I can see it is only for the frontend. A long with that de_DE.mo File you will need to modify some fields within the backend for the post footers for example.
|
1 Attachment(s)
Hungarian translate is done. :)
I attached hu_HU.po and hu_HU.mo files, and here is our site with Atahualpa3 (first trying - the English version is an other theme yet). Best regards! :) P.S.: I found an error in original atahualpa3.pot file: Code:
#: comments-paged.php:29 |
Thanks a lot. I will include it in the next version.
As for the %, Wordpress wants it that way in the template, %s might work for PoEdit but I am not sure if would work in the theme (for Wordpress) as well |
Czech translation is OK. You can see my web.
|
1 Attachment(s)
Here are Czech lang files. Sorry the string "%comments to" cannot be translated (if I try it I'll get a fatal error in PoEdit). Josef
|
Thank you, Pepawo
There should be a space between % and comments, like so: PHP Code:
Yes it currently throws one error related to % comments when saving the file but if you ignore that and you save your .po file anyway does the resulting .mo file work on a blog in czech language? Post updated |
Sorry I misstyped in post, really. Of course original sequence is OK with space. Just I am testing if Fatal error is problem or not. Will reply...
|
1 Attachment(s)
Yes, as you supposed, there is not problem if PO file is saved with that fatal error:
cs_CZ.po:49: 'msgstr' is not a valid PHP format string, unlike 'msgid'. Reason: In the directive number 1, the character 'k' is not a valid conversion specifier (id I translated % comments as % komentářů). Anyway it is not well translated of course, because Czech need to have 2 plurals: 2,3,4 komentáře but 5,6,7 and more (a více) komentářů. The only __ngettext should give the right strings to translate. At moment I translated this string as [%] - komentáře k... vhich give me the same fatal error (char ']'....) but is usable. Not perfect of course. Actualized zip is included. |
1 Attachment(s)
Hello all,
Here's the portuguese translation. I'm using it in my company's blog but it's not online yet. |
Thank you, bergonzzi
I am adding it to the next release |
1 Attachment(s)
Turkish frontend translation is finished for version 3.1.8. It would take a lot more time to finish translating Admin Options...
Here is how it looks: Mental Masturbasyon |
Thank you, Megu. I'll add it to the next version.
|
I'm working on the french version, but hum, I have a 3.1.9 version, found here.
So there's some changes for the line ~175 : Code:
msgid "<strong>XHTML:</strong> You can use these tags:" Code:
msgid "You can use %1$sthese HTML tags</a>" Code:
msgid "<br />Powered by %1$sWordPress</a> · %2$sWordPress Themes</a> by BFA" |
Sorry about that, I have to update the atahualpa.pot file. But you can just use the existing atahualpa.pot that you have and I'll correct those 2 issues myself after you've sent me your .mo/.po files.
Both 3.1.8 and 3.1.9 have the slightly outdated atahualpa.pot file. The 3.1.9 that Wordpress.org hosts has a default style set for sticky posts whereas 3.1.8 has none set (but 3.1.8 is also fully prepared for sticky posts). A very small difference for which I didn't publish an update here on my site. I'll bring everything (the atahualpa.pot and the small 3.1.8-3.1.9 difference) up to date in 3.2 |
1 Attachment(s)
Here it is.
|
Thank you, Tomne. I'll add it to the next version. Please post or PM me a link title and URL for a credit link in the next release post.
|
1 Attachment(s)
Hello, and congratulations for this splendid job :)
I've translated Atahualpa 3 today in french. Fell free to do what you want with it |
Thank you, Wolforg. There's already a french translation. I'll add yours as a second, alternative version.
|
Thanks to you Flynn. I think there is obligatory few variations between these two translations but "more better than less" isn't it? ;)
|
1 Attachment(s)
Polish frontend translation is finished for version 3.1.9: Attachment 15
Note: atahualpa.pot don't contain all phrases from Atahualpa theme in version 3.1.9. Based on code I change in my pl_PL.po file entry: Code:
#: comments-paged.php:200 Code:
#: comments-paged.php:201 Code:
#: comments-paged.php:214 Meybe in future version you move this phrase to .pot file ... |
Thank you, Agard. I'll add it to the next release. You're right the .pot file needs to updated for the next release.
|
1 Attachment(s)
I have made a dutch translation. See attachment for po + mo.
Edit: New Dutch translation can be found here. |
Thanks, josjojo. Will add it to the next release. In case it is not included in your files, please post or PM me a URL/link title for a credit link in the release post
(Other translators, too: Make sure there's a URL somewhere, either in the .po file, or in your Forum profile here, or post/PM it, so I can give you a credit link) |
1 Attachment(s)
Hello,
bulgarian translation is ready. PLease find the attached zip file Attachment 17. Best Regards Veselin Dimitrov |
1 Attachment(s)
Hello,
I've translated Atahualpa in Italian! ;) Here you have the .po & .mo files Thanks in Advance Best regards Gianni Diurno gidibao.net PS I've wrote a post about Atahualpa | http://gidibao.net/index.php/2009/01...a-in-italiano/ |
Thank you, Veselin and Gianni. Will add them both to the next release.
|
Quote:
you're welcome! No, I have to thank you for your awesome theme!!! ;) Best regards as always Gianni [edit] Some readers asked me to translate the 25 admin pages. Do you have any .pot file for the theme back-end translation? Thanks in avance |
Hallo everybody,
I am Frank from Germany and have a hopefully small problem. I am running a WordPress 2.7 DE-Edition Installation. Now I found this great Theme and want to use it in German as well. I found that a german Language File " de_DE.mo " is include in the Theme. My Wordpress configuration file "wp-config.php" says correctly define ('WPLANG', 'de_DE'); Result: My Wordpress is running in german - but Atahualpa is still english. Can anybody help me - I can´t find want wrong Kind regards from the westerwald in germany Frank Hamm |
I think what you're seeing is that a part of the terms is still English. Those terms can be totally customized via the theme options. But if everything worked right, the other part should be German. For instance, is the "Leave a Reply" above the comment form German?
|
I'm working in a Spanish translation. I have finished the first cut and I am testing it in my site.
Regards and thanks for the work Javier |
1 Attachment(s)
Dear Flyn,
Great theme! I've finished translating the theme v.3.1.9 into Vietnamese and attached the .mo and .po files with this post. I've uploaded the .mo file onto my atahualpa folder on my host but it doesnt seem to work. Here my blog using the theme: www.anbinh.info/blog. Hope to hear from you soon. |
Just found out that if I change the file vi_VN.mo into vi.mo then everything works fine. Will fine-tune the file and send you the updated version very soon
|
Hello, I am Fumito Mizuno, living in Kobe, Japan.
I'm interested in Atahualpa Theme. I will translate into Japanese. It may take time, please be patient. |
Quote:
|
Quote:
|
I see, then it makes sense for your installation. Now I wonder if something is wrong with the official vi_VN.mo file. I guess you had this file http://blog.link2caro.net/files/wordpress/vi_VN.mo which is linked from http://codex.wordpress.org/WordPress...7t_.28vi_VN.29 ?
|
1 Attachment(s)
Flyn, that's exactly where I took the (core) language file from. Btw, I've finished the translation. Attached is the new files. Below are text strings that I couldn't manage to get it translated (since they're not included in the pot files)
1. The Post summary info section: a)Format of the date that the post was written. Currently it reads: "Tháng Một 30th, 2009" where "Tháng Một" means January. It should be read: "Ngŕy 30, tháng Một, 2009" b)Text: "Category" also in the Post summary info. c)Text: "%s comment" 2. Reply to post section: text: "You can use these HTML tags" has already mentioned in previous posts 3. Text: "Post" and "Comment" on the "Subscribe to the Posts/Comments feed" at the top right corner. 4. Text: HOME in the Page menu bar. Please refer to my website www.anbinh.info/blog to have a better understanding of what I'm trying to explain above. Please use the language switcher widget to see the different. I'm hoping that these and others will be accommodated in the release 3.2 Kind regards and thank you so much for the theme |
Thank you teddybear, I'll add it to the next release.
|
1 Attachment(s)
Dear all,
I finished translation. I attached a translated file. Please change file_name from "ja_JP.txt" to "ja_JP.po" |
All times are GMT -6. The time now is 01:35 AM. |
Powered by vBulletin® Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.