From: Luis Felipe via Guix-patches via <guix-patches@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: "48637@debbugs.gnu.org" <48637@debbugs.gnu.org>
Subject: [bug#48637] [PATCH] website: Add publications page
Date: Tue, 25 May 2021 14:37:03 +0000 [thread overview]
Message-ID: <3mZyc8pra0TLSyJS6RlWIrQGBnje7dT_EMRBeOdFC_Z2wsZGoaI1rVNVtoiI57KEOvolEiahl6j7M4UBsoO0NsuieAfDPIkZQ-MR8C5UhAE=@protonmail.com> (raw)
In-Reply-To: <20210525134405.hmevensj5m42iluo@pelzflorian.localdomain>
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, May 25, 2021 1:44 PM, pelzflorian (Florian Pelz) <pelzflorian@pelzflorian.de> wrote:
> On Mon, May 24, 2021 at 11:35:24PM +0000, Luis Felipe via Guix-patches via wrote:
>
> > Hi,
> > This patch adds a new Publications page to the website.
>
> Nice!
>
> I could not test yet, but maybe make the date string in
>
> > +(define (publication->shtml publication)
> >
> > - "Return an SHTML representation of the given publication object.
> > -
> > - PUBLICATION (<publication>)
> > - A publication object as defined in (apps media types)."
> >
> >
> > - `(a
> > - (@ (class "publication-preview")
> > - (href ,(publication-url publication)))
> >
> >
> > -
> > - (h3
> > - (@ (lang ,(publication-language publication))
> >
> >
> > - (class "publication-title"))
> >
> >
> > - ,(publication-title publication))
> >
> >
> > -
> > - (p
> > - (@ (class "publication-info"))
> >
> >
> > - ,(G_ `("Published "
> >
> >
> > - ,(date->string (publication-date publication) "~b ~d, ~Y")
> >
> >
>
> translatable like website/apps/blog/templates/components.scm line 33.
Yeah. Would it as follows? (I still struggle with i18n):
(p
(@ (class "publication-info"))
,(G_ `("Published "
,(date->string (publication-date publication)
(C_ "SRFI-19 date->string format" "~b ~d, ~Y"))
" by "
,(string-join (publication-authors publication) ", "))))
Also, I think the delimiter for "string-join" in the list of authors should be translated because that comma is not used in Japanese, for example. So would it be ok like this:
(p
(@ (class "publication-info"))
,(G_ `("Published "
,(date->string (publication-date publication)
(C_ "SRFI-19 date->string format" "~b ~d, ~Y"))
" by "
,(string-join (publication-authors publication)
(C_ "Separator of items in a list" ", ")))))
I'm still unsure about when I should use a context and when a TRANSLATORS comment...
> > +(define (publication-list-t publications)
> >
> > - "Return the Publication list page in SHTML.
> > -
> > - PUBLICATIONS (list of <publication>)
> > - See the (apps media types) module for information on the
> >
> >
> > - <publication> type."
> >
> >
> > - (theme
> > - #:title (C_ "webpage title" '("Publications"))
> > - #:description
> > - (G_ "A list of written publications about GNU Guix.")
> > - #:keywords
> > - ;; TRANSLATORS: |-separated list of webpage keywords.
> > - (string-split (G_ "Publications|Papers") #\|)
>
> I don’t know, but should there really be only none of the other pages’
> SEO keywords? All other occurrences of #:keywords begin with
>
> GNU|Linux|Unix|Free software
Hmm, I don't know... Last time I checked, I think I saw that search engines care more about the page content than meta keywords. So I don't think it would make a difference.
Also, if it turns out to be important to repeat these keywords in all pages, maybe it would be better to add these by default in (apps base templates theme).
next prev parent reply other threads:[~2021-05-25 14:38 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 [this message]
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)
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='3mZyc8pra0TLSyJS6RlWIrQGBnje7dT_EMRBeOdFC_Z2wsZGoaI1rVNVtoiI57KEOvolEiahl6j7M4UBsoO0NsuieAfDPIkZQ-MR8C5UhAE=@protonmail.com' \
--to=guix-patches@gnu.org \
--cc=48637@debbugs.gnu.org \
--cc=luis.felipe.la@protonmail.com \
--cc=pelzflorian@pelzflorian.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).