From b882d4ef11b4d12cc16face4a0e80818045a2aa3 Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Sat, 23 Dec 2017 10:34:42 +0200 Subject: [PATCH] Fix problems with ligatures in PDF version of ELisp manual * doc/lispref/strings.texi (Case Conversion): Avoid problems with ligatures in printed versions of the manual. (Bug#29818) --- doc/lispref/strings.texi | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/doc/lispref/strings.texi b/doc/lispref/strings.texi index 09c3bdf71f6..24d3ee45877 100644 --- a/doc/lispref/strings.texi +++ b/doc/lispref/strings.texi @@ -1197,6 +1197,7 @@ a character, functions are unable to perform proper substitution and result may differ compared to treating a one-character string. For example: +@ifnottex @example @group (upcase "fi") ; note: single character, ligature "fi" @@ -1207,6 +1208,19 @@ example: @result{} 64257 ; i.e. ?fi @end group @end example +@end ifnottex +@iftex +@example +@group +(upcase "fi") ; note: single character, ligature "fi" + @result{} "FI" +@end group +@group +(upcase ?fi) + @result{} 64257 ; i.e. ?fi +@end group +@end example +@end iftex To avoid this, a character must first be converted into a string, using @code{string} function, before being passed to one of the casing -- 2.39.2