Right Dan, in retrospect, I should have learned more about how the PO files operate on Launchpad. In the future, it seems that translating using a downloaded copy of the PO file from Launchpad would be most effective; and then uploading it back. In this case, we'll pull a copy of the PO file to add strings for all the contents we can find in the local copy of opac.dtd that we'll be getting from the library's volunteer (yay for Hagaman Library, East Haven, CT!).
More to come, thanks for helping us move in the right direction. -- Ben On 12/15/2010 04:42 PM, Dan Scott wrote: > On 15 December 2010 14:47, Ben Shum <bs...@biblio.org> wrote: >> Hi Jose, >> >> One of our libraries had someone willing to translate Evergreen into >> Spanish. Because they only wanted to focus on OPAC translation to give >> patrons a Spanish version of the OPAC, we gave them a copy of the opac.dtd >> file from /openils/var/web/opac/locale/es-ES to work with. Once we get this >> file back, we're going to contribute its contents back to the Evergreen >> community. We're unsure if that'll mean we have to copy/paste contents back >> to Launchpad's translations or something... > Hmm. How do you plan to merge that translation with the almost 60% of > opac.dtd that has already been translated, according to > https://translations.launchpad.net/evergreen/2.0/+lang/es ? Or was the > copy of es-ES/opac.dtd that you sent to them from later than > 2010-09-28? > > The nice thing about translating directly via an online service is > that you can coordinate efforts to divide and conquer and not step on > one another's toes too much. It's definitely good to be talking about > these efforts on the list, hopefully we can still manage that > coordination. > > Dan > -- Benjamin Shum Open Source Software Coordinator Bibliomation, Inc. 32 Crest Road Middlebury, CT 06762 203-577-4070, ext. 113