From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean-Christophe Helary Newsgroups: gmane.emacs.devel Subject: Re: Emacs as an XLIFF editor Date: Tue, 28 Sep 2021 23:17:22 +0900 Message-ID: References: <87ilyrwc4a.fsf@laposte.net> <87zgs1cmxa.fsf@laposte.net> <87v92oolrw.fsf@laposte.net> <87v92l15oo.fsf@laposte.net> <0D74A79F-AEC2-4A6B-B6E4-C4296159950F@traduction-libre.org> <87fsto7rr3.fsf_-_@laposte.net> Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11081"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Kevin Vigouroux Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Sep 28 16:19:00 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mVDwi-0002gS-5o for ged-emacs-devel@m.gmane-mx.org; Tue, 28 Sep 2021 16:19:00 +0200 Original-Received: from localhost ([::1]:53134 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mVDwg-0008In-Kl for ged-emacs-devel@m.gmane-mx.org; Tue, 28 Sep 2021 10:18:58 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58212) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mVDvO-0007AG-Ep for emacs-devel@gnu.org; Tue, 28 Sep 2021 10:17:38 -0400 Original-Received: from relay2-d.mail.gandi.net ([217.70.183.194]:47199) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mVDvH-0007m8-AG for emacs-devel@gnu.org; Tue, 28 Sep 2021 10:17:38 -0400 Original-Received: (Authenticated sender: lists@traduction-libre.org) by relay2-d.mail.gandi.net (Postfix) with ESMTPSA id BB74C4000E; Tue, 28 Sep 2021 14:17:27 +0000 (UTC) In-Reply-To: <87fsto7rr3.fsf_-_@laposte.net> X-Mailer: Apple Mail (2.3654.120.0.1.13) Received-SPF: pass client-ip=217.70.183.194; envelope-from=lists@traduction-libre.org; helo=relay2-d.mail.gandi.net X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:275695 Archived-At: > On Sep 28, 2021, at 22:29, Kevin Vigouroux via Emacs development = discussions. wrote: >=20 > Jean-Christophe Helary writes: >=20 >>> On Sep 28, 2021, at 17:10, Kevin Vigouroux via Emacs development = discussions. wrote: >>>=20 >>> Richard Stallman writes: >>>=20 >>>>> XLIFF documents are validated using XML schemas. These schemas are >>>>> currently not supported by Emacs. >>>>=20 >>>> Is there other free software that can do this? >>>> Emacs could invoke it in a subprocess. >>>=20 >>> LemMinX [1] is released under the Eclipse Public License 2.0. It >>> depends on Eclipse LSP4J (license EPL 2.0 [2]). This LSP server=20 >>> is used by an Emacs LSP mode (lsp-mode). >>>=20 >>> [1] https://github.com/eclipse/lemminx/blob/master/LICENSE >>> [2] https://github.com/eclipse/lsp4j/blob/main/LICENSE >>=20 >> All the applications from Maxprograms are Eclipse 1.0 licensed. The >> developer is the editor of the current XLIFF standard (2.2), along >> with being a top class expert in the localization area. >>=20 >> https://maxprograms.com/products/index.html >=20 > Yes, but the idea is to be able to parse the sources of the = programming > languages supported by Emacs. I don't know if it's possible, but then, > from the parsing, build the XLIFF file. Programming languages supported by emacs already have gettext, = documentation has po4a, and PO is a robust enough format. I'm not sure = how using XLIFF for them would add any value to the process. Also there = are PO/XLIFF round-trip converters already. Creating a translation file and parsing/translating it are 2 very = different processes and if the goal is to design a translation = application inside Emacs, then creating PO/XLIFF files is fully outside = the scope. There are already plenty of very robust filters/converters that = accomplish that already. > The final goal is to design a translation application inside Emacs. In > this case, Emacs should also edit the XLIFF file. I understand that. May I suggest that you read the thread that I = mentioned earlier if you've not done so already? If that is the goal, = the main task is indeed to properly *edit* the XLIFF file, and probably = the way the PO mode does that for PO can be used as a base. > OpenXLIFF Filters can=E2=80=99t do that [1]. I never suggested that OpenXLIFF could do that. Maxprograms=E2=80=99 = XLIFF editor is Swordfish. OpenXLIFF is just the filtering/conversion = part. --=20 Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/