talk@lists.collectionspace.org
WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org
View all threadsInterface translation to spanish
Hello, my name is Javier Ormeño, I work at The Pablo Neruda Foundation as
Collection and Conservation Manager. I would like to collaborate in the
translation of the CollectionSpace interface to Spanish. My interest is to
facilitate adoption of CollectionSpace in our institution and Spanish
speaking countrys as well. During January and February, I will probably
have some spare time where I could spend time on translation.
Angela Spinazze, oriented me into the basic archives for translation and
suggested to post on this mailing list to see if others would like to help.
Im a competent English reader and have done some articles translation for
colleagues to Spanish, and know about museum collection management
terminology. But programming is not my area of expertise (only know a little
bit of VB programming), so if someone would help me out in this matter it
would be appreciated.
Archives to translate:
a.- The main message properties file for the 4.0 release. At
<https://github.com/collectionspace/ui/blob/v4.0/src/main/webapp/defaults/bu
ndle/core-messages.properties>
https://github.com/collectionspace/ui/blob/v4.0/src/main/webapp/defaults/bun
dle/core-messages.properties. It seems like a straight forward translation,
translate everything after the colon except programming references (%count
or the email pointed in some strings) or the comments (#).
b.- The termLists file. At
<https://github.com/collectionspace/application/blob/v4.0/tomcat-main/src/ma
in/resources/defaults/base-instance-vocabularies.xml>
https://github.com/collectionspace/application/blob/v4.0/tomcat-main/src/mai
n/resources/defaults/base-instance-vocabularies.xml.
Do I translate everything between the option and title marker? Leaving the
instance, web-url and title-ref markers untouched?
Questions:
1.- Im not familiar with Github, so Im not sure where do I make the
translation, do I sign in and fork these files or make a copy, edit and send
them?
2.- How do I update these translations if theres a new CollectionSpace
release?
3.- Would the Spanish interface (once implemented) be an out of the box
option for users to set, or would it require some programming setup on the
server side?
4.- Angela also mentioned that there was a Danish translation, does anybody
have some feedback on the process that might be helpful in this case?
Best regards,
Javier.
Hello Javier,
I'm not able to answer your questions, so hopefully someone else will be able to respond today. But I just wanted to say THANKS from the CollectionSpace community! This is a great offer and idea!
Regards,
Chris Hoffman
UC Berkeley
On Dec 9, 2013, at 6:58 AM, Javier Ormeño wrote:
Hello, my name is Javier Ormeño, I work at The Pablo Neruda Foundation as Collection and Conservation Manager. I would like to collaborate in the translation of the CollectionSpace interface to Spanish. My interest is to facilitate adoption of CollectionSpace in our institution and Spanish speaking country’s as well. During January and February, I will probably have some spare time where I could spend time on translation.
Angela Spinazze, oriented me into the basic archive’s for translation and suggested to post on this mailing list to see if others would like to help. I’m a competent English reader and have done some articles translation for colleagues to Spanish, and know about museum collection management terminology. But programming is not my area of expertise (only know a little bit of VB programming), so if someone would help me out in this matter it would be appreciated.
Archives to translate:
a.- The main message properties file for the 4.0 release. Athttps://github.com/collectionspace/ui/blob/v4.0/src/main/webapp/defaults/bundle/core-messages.properties. It seems like a straight forward translation, translate everything after the colon except programming references (%count or the email pointed in some strings) or the comments (#).
b.- The termLists file. At https://github.com/collectionspace/application/blob/v4.0/tomcat-main/src/main/resources/defaults/base-instance-vocabularies.xml.
Do I translate everything between the option and title marker? Leaving the instance, web-url and title-ref markers untouched?
Questions:
1.- I’m not familiar with Github, so I’m not sure where do I make the translation, do I sign in and fork these files or make a copy, edit and send them?
2.- How do I update these translations if there’s a new CollectionSpace release?
3.- Would the Spanish interface (once implemented) be an out of the box option for users to set, or would it require some programming setup on the server side?
4.- Angela also mentioned that there was a Danish translation, does anybody have some feedback on the process that might be helpful in this case?
Best regards,
Javier.
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Hi Javier,
I'm a member of the team which carried out some Danish translations. These translations have not been merged with Collectionspace core code, so you would be the first to attempt this. It seems reasonable that one should be able to build an alternative language core package through configuration but I don't think there is currently a process in place for supporting multiple versions of these config files (except through tenants). I expect the core development team will get back to you about how to configure and contribute these. If you have the possibility, I think you should try to install a version of Collectionspace (http://wiki.collectionspace.org/display/DOC/Installing+CollectionSpace) you can test on - you can try out these changes without programming.
We carried out all our translations under a new tenant (http://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant), so our changes were not made to the core files, but to our local tenant versions of these files. The reason for this new tenant was to support a large number of extensions (extra fields) which aren't present in core but also to support duplicate English language versions of many of our fields (as we have to support English versions of web pages, signs and reports) and each of these requires an extension.
Your summary of the necessary changes seems to be correct. There're some notes here: http://wiki.collectionspace.org/display/DOC/The+message+bundle+file+in+the+UI+layer and I've provided links to our versions of the files below. Where some vocabularies and texts are not translated, it's because much of the core is not being used in our deployment. There may also be a couple of places where texts are hardcoded in html (sorry, can't remember where) and at least one administrative text can be found in the "*settings.xml" configuration file (search for <message> under <passwordreset> in the last link).
https://bitbucket.org/christopher_pott/corpus_ui/src/master/src/main/webapp/tenants/smk/bundle/core-messages.properties-overlay?at=master
https://bitbucket.org/christopher_pott/corpus_application/src/master/tomcat-main/src/main/resources/tenants/smk/base-instance-vocabularies.xml?at=master
https://bitbucket.org/christopher_pott/corpus_application/src/master/tomcat-main/src/main/resources/tenants/smk/domain-instance-vocabularies.xml?at=master
https://bitbucket.org/christopher_pott/corpus_application/src/master/tomcat-main/src/main/resources/tenants/smk/local-smk-settings.xml?at=master
Best regards,
Chris Pott
IT Developer
Statens Museum for Kunst
Fra: Talk [mailto:talk-bounces@lists.collectionspace.org] På vegne af Javier Ormeño
Sendt: 9. december 2013 15:58
Til: talk@lists.collectionspace.org
Emne: [Talk] Interface translation to spanish
Hello, my name is Javier Ormeño, I work at The Pablo Neruda Foundation as Collection and Conservation Manager. I would like to collaborate in the translation of the CollectionSpace interface to Spanish. My interest is to facilitate adoption of CollectionSpace in our institution and Spanish speaking country's as well. During January and February, I will probably have some spare time where I could spend time on translation.
Angela Spinazze, oriented me into the basic archive's for translation and suggested to post on this mailing list to see if others would like to help. I'm a competent English reader and have done some articles translation for colleagues to Spanish, and know about museum collection management terminology. But programming is not my area of expertise (only know a little bit of VB programming), so if someone would help me out in this matter it would be appreciated.
Archives to translate:
a.- The main message properties file for the 4.0 release. At https://github.com/collectionspace/ui/blob/v4.0/src/main/webapp/defaults/bundle/core-messages.properties. It seems like a straight forward translation, translate everything after the colon except programming references (%count or the email pointed in some strings) or the comments (#).
b.- The termLists file. At https://github.com/collectionspace/application/blob/v4.0/tomcat-main/src/main/resources/defaults/base-instance-vocabularies.xml.
Do I translate everything between the option and title marker? Leaving the instance, web-url and title-ref markers untouched?
Questions:
1.- I'm not familiar with Github, so I'm not sure where do I make the translation, do I sign in and fork these files or make a copy, edit and send them?
2.- How do I update these translations if there's a new CollectionSpace release?
3.- Would the Spanish interface (once implemented) be an out of the box option for users to set, or would it require some programming setup on the server side?
4.- Angela also mentioned that there was a Danish translation, does anybody have some feedback on the process that might be helpful in this case?
Best regards,
Javier.
Thank you Christopher, I was planning to install a test version of
CollectionSpace mid 2014. But I first wanted to translate collaborate on
translation, since programming and server installations are out of my
current capabilities. So in case the translation couldnt be merged with the
core code, at least by your experience, it doesnt seem like a difficult
task to configure the translation at tenants level.
I will wait for the insight of the core development team.
Best regards.
Javier.
De: Christopher Pott [mailto:Christopher.Pott@smk.dk]
Enviado el: Martes, 10 de Diciembre de 2013 5:33
Para: 'Javier Ormeño'; talk@lists.collectionspace.org
Asunto: SV: [Talk] Interface translation to spanish
Hi Javier,
Im a member of the team which carried out some Danish translations. These
translations have not been merged with Collectionspace core code, so you
would be the first to attempt this. It seems reasonable that one should be
able to build an alternative language core package through configuration but
I dont think there is currently a process in place for supporting multiple
versions of these config files (except through tenants). I expect the core
development team will get back to you about how to configure and contribute
these. If you have the possibility, I think you should try to install a
version of Collectionspace (
http://wiki.collectionspace.org/display/DOC/Installing+CollectionSpace
http://wiki.collectionspace.org/display/DOC/Installing+CollectionSpace) you
can test on you can try out these changes without programming.
We carried out all our translations under a new tenant (
http://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant
http://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant), so
our changes were not made to the core files, but to our local tenant
versions of these files. The reason for this new tenant was to support a
large number of extensions (extra fields) which arent present in core but
also to support duplicate English language versions of many of our fields
(as we have to support English versions of web pages, signs and reports) and
each of these requires an extension.
Your summary of the necessary changes seems to be correct. Therere some
notes here:
<http://wiki.collectionspace.org/display/DOC/The+message+bundle+file+in+the+
UI+layer>
http://wiki.collectionspace.org/display/DOC/The+message+bundle+file+in+the+U
I+layer and Ive provided links to our versions of the files below. Where
some vocabularies and texts are not translated, its because much of the
core is not being used in our deployment. There may also be a couple of
places where texts are hardcoded in html (sorry, cant remember where) and
at least one administrative text can be found in the *settings.xml
configuration file (search for <message> under <passwordreset> in the last
link).
<https://bitbucket.org/christopher_pott/corpus_ui/src/master/src/main/webapp
/tenants/smk/bundle/core-messages.properties-overlay?at=master>
https://bitbucket.org/christopher_pott/corpus_ui/src/master/src/main/webapp/
tenants/smk/bundle/core-messages.properties-overlay?at=master
<https://bitbucket.org/christopher_pott/corpus_application/src/master/tomcat
-main/src/main/resources/tenants/smk/base-instance-vocabularies.xml?at=maste
r>
https://bitbucket.org/christopher_pott/corpus_application/src/master/tomcat-
main/src/main/resources/tenants/smk/base-instance-vocabularies.xml?at=master
<https://bitbucket.org/christopher_pott/corpus_application/src/master/tomcat
-main/src/main/resources/tenants/smk/domain-instance-vocabularies.xml?at=mas
ter>
https://bitbucket.org/christopher_pott/corpus_application/src/master/tomcat-
main/src/main/resources/tenants/smk/domain-instance-vocabularies.xml?at=mast
er
<https://bitbucket.org/christopher_pott/corpus_application/src/master/tomcat
-main/src/main/resources/tenants/smk/local-smk-settings.xml?at=master>
https://bitbucket.org/christopher_pott/corpus_application/src/master/tomcat-
main/src/main/resources/tenants/smk/local-smk-settings.xml?at=master
Best regards,
Chris Pott
IT Developer
Statens Museum for Kunst
Fra: Talk [mailto:talk-bounces@lists.collectionspace.org] På vegne af Javier
Ormeño
Sendt: 9. december 2013 15:58
Til: talk@lists.collectionspace.org
Emne: [Talk] Interface translation to spanish
Hello, my name is Javier Ormeño, I work at The Pablo Neruda Foundation as
Collection and Conservation Manager. I would like to collaborate in the
translation of the CollectionSpace interface to Spanish. My interest is to
facilitate adoption of CollectionSpace in our institution and Spanish
speaking countrys as well. During January and February, I will probably
have some spare time where I could spend time on translation.
Angela Spinazze, oriented me into the basic archives for translation and
suggested to post on this mailing list to see if others would like to help.
Im a competent English reader and have done some articles translation for
colleagues to Spanish, and know about museum collection management
terminology. But programming is not my area of expertise (only know a little
bit of VB programming), so if someone would help me out in this matter it
would be appreciated.
Archives to translate:
a.- The main message properties file for the 4.0 release. At
<https://github.com/collectionspace/ui/blob/v4.0/src/main/webapp/defaults/bu
ndle/core-messages.properties>
https://github.com/collectionspace/ui/blob/v4.0/src/main/webapp/defaults/bun
dle/core-messages.properties. It seems like a straight forward translation,
translate everything after the colon except programming references (%count
or the email pointed in some strings) or the comments (#).
b.- The termLists file. At
<https://github.com/collectionspace/application/blob/v4.0/tomcat-main/src/ma
in/resources/defaults/base-instance-vocabularies.xml>
https://github.com/collectionspace/application/blob/v4.0/tomcat-main/src/mai
n/resources/defaults/base-instance-vocabularies.xml.
Do I translate everything between the option and title marker? Leaving the
instance, web-url and title-ref markers untouched?
Questions:
1.- Im not familiar with Github, so Im not sure where do I make the
translation, do I sign in and fork these files or make a copy, edit and send
them?
2.- How do I update these translations if theres a new CollectionSpace
release?
3.- Would the Spanish interface (once implemented) be an out of the box
option for users to set, or would it require some programming setup on the
server side?
4.- Angela also mentioned that there was a Danish translation, does anybody
have some feedback on the process that might be helpful in this case?
Best regards,
Javier.
Se certificó que el correo no contiene virus.
Comprobada por AVG - www.avg.es
Versión: 2012.0.2247 / Base de datos de virus: 3658/6407 - Fecha de la
versión: 10/12/2013