Talk:Parley/Manual: Difference between revisions
No edit summary |
SabineEller (talk | contribs) No edit summary |
||
| Line 5: | Line 5: | ||
We hope to get many more translations done when we change to the new, simpler translation system (next month, all being well). We have discovered, though, that empty lines create the splits, so that if you include an empty line after a section heading, one translation unit contains only the heading, then the connected body is in a separate unit. This causes frustration for the translators, as every unit has to be uploaded separately - a very slow task. Consequently, over the next month I'm likely to have to go through every UserBase page and remove unnecessary white lines. If you could do this on your web pages while you are creating them it would save me a job. Thanks. --[[User:Annew|annew]] 10:47, 25 January 2010 (UTC) | We hope to get many more translations done when we change to the new, simpler translation system (next month, all being well). We have discovered, though, that empty lines create the splits, so that if you include an empty line after a section heading, one translation unit contains only the heading, then the connected body is in a separate unit. This causes frustration for the translators, as every unit has to be uploaded separately - a very slow task. Consequently, over the next month I'm likely to have to go through every UserBase page and remove unnecessary white lines. If you could do this on your web pages while you are creating them it would save me a job. Thanks. --[[User:Annew|annew]] 10:47, 25 January 2010 (UTC) | ||
:Sorry, but being a translator I disagree: Sentences should go into separate segments in translation. This is the best way to get good matches when working with a CAT-Tool. If the CAT-Tool cannot manage a wiki-paragraph it means it is not suited to do the job. Then I would suggest to just use OmegaT to directly translate wiki pages. It has an inbuilt function from where you can access the pages on a MediaWiki installation directly for translation. --[[User:SabineEller|SabineEller]] 01:20, 2 June 2010 (UTC) | |||
---- | |||
Ok, so here we go: I cannot do much more now since I don't have examples for comparatives and conjugations. I DID NOT check for consistency in writing since I really worked fast to get things done. If tomorrow is enough time I will go through the repetitive sentences used and see to make just "one sentence" which helps a lot in speeding up localization. | |||
To remember: | |||
*file --> collection | |||
*picture --> image | |||
fregl and dani_l please write down your notes here. --[[User:SabineEller|SabineEller]] 01:20, 2 June 2010 (UTC) | |||
Revision as of 01:21, 2 June 2010
Please don't add 'Parley' as a category. If you search for Parley you will see all the pages with Parley in the name,including the path, so Parley/Manual will automatically be listed.
We've only recently set up Categories, but I think this will be even better, soon. The Category:Education will list all your Parley pages. For the moment it would also list all Parley translated pages, but I'm working with the translators to enable each language to have its own Category-translated page. --annew 17:29, 17 January 2010 (UTC)
We hope to get many more translations done when we change to the new, simpler translation system (next month, all being well). We have discovered, though, that empty lines create the splits, so that if you include an empty line after a section heading, one translation unit contains only the heading, then the connected body is in a separate unit. This causes frustration for the translators, as every unit has to be uploaded separately - a very slow task. Consequently, over the next month I'm likely to have to go through every UserBase page and remove unnecessary white lines. If you could do this on your web pages while you are creating them it would save me a job. Thanks. --annew 10:47, 25 January 2010 (UTC)
- Sorry, but being a translator I disagree: Sentences should go into separate segments in translation. This is the best way to get good matches when working with a CAT-Tool. If the CAT-Tool cannot manage a wiki-paragraph it means it is not suited to do the job. Then I would suggest to just use OmegaT to directly translate wiki pages. It has an inbuilt function from where you can access the pages on a MediaWiki installation directly for translation. --SabineEller 01:20, 2 June 2010 (UTC)
Ok, so here we go: I cannot do much more now since I don't have examples for comparatives and conjugations. I DID NOT check for consistency in writing since I really worked fast to get things done. If tomorrow is enough time I will go through the repetitive sentences used and see to make just "one sentence" which helps a lot in speeding up localization.
To remember:
- file --> collection
- picture --> image
fregl and dani_l please write down your notes here. --SabineEller 01:20, 2 June 2010 (UTC)