all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Julien Lepiller <julien@lepiller.eu>
Cc: Luis Felipe <luis.felipe.la@protonmail.com>,
	"48637@debbugs.gnu.org" <48637@debbugs.gnu.org>
Subject: [bug#48637] [PATCH] website: Add publications page
Date: Wed, 26 May 2021 12:00:18 +0200	[thread overview]
Message-ID: <20210526095955.obtu772oolv4lkrb@pelzflorian.localdomain> (raw)
In-Reply-To: <68748170-9C48-45F1-98D7-6152572D6D61@lepiller.eu>

On Tue, May 25, 2021 at 10:03:01PM -0400, Julien Lepiller wrote:
> Le 25 mai 2021 16:16:42 GMT-04:00, Luis Felipe <luis.felipe.la@protonmail.com> a écrit :
> >#:authors (G_ "Jane Roe, Eva Lua and Luis Felipe")
> 
> I think so, but I think we'll have to test, because I don't really know the i18n process either for the website ^^'

Yes, it is correct and the best way, but testing by running the
sexp-xgettext script is good too.


> >That's what I thought, and I was about to ask if it was possible to
> >have <date> and <authors> instead of <1> and <2>. I guess not...
> >
> >I need a course on the i18n system :)

I wanted the sexp-xgettext i18n system so developers would not have to
add a tag name to every element …  Well, we can use regexp helper
function find-empty-element like website/sexp-xgettext.scm uses at the
beginning of the deconstruct procedure:

(define (find-empty-element msgstr name)
  "Return the regex match structure for the empty tag for XML
element of type NAME inside MSGSTR.  If the element does not exist or
is more than the empty tag, #f is returned."
  (string-match (string-append "<" (regexp-quote name) "/>") msgstr))

and call it on a translation with G_, but I would prefer not to
increase code complexity in the website.

Regards,
Florian




  reply	other threads:[~2021-05-26 10:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24 23:35 [bug#48637] [PATCH] website: Add publications page Luis Felipe via Guix-patches via
2021-05-25 13:44 ` pelzflorian (Florian Pelz)
2021-05-25 14:37   ` Luis Felipe via Guix-patches via
2021-05-25 18:21     ` pelzflorian (Florian Pelz)
2021-05-25 19:46       ` Luis Felipe via Guix-patches via
2021-05-25 19:58         ` Julien Lepiller
2021-05-25 20:16           ` Luis Felipe via Guix-patches via
2021-05-26  2:03             ` Julien Lepiller
2021-05-26 10:00               ` pelzflorian (Florian Pelz) [this message]
2021-05-26 14:06                 ` Luis Felipe via Guix-patches via
2021-05-26 17:41                   ` Julien Lepiller
2021-05-26 18:25                     ` Luis Felipe via Guix-patches via
2021-05-26 18:42                       ` Julien Lepiller
2021-05-26 19:05                         ` Luis Felipe via Guix-patches via
2021-05-25 18:35     ` pelzflorian (Florian Pelz)
2021-05-25 19:14       ` Luis Felipe via Guix-patches via
2021-05-28 11:06 ` Ludovic Courtès
2021-05-28 15:20   ` Luis Felipe via Guix-patches via
2021-05-29 10:25     ` Ludovic Courtès
2021-06-02 19:31   ` Luis Felipe via Guix-patches via
2021-06-02 20:28     ` Julien Lepiller
2021-06-02 21:52       ` Luis Felipe via Guix-patches via
2021-06-02 23:28         ` Julien Lepiller
2021-06-03  9:40     ` Ludovic Courtès
2021-06-03 10:37       ` Julien Lepiller
2021-06-03 13:39         ` Luis Felipe via Guix-patches via
2021-06-03 19:50           ` Luis Felipe via Guix-patches via
2021-06-03 20:37           ` Ludovic Courtès
2021-06-03 21:50             ` Luis Felipe via Guix-patches via
2021-06-04 15:38               ` Ludovic Courtès

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=20210526095955.obtu772oolv4lkrb@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=48637@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    --cc=luis.felipe.la@protonmail.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.