From: Ricardo Wurmus <rekado@elephly.net>
To: ng0 <ng0@n0.is>
Cc: Guile User <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: Website translations with Haunt
Date: Sat, 16 Dec 2017 10:54:15 +0100 [thread overview]
Message-ID: <87k1xnngl4.fsf@elephly.net> (raw)
In-Reply-To: <20171215120628.6u3yfwndme6kl2ua@abyayala>
ng0 <ng0@n0.is> writes:
> Christopher Lemmer Webber transcribed 1.4K bytes:
>> pelzflorian (Florian Pelz) writes:
>>
>> > I want to ask for your thoughts on my new solution since translations
>> > are probably important to many Haunt users. In particular, I believe
>> > there was some discussion on Website translation on the Guile or Guix
>> > lists as well.
>>
>> And not just important to Haunt... many sxml using projects!
>
> What's the difference (except for the visible syntax/writing) between
> SXML and XML? When I've looked into translations not just prep came to
> my mind but XML has native translation support - just no one wants to
> work with plain XML when it can be avoided ;)
I would not call this “native translation support”. There is a
specification for tags and XPath rules that extract text from XML
documents.
Here’s an example relating to text segmentation:
https://www.w3.org/TR/xml-i18n-bp/#DevSeg
This doesn’t help us much, though. It is an example of a rule set to
extract strings in a way that is sensible for a translator.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-12-16 9:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-09 18:06 Website translations with Haunt pelzflorian (Florian Pelz)
2017-12-09 18:15 ` ng0
2017-12-09 21:08 ` pelzflorian (Florian Pelz)
2017-12-09 22:29 ` ng0
2017-12-13 14:53 ` pelzflorian (Florian Pelz)
2017-12-10 15:22 ` Matt Wette
2017-12-10 19:21 ` pelzflorian (Florian Pelz)
2017-12-10 22:35 ` Matt Wette
2017-12-12 7:51 ` pelzflorian (Florian Pelz)
2017-12-12 8:03 ` ng0
2017-12-12 9:30 ` pelzflorian (Florian Pelz)
2017-12-12 13:45 ` Matt Wette
2017-12-12 18:47 ` pelzflorian (Florian Pelz)
2017-12-10 23:00 ` Matt Wette
2017-12-12 8:17 ` pelzflorian (Florian Pelz)
2017-12-14 9:16 ` Ludovic Courtès
2017-12-14 13:23 ` Thompson, David
2017-12-15 11:39 ` pelzflorian (Florian Pelz)
2017-12-15 14:01 ` pelzflorian (Florian Pelz)
2017-12-15 3:48 ` Christopher Lemmer Webber
2017-12-15 8:34 ` pelzflorian (Florian Pelz)
2017-12-15 12:06 ` ng0
2017-12-15 14:25 ` pelzflorian (Florian Pelz)
2017-12-16 9:54 ` Ricardo Wurmus [this message]
2017-12-16 12:37 ` pelzflorian (Florian Pelz)
2017-12-16 15:26 ` sirgazil
2017-12-16 19:30 ` pelzflorian (Florian Pelz)
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k1xnngl4.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=ng0@n0.is \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).