From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Guile User <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: Website translations with Haunt
Date: Sat, 9 Dec 2017 22:08:57 +0100 [thread overview]
Message-ID: <20171209210857.GA1064@floriannotebook.localdomain> (raw)
In-Reply-To: <20171209181529.xzpfpjl4y4ugrqhv@abyayala>
[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]
On Sat, Dec 09, 2017 at 06:15:29PM +0000, ng0 wrote:
> Hey Florian,
>
> interesting work. I opened a bug a very long time ago for Guix,
> and the content applied to Guile (as well as to the project
> I initiated (infotropique) and very likely many other Haunt
> using websites like Haunt itself, 8sync, etc).
>
> I've seen the first versions of this a while back in the code
> for your website, I'll check out the changes soon, exciting work!
>
Oh, thank you. :) Some code is not clean and more proof-of-concept.
> My idea was a reimplementation of prep (a text format and html document
> generator that is capable to include multiple languages in its source
> files, written by lynX back in the early 90s (or earlier) iirc (and
> still used today).
>
Hmm I can find neither prep nor lynX in a quick Web search.
Po files are separate from the source code files. I don’t know if
prep has such a separation or if such a separation really is better.
Then again, another issue with HTML/SHTML is that e.g. a hyperlink within
the text is difficult to handle with traditional format strings
without breaking the separation:
* The link text should be translated in the context of the text
surrounding the link
* but the link formatting and maybe the link destination URL maybe
should not be changeable by the translator.
Does prep handle this?
Regards,
Florian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-12-09 21:08 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) [this message]
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
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=20171209210857.GA1064@floriannotebook.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
/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).