Difference between revisions of "Guidelines for Translators"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
Too fragmentary parts of an otherwise translatable texts can also be left aside and properly signalled with diacritic signs |
Too fragmentary parts of an otherwise translatable texts can also be left aside and properly signalled with diacritic signs |
||
| + | |||
| + | Round brackets conventionally used for resolving an abbreviated word should never appear in the translation |
||
| + | |||
| + | Square brackets should also be omied when the whole text is re- stored to full intelligibility and/or the proposed integrations are marked by the editor as certain. |
||
| + | |||
{{Cite book |
{{Cite book |
||
Revision as of 11:08, 4 August 2014
Appendices of translated common abbreviations like Keppie’s and glossaries like Andreu Pintado’s may very well be the starting point of a discussion on an EAGLE vocabulary, which could ideally form the core of the expected Deliverable on Translations.
Too fragmentary parts of an otherwise translatable texts can also be left aside and properly signalled with diacritic signs
Round brackets conventionally used for resolving an abbreviated word should never appear in the translation
Square brackets should also be omied when the whole text is re- stored to full intelligibility and/or the proposed integrations are marked by the editor as certain.
