See http://www.zotero.org/support/dev/localization

I have translated the danish language file for CSL. It is now complete.

https://www.strongspace.com/hafnius/public/dev/citation-style-language-locales-2b7aa27/locales-da-DK.xml

I have been carefull in getting it right, cross-referenced it with the norwegian trans. since norwegian is close to danish.

Kind regards
Klaus Brinch

No - it was an error on my part. Its been corected now and uploaded again. Thanks

So i started translating the files for the zotero client and the work is well under way.

There are some terms that i am strugling with though and that will require some extra work. Those terms are:

1. Resolver
2. Child node/link
3. Style (ie. citation style)
4. Lbrary (ie. group library)

I know what all the terms mean in the Zotero context but i have a hard time finding the right danish equivalent. What i have so far for the danish inclined:

1. Resolver = udbyder, men det passer ikke helt
2. Child node/link = barn, men det funker ikke. Drupal bruger begrebet meget, så kigger der.
3. Styles = citat stil, føles heller ikke helt rigtig. måske refworks på dansk kan hjælpe.
4. Library = bibliotek, men måske samling ville være bedre

I welcome any suggestions from my fellow danes (danskere)

I will update this thread when i have more

Same as above: http://www.zotero.org/support/dev/localization

By the way: locales-da-DK.xml needs further revision. The version provided by Hafnius was a big step forward, but it has some deviations from Danish reference standards.

I will provide a revised version when the problems mentioned abover have been solved.

Yours NEWille

Actually I need to test the results of the translation before any "innocent" users have to use the new version. That is the professional translator's way.

The problem is that I do not always know where the text will prop up in Zotero and what the specific context for the wording will be. I have already had to change translation several times in a very slow analysing and guessing proces. Implementing and checking the results would speed up things considerably.

The present version shipped with Zotero is bad enough. I do not want confuse users in the same way because of forced ignorance.

Yours NEWille

Here. Just create a gist at gist.github.com and post the URL.

How do I test my translation???

The easiest way is described at the bottom of this page, under the heading "Longer-term Development". Edit: direct link.

On TransiFex, download "for use".

When I have tested and revised the translation I will have to go back and revise the TransiFex version so to speak "by hand". Or is there another way?

Yes.

PS I haven't tried the gist way yet for the xml file. But it will probably add to my experiences as a Zotero-localizer.

Gist is really really easy: you've just to copy&paste.

I just don't think there is a good way to test and sync translations - that's what Gracile's "yes" means.
It is not expected that translators compile a new version of Zotero to test their translations, and transifex isn't set-up for that, so there is not good way to test or to sync your tested files back onto transifex.

Zotero has a relatively quick update cycle, so if something really comes out badly, you can fix it after the next release, that's how all the other teams have worked and I think it's been going fine.
Thanks for all your work on that, btw.

Sorry to be such a pest. But I wanted to be sure that the Danish translation works well before I can recommend Zotero wholeheartedly to my students an colleagues. The present version shipped with Zotero is just not good enough.

When I tried to test the translated files by unzipping and rezipping zotero.jar the system just froze in the middle of loading the Library. I do not know why - but that was seemingly not the way to go about it. It happened every time with renwed attempts. And if that was caused by something in the translated file and included in the next update, the result would be bad for Zotero.

I then implemented the procedure recommended by Gracile and it worked as I have described earlier. But I didn't use downloaded files from TransiFex, since it looked like they were the cause of the trouble.

This morning I downloaded the file "for translation" and renamed it. Then added it to the unpacked zotero.jar in the proper place. And this time it worked well.

So the workflow described by Gracile should work (!).

Now I am all set to finish the work. But it would be a blessing for translators if somebody could produce something to explain which fields go where in the bibliographic descriptions and what they are supposed to represent. The Glossary in TransiFex would be a handy place.

Yours NEWille

No, I didn't use compression when re-zipping. And of course the TransiFex-files weren't the cause. But at the time I couldn't know that. I still haven't figured out what went wrong, but in practice I am past the point where it really matters.

As for using the glossary for explanations, I think it would be enough to have the explanations in the English version, since the terminology used in the default system obviously is English (en-US?). I don't want to inherit interpretation mistakes made by other translators.

But as you say - very time-consuming - but also very useful for the translators.

@fbennett: That's what NEWille did eventually.

Please!

How did the ***SPAM*** above get into this Forum?

And How do we get rid of it?

Yours NEWille