Welcome to the team, Christiane!
I want to repeat some of the issues of our mail conversation here at
this list, in order to help others that have the same questions:
> should I use, the .PO, the .XLIFF, .CSV or what?
You should use the PO files, preferably - even if they could be
converted. The Pootle provides also other formats in case the target
application would require these, but Sahana uses PO.
> download the .ZIP files, I get the following error: "'ascii' codec can't
> decode byte 0x9e in position 11: ordinal not in range(128)"
Okay - I fixed that. Sorry for the unconveniences.
> I'd rather work offline, yes, if that's not an inconvenience for the project
No - it's absolutely no problem if you want to work offline. Just
download the PO files from the Pootle server, translate them and send
them back to me. I will merge and upload them. It would be good to
know which of the files you're currently working on, to have a better
oversight which files could be assigned to other translators.
> I'm also assuming that the PO files are generated from the application files
> (I did see somewhere "generated from glossary.txt"). Is it possible to work
> directly from the say glossary.txt file?
It makes rather no sense to work from the source files, and the source
code itself doesn't have to be changed for translation. If you need to
take a look at the Sahana user interface to see what a particular
message string is used for, feel free to use the Sahana demo at the
EDRS server.
Thank you for contributing!
Kind regards,
Dominic