Re: APIDOCS was: [Bug 244946] [NEW] Translation template #48 unclear
Hi Karsten, On Fri, 2008-07-04 at 10:58 +0200, Karsten Hilbert wrote: > I don't think so from a few years of translating. > > It may seem attractive at first to break down translated > strings into small components thinking the formatting > shouldn't change across languages. However, one and the same > word will need to be translated differently according to > context. That context is made up of a) other words and b) > formatting. > > This surely doesn't apply so much to triple quoted class > descriptions as discussed here but it will apply to > intra-app strings. Thanks for your perspective. Experience is always helpful. I think, especially with all the other things that need to be done, we'll leave them as is for now. I am certainly open to revisiting the issue. Maybe if you start on the German translation (yes I know you re busy with exams) then you can comment further. :-) Cheers, Tim -- Timothy Cook, MSc Health Informatics Research & Development Services LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == timothy.cook ************************************************************** *You may get my Public GPG key from popular keyservers or * *from this link http://timothywayne.cook.googlepages.com/home* **************************************************************
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ ref_impl_python mailing list ref_impl_python@openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/ref_impl_python