Internationalize bagit

[johnscancella]

Bagit should use the Java standard way for internationalize all messages. This way Bagit can be used by others that don't understand english.

[johnscancella]

see http://docs.oracle.com/javase/tutorial/i18n/intro/after.html for example

[johnscancella]

see https://docs.transifex.com/client/introduction for translating

[johnscancella]

Help is wanted to translate into other languages:

• English
• Chinese
• Spanish
• Arabic
• Portuguese
• Japanese
• Russian
• Malay
• French
• German

(from the top 10 listing of internet languages https://www.accreditedlanguage.com/2016/09/13/top-10-languages-used-on-the-internet/)

[johnscancella]

TODO
add gradle task to check that all messages used are in each messageBundle

[buslov]

Transifex says:

This organization's trial has ended. To keep using Transifex, please ask one of the organization's administrators to subscribe to a plan.

And moreover it seems to be ugly HTML on Transifex instead of Java ResourceBundle.

[johnscancella]

@acdha suggestions? You know Transifex better than I do

[acdha]

It looks like Transifex changed their subscription system recently so I had to switch to the open source plan to unlock it.

I don't know what format was configured for bagit-java but Transifex supports Java properties files so that appears to be an error loading data into the system.

[acdha]

After uploading the properties file manually, it looks fine:

https://www.transifex.com/acdha/bagit-java/translate/#ru/messagebundleproperties/112102491

I suspect what happened before was that it had the URL to the GitHub HTML view of the file rather than the raw file itself.

[acdha]

One other thing to consider: we should probably move this to a separate organization once it's out of testing status so it's not anchored to my personal account.

[johnscancella]

@acdha yes, we should talk to @dbrunton about that

[Segerberg]

Hello, working on a Swedish translation and noticed that other translations translate the bagit specification reserved metadata elements. Is this the preferred way? //A

[johnscancella]

@Segerberg Thanks for contributing by translating to Swedish! I'm not sure what you mean, could you give me an example? In general I have left it up to the translator to determine if a specific word should be kept in english or not so that they can choose the best message they can. All {} need to be preserved as they are place holders for information that is passed in during runtime.

[Segerberg]

Sorry for being unclear! For our use we wish to keep the original naming of the reserved elements as stated in the specification Bag-Size, source-organization etc...(for correct reference amongst other things). When i checked other translations they consequently translates these. But if it's up to me I'll keep them in english! Happy to continue talk but it maybe better to do it crowdin !

[johnscancella]

That sounds good to me, and thanks again for all the hard work!

[Segerberg]

Hello @johnscancella the Swedish translation is finished. Do you need som external review before commiting or do you trust me? =)

[jscancella]

@Segerberg I no longer work at the Library of Congress. Perhaps @acdha or @dbrunton will be able to merge it for you.