summaryrefslogtreecommitdiffstats
path: root/2021
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--2021/talks/omegat.md7
1 files changed, 3 insertions, 4 deletions
diff --git a/2021/talks/omegat.md b/2021/talks/omegat.md
index 3569a611..76a73b70 100644
--- a/2021/talks/omegat.md
+++ b/2021/talks/omegat.md
@@ -28,22 +28,21 @@ The sources are regularly updated with a po4a based shell script.
# Outline
- Duration: 10 minutes
-- Software used during the presentation
+- Software introduced during the presentation
- [po4a](https://po4a.org) a tool to convert documentation formats to and from the commonly used `gettext` **PO** format.
po4a supports the `texinfo` format along with many others.
- - [OmegaT](https://omegat.org) a "computer aided translation" tool used by translators to efficiently combine translation resources (legacy translations, glossaries, etc.) so as to produce more consistent translations.
+ - [OmegaT](https://omegat.org) a "computer aided translation" tool used by professional (and amateur) translators to efficiently combine translation resources (legacy translations, glossaries, etc.) so as to produce more consistent translations.
During this short presentation, I will address:
- The specificities of the Emacs manuals and the difficulties they present to the translator
-- The reason why a professional tool is better than a collaborative web-based system
- How to convert the texi and org files to a format that translators can handle
- How to adapt OmegaT to the Emacs manual specificities
- How to use OmegaT features such as arbitrary string protection, legacy translation handling, glossaries, autocompletion, QA, etc.
- How to use OmegaT with a team of 2 (or more) translators working at the same time
-I will *not* show:
+I will *not* discuss:
- How to create an OmegaT project
- How to set up an OmegaT team project