[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [11/27] Short presentation about translating the Emacs manuals at th
Re: [11/27] Short presentation about translating the Emacs manuals at the coming EmacsConf
Tue, 30 Nov 2021 00:29:50 +0900
> On Nov 28, 2021, at 20:15, Gavin Smith <email@example.com> wrote:
> On Wed, Nov 24, 2021 at 08:59:30AM +0900, Jean-Christophe Helary wrote:
>> Good morning everybody,
>> I’ll be making a shot presentation about translating the Emacs manuals in
>> OmegaT next Saturday. The presentation is 9 min long. There will also be a
>> short Q&A. Of course the Texinfo format is what I discuss most, and how to
>> handle it gracefully in OmegaT.
>> It will be in broken English, with English/French/Japanese captions :-)
> I see there is a video up on that page with your presentation.
The video was linked to after the presentation was broadcast.
> I haven't looked into it recently but I believe the help2man project
> did a good job with getting their manual translated. They put parts
> of the manual in a POT file
> So I have help2man manuals on my system in at least Spanish, Brazillian
> Portuguese, French, Polish, German, Ukrainian and Chinese. I'm not aware
> of any other manual being translated so widely. I guess their approach
> could be copied by Emacs and others, if it's not being done already. I
> don't know what exactly they do or how that would work with OmegaT, but
> I definitely agree that smoothing workflows for translators is a very
> good idea.
As I suggest in the video, OmegaT is a tool for professional translators, so
unless you want to work on your own on a big piece of documentation, for ex, if
you just want to update a few strings in the latest version of your favourite
software, then just working from the PO file should be enough (although I
always work in OmegaT projects even for super small PO jobs).
I mention clumsy web interfaces in the presentation and that’s really what it
is about: either you use a web-based collaborative tool for low-level
commitment, or you (eventually) use pro-tools, just like some people use emacs
even for basic writing tasks.
What I showed was a PO based demonstration. As long as people in a team use PO,
whatever tool is used to translate the thing, the result will be a PO file and
things will work.
If OmegaT had a native Texinfo filter (which would be a good thing too), that
would be a bit more difficult to merge different processes, but not impossible.
Jean-Christophe Helary @brandelune