summaryrefslogtreecommitdiffstats
path: root/2021/talks/omegat.md
diff options
context:
space:
mode:
Diffstat (limited to '2021/talks/omegat.md')
-rw-r--r--2021/talks/omegat.md46
1 files changed, 23 insertions, 23 deletions
diff --git a/2021/talks/omegat.md b/2021/talks/omegat.md
index 10a1aca..1b217a2 100644
--- a/2021/talks/omegat.md
+++ b/2021/talks/omegat.md
@@ -10,9 +10,9 @@ Jean-Christophe Helary
Even if it is generally agreed that software localization is a good thing, Emacs is lacking in that respect for a number of technical reasons. Nonetheless, the free software using public could greatly benefit from Emacs manuals translations, even if the interface were to remain in English.
-OmegaT is a multiplatform GPL3+ "computer aided translation" tool running on OpenJDK 11. That category of software is roughly equivalent for translators to what IDEs are for code writers. Casual translators can benefit from its features but professionals are the most likely to make the most use of OmegaT.
+OmegaT is a multiplatform GPL3+ "computer aided translation" (CAT) tool running on OpenJDK 8. CATs are roughly equivalent for translators to what IDEs are for code writers. Casual translators can benefit from their features but professionals or commited amateurs are the most likely to make the most use of such tools.
-When Emacs, OmegaT and free software based forges meet, we have a free multi-user translation environment that can easily sustain the (close to) 2 million words load that comprise the manuals distributed with Emacs, along with powerful features like arbitrary string protection for easy typing and QA (quality assurance), automatic legacy translation handling, glossary management, history based or predictive autocompletion, etc.
+When OmegaT, free software based forges and Emacs meet, we have a free multi-user translation environment that can easily sustain the (close to) 2 million words load that comprise the manuals distributed with Emacs, along with powerful features like arbitrary string protection for easy typing and QA (quality assurance), automatic legacy translation handling, glossary management, history based or predictive autocompletion, etc.
The current trial project for French is hosted on 2 different forges:
@@ -23,29 +23,29 @@ The current trial project for French is hosted on 2 different forges:
The sources are regularly updated with a po4a based shell script.
-
-
# Outline
-- 5-10 minutes: (brief description/outline)
-
-In this format, I would show the basics of:
-
-1. using po4a to convert the texi files to the PO format
-2. using OmegaT as a team with 2 (or more) translators working at the same time
-3. using OmegaT features such as regex based string protection, legacy translation handling, autocompletion, QA, etc.
-
-<!--
-- 20 minutes: (brief description/outline)
-
-With more time, I would discuss the same items, slightly longer, along with:
-
-1. a short description of how I came up with the regex used to identify non-translatable markers in the manuals, found here:
- <https://gist.github.com/brandelune/46faceb4c81bfee7c938282cc6dfe17c>
- and explained in French here:
- <https://goshikidai.blogspot.com/2021/08/#5695124486632169049>
-2. how all that team coordination is in fact a huge git job hidden from the users
-3. discuss what is called MTPE in the translation industry (Machine Translation Post Edit) and how that relates to/affects localization in general (cf. the recent LibreOffice documentation Japanese translation using MT)
+- Duration: 10 minutes
+- Software used 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 ressources (legacy translations, glossaries, etc.) so as to produce more consistent translations.
+
+During the presentation, I will show:
+- How to use po4a to convert the texi files to the PO format (the org.org file is also converted)
+- What are the specificities of the Emacs manuals and what difficulties they present to the tanslator
+- How to address those specificities in OmegaT, with regular expressions
+- 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
+- How to solve translation conflicts
+
+I will *not* show:
+- How to create an OmegaT project
+- How to setup an OmegaT team project
+- How to use OmegaT from the command line to work in localization pipelines
+- How to use machine translation and MT "post-edit"
+- How to convert back the translated files to texi format
+- How to install translated texi files for use in Emacs
-->