Translations

Attached is the Brazilian Portuguese translation of interface and images.

If you have any problem, please contact me.

Best regards.

Frederico (aka Aracnus)

Hi Michelle,

This translation is for the stable version. It's here because this was the only "Translation" issue that I found. :-) May I put it on another place?

Sorry about the mess.

Best regards,

Frederico (aka Aracnus)

Hi, not sure where else to ask - can you please split of translation of "Views" (column name) from the module name? I am translating into Russian, and the cases and context make a lot of difference in what words I'd be using...

Regards,
NPC

Thanks for your reply, Michelle. I found that you do this in file "advanced_forum.module" - can I edit the call to something else, say, t('Topic Views'), would that automatically add a new untranslated string to Drupal, do you know?

Otherwise, I will probably have to comment that part of the header forming code out - is that okay, or should I then rebuild something?

Regards,
NPC

Translators,

It might be worth mentioning somewhere in the documentation that some of the translation might have to take place in the views.

In spite of the fact that I knew that some elements in Advanced Forum were view based, I spent more time than I want to admit tracking down strings like "[title] by [author] on [date]", which are use in the main list of topics for each forum.

I had to edit the individual field in each view to get the proper translation.

Other translations in the views seemed to be picked up during installation and used in the views. Amongst them the word "view/views" itself, which can mean a lot of things and can translate to more than one single word in some languages.
Again I had to hunt down the translation in the view, where it ocurred as already translated field labels, rather than through the usual translation tools.

So if you can't find certain strings, which appear in English your translated forums, look in the view for the block or page in question. It might hide in there.

Martin

OK, I tried to solve the problem I am having myself, and it works.

What I needed to correct is Advanced Forums "View" column title using the translation of the Views module - which, at least for Russian language, produces wrong text for the context.

In file advanced_forum.module, row 843 contains string T('Views'). I changed it to T('Forum Views') (I don't use English on the site, so just needed a unique and an identifiable string) and saved. Then I looked at the forum page - the column title changed to "Forum Views", and then I could find it in administration translation page search, and enter a correct translation of the string to Russian.

Now I need to remember to re-do this every time AF is updated, until there is a proper solution. A pain, but I don't seem to have any choice (it is not even possible to hide the column without a hack).

Hi,

I know v. 2 isn't finished yet. But there were some features there that I really missed from v. 1, so I tried it out. But the translations don't take. My site is in Swedish and there is a Swedish .po file. Is there anything else needed to be done to get translations to work in v. 2?

@michelle: Thanks for quick reply! Well, there are several translation files, although only partly translated. One of them is Swedish. I got it to work after removing Swedish as a language for my site and then reenabling it.

Also, if I make my own translations, since I needed some of them quickly, in the sv.po file and upload it, they don't take. So I suppose translating isn't simply to upload a new .po file?

I will help out translating at localize.drupal.org, but I also needed a quick way to update some untranslated strings.

Other modules have worked with my default language (Swedish) when installing them, but maybe that part is not yet ready in the alpha 2 version of Advanced Forum?

From Maintainer News dec 7 2010:

A. If you are a translation maintainer: you've already been contacted, and
your team is in the process of moving from drupal.org to localize.drupal.org.

B. If you are a translator: stop working on .po files in CVS (either for
Drupal core or contrib), instead import existing .po files from CVS to
localize.drupal.org (if not already), remove the imported file from CVS and
work on localize.drupal.org from now on.

C. If you are a drupal.org project maintainer: do not accept .po files
anymore in your issue queues and remove your .pot files from CVS; tell people
to use localize.drupal.org.

I took the time to import all translations to respective language team on localize.drupal.org to ensure no work will be lost.