From: taylanbayirli@gmail.com ("Taylan Ulrich Bayırlı/Kammer")
To: guix-devel@gnu.org
Subject: doc: Fix syntax errors.
Date: Tue, 25 Nov 2014 14:46:47 +0100 [thread overview]
Message-ID: <87d28b8kag.fsf@taylan.uni.cx> (raw)
Some .texi syntax errors seem to have sneaked in on commit 7fec52b.
===File /home/tub/media/src/guix/0001-doc-Fix-syntax-errors.patch===
From 110e68f04cc9efb8d72d19a401a6ff1ca039c7d4 Mon Sep 17 00:00:00 2001
From: Taylan Ulrich B <taylanbayirli@gmail.com>
Date: Tue, 25 Nov 2014 14:41:02 +0100
Subject: [PATCH] doc: Fix syntax errors.
* doc/guix.texi (Package Naming):
(Fonts): Remove space between '@foo' and '{'.
---
doc/guix.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/guix.texi b/doc/guix.texi
index ec48f4a..a88b774 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -4889,7 +4889,7 @@ already part of the official project name. But @pxref{Python
Modules} and @ref{Perl Modules} for special rules concerning modules for
the Python and Perl languages.
-Font package names are handled differently, @pxref {Fonts}.
+Font package names are handled differently, @pxref{Fonts}.
@node Version Numbers
@@ -4999,7 +4999,7 @@ under a common name, we prefer to package them together as
In the case where several formats of the same font family or font collection
are packaged separately, a short form of the format, prepended by a dash,
is added to the package name. We use @code{-ttf} for TrueType fonts,
-@code {-otf} for OpenType fonts and @code{-type1} for PostScript Type 1
+@code{-otf} for OpenType fonts and @code{-type1} for PostScript Type 1
fonts.
--
2.1.2
============================================================
next reply other threads:[~2014-11-25 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 13:46 "Taylan Ulrich Bayırlı/Kammer" [this message]
2014-11-25 20:58 ` doc: Fix syntax errors Ludovic Courtès
2014-11-25 21:23 ` Taylan Ulrich Bayırlı/Kammer
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=87d28b8kag.fsf@taylan.uni.cx \
--to=taylanbayirli@gmail.com \
--cc=guix-devel@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 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.