From: Kevin Vigouroux via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Kevin Vigouroux <ke.vigouroux@laposte.net>
Subject: Re: A not so short introduction to ConTeXt Mark IV
Date: Wed, 28 Jul 2021 16:33:23 +0200 [thread overview]
Message-ID: <878s1q7bkc.fsf@laposte.net> (raw)
In-Reply-To: <f09a5d48-e17a-94f3-853e-454369bfcbf5@azules.eu> (garulfo@azules.eu's message of "Tue, 5 Jan 2021 21:31:22 +0100")
I am not a translator but I think that working from XLIFF documents
would make the translation a bit easier.
XLIFF makes it possible to follow the translation process, at least
partially.
For example, if the translation tools implement the "Change Tracking
Extension" module defined in the latest XLIFF specification (v2.1), you
can track the status of elements. The "property" attribute can indicate
a new level: for example, the translator who changed the "state" (XLIFF
attribute) of the translation: initial, translated, reviewed, final.
[1] https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xliff
[2] http://docs.oasis-open.org/xliff/xliff-core/v2.1/xliff-core-v2.1.pdf
Unfortunately, translators would need to use translation tools based on
the latest XLIFF specification (v2) to take advantage of this. However,
someone will eventually be able to use the tools at their disposal.
Garulfo <garulfo@azules.eu> writes:
> Does anybody has a guide about "how to set up a documentation
> translation project with git ?".
> One requirement will probably to define how propositions are
> officially validated. Does it requires Joaquín to learn how to use git
> ? Can we just work by sending files (or patches) to Joaquín who will
> update with a single git command ?
--
Best regards,
Kevin Vigouroux
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2021-07-28 14:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 9:45 Joaquín Ataz López
2021-01-03 10:32 ` Saša Janiška
2021-01-03 14:37 ` Garulfo
2021-01-03 16:42 ` Mojca Miklavec
2021-01-03 18:08 ` Hans Hagen
2021-01-05 20:31 ` Garulfo
2021-01-06 0:36 ` Bruce Horrocks
2021-01-06 5:26 ` Joaquín Ataz López
2021-01-06 12:08 ` Hans Hagen
2021-07-28 14:33 ` Kevin Vigouroux via ntg-context [this message]
2021-07-28 19:11 ` Kevin Vigouroux via ntg-context
2021-01-03 18:56 ` Joaquín Ataz López
2021-01-03 10:40 ` Alain Delmotte
2021-01-03 18:42 ` BPJ
2021-01-03 19:00 ` Joaquín Ataz López
2021-01-03 21:02 ` BPJ
2021-01-03 21:11 ` denis.maier
2021-01-03 21:25 ` Hans Hagen
2021-01-03 21:24 ` Hans Hagen
2021-01-03 22:59 ` Henning Hraban Ramm
2021-01-04 13:02 ` Migrating from LaTeX (was: A not so short introduction to ConTeXt Mark IV) BPJ
2021-01-04 13:28 ` Taco Hoekwater
2021-01-04 14:21 ` Hans Hagen
2021-01-04 15:54 ` Henning Hraban Ramm
2021-01-04 20:19 ` Migrating from LaTeX jbf
2021-01-04 13:18 ` A not so short introduction to ConTeXt Mark IV Ulrike Fischer
2021-01-04 14:30 ` Hans Hagen
2021-01-04 14:53 ` Ulrike Fischer
2021-01-04 16:32 ` Joaquín Ataz López
2021-01-05 9:04 ` Hans Hagen
2021-01-04 16:02 ` Henning Hraban Ramm
2021-01-04 16:13 ` Henning Hraban Ramm
2021-01-06 7:17 ` Augusto Stoffel
2021-01-03 21:27 ` denis.maier
2021-01-04 16:44 ` Aditya Mahajan
2021-01-08 13:01 ` Robert Zydenbos
[not found] <mailman.2967.1609923358.1206.ntg-context@ntg.nl>
2021-01-11 15:08 ` Ivan Pešić
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878s1q7bkc.fsf@laposte.net \
--to=ntg-context@ntg.nl \
--cc=ke.vigouroux@laposte.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).