german translation
FrankT - August 11, 2008 - 16:45
| Project: | Privatemsg |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Description
I updated the german translation provided with the module and updated it with the pot file in the po directory. I translated missing strings, corrected obvious errors (including correct plural forms in the catalog options) and misspellings and applied some changes to match the german translation standards ('Sie' instead of 'Du' etc.). I did not change the de-informal.po.
I did this mainly to supply a better base line for a drupal 6 version of the module (I do not have a drupal 5 installation but I'm sure my corrections are correct).
You may commit it to CVS.
| Attachment | Size |
|---|---|
| de.po | 15.8 KB |
#1
I continued to translate the module and it now matches V6.x-1.0-rc2. Please commit it to CVS. Thanks!
#2
Looks good.
Not sure if sub-modules should have their own translations....
#3
I can extract each sub-module into an own po file if you like (to have on po file is better for translation, if other strings must be searched).
But it is no problem if privatemsg is nearing its release.
#4
...had to fix a problem with extracting sub-modules. Here are they files you might need.
#5
how do i get this working? where do i have to put the po file? thanks.
#6
So far if only one po files (for all modules) has been created it had to be put into a subdirectory translations under the module's dir (primatemsg/translations).
Now that there are translation files for each module, each translation must (?) be put into a 'translation' subdirectory of each module. That's what I could find out going through translations for organic groups.
So in my eyes
- privatemsg.de.po must be put into privatemsg/translations
- privatemsg_filter.de.po must be put into privatemsg/privatemsg_filter/translations
#7
I have created translations directories in each of the privatemsg and submodule folders. According to drupal.org rules, anyone may commit translations into the translations folders. I've never done this before so i am not 100% sure. because of that i would like some one other than myself to try to commit translations to the DRUPAL-6--1 branch.
Let me know if you need some further help.
#8
I updated my translation to match the latest dev. As nobody has put it into CVS so far (and I don't know how to do at all) I would like you to put the file into the translations directory as is. Thanks!
#9
That's cool! I didn't know that.
I committed a .pot file to the translations folder of branch 6.1. (http://drupal.org/node/446360)
Cheers,
Frank
#10
I updated my translation to match the latest dev of June, 09.
I would be very pleased if it could be put into the translations directory now such as hu.po already is. Thanks!
#11
Thanks!
I had a quick look at the translation and there are three strings untranslated and line 193 doesn't look OK for me:
You have <a href=\"@messages\">%unread</a>.Es gibt <a href=\"@inbox\">%unread</a>.Seems like a wrong placeholder? Could you have another look at the translation and upload it again?
TIA
Frank
#12
You're right, there was a wrong placeholder. An updated translation is attached.
With the 3 untranslated strings: I was not able to locate it in the user interface so they are still untranslated. If you can tell me the meaning of the string (or the place where to find them) I will translate them, too.
#13
Thanks a lot! Will commit your translation ASAP.
Frank
#14
I updated the translation to reflect the change in #491414: String issue (b-tag). Please commit it to CVS. Thanks!
#15
Many thanks for your effort! I corrected some small typos and committed the translation to the MAIN/HEAD branch.
#16
You have to commit it to the DRUPAL-6--1 branch. HEAD is currently not used (it links to the 2.x-dev release, but that is dead atm)
#17
Done. Thanks for the hint!
#18
Ok, great, let's set this to fixed then.
#19
Automatically closed -- issue fixed for 2 weeks with no activity.