unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 46872@debbugs.gnu.org
Subject: [bug#46872] [PATCH] doc: Define canned recipes for creating translated manuals.
Date: Thu, 20 Jan 2022 16:44:14 +0000	[thread overview]
Message-ID: <d204f88a7ff395dc2c8a97628247fabfbb1d278c.camel@telenet.be> (raw)
In-Reply-To: <874k5y8puv.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]

Ludovic Courtès schreef op do 20-01-2022 om 15:05 [+0100]:
> [...] However, it doesn’t work as expected:
> 
> --8<---------------cut here---------------start------------->8---
> $ rm -f doc/contributing.fr.texi
> $ make doc/contributing.fr.texi
> make: 'doc/contributing.fr.texi' is up to date.
> $ ls -l doc/contributing.fr.texi
> ls: ne eblas atingi 'doc/contributing.fr.texi': Dosiero aŭ dosierujo ne ekzistas
> --8<---------------cut here---------------end--------------->8---
> 
> If I inline the expansion of ‘translate_chapter_command’, everything
> works as expected.
> 
> My GNU Make is rusty and fuzzy, but I wonder if we can expand text that
> includes tabs.  I vaguely remember that I’d usually define functions
> that would expand the whole text: target/prerequisites + commands.

My GNU Make is practically non-existent, e.g. I always forget whether
to use $< or $@ or $? (does $? even exist?) ...

> WDYT?

... so as long as it works, it is seems ok to me.

Greetings,
Maxime



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

      reply	other threads:[~2022-01-20 20:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 13:40 [bug#46872] [PATCH] doc: Define canned recipes for creating translated manuals Maxime Devos
2022-01-20 14:05 ` Ludovic Courtès
2022-01-20 16:44   ` Maxime Devos [this message]

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=d204f88a7ff395dc2c8a97628247fabfbb1d278c.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=46872@debbugs.gnu.org \
    --cc=ludo@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.
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).