From: Christoph Bauer <Christoph.Bauer@lms-gmbh.de>
Cc: cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: [Christoph.Bauer@lms-gmbh.de: HP-UX: link error]
Date: Thu, 23 Mar 2006 12:51:53 +0100 [thread overview]
Message-ID: <26EB47FDD566A7469FC862DAF373792FE20E62@kaiserslautern1.lmsintl.com> (raw)
>
> So <sys/_mbstate_t.h> is not included (_LIBC in not defined).
> When I define MULTIBYTE_IS_FORMAT_SAFE in config.h, the build
> succeeds.
This was just a stupid test. As formerly written with
-D_INCLUDE__STDC_A1_SOURCE the definition of MULTIBYTE_IS_FORMAT_SAFE
isn't necessary.
>
> That does not necessarily mean it is correct to define that
> symbol. Here's the explanation of it:
>
> /* Do multibyte processing if multibytes are supported, unless
> multibyte sequences are safe in formats. Multibyte sequences are
> safe if they cannot contain byte sequences that look like format
> conversion specifications. The GNU C Library uses UTF8 multibyte
> encoding, which is safe for formats, but strftime.c can be used
> with other C libraries that use unsafe encodings. */
> #define DO_MULTIBYTE (HAVE_MBLEN && ! MULTIBYTE_IS_FORMAT_SAFE)
>
> So, are multibyte sequences safe on your system?
man page of printf(3S) says:
Locale
The LC_CTYPE category affects the following features:
+ Plain characters within format strings are interpreted as
single byte and/or multibyte characters.
+ Field width is given in terms of bytes. As characters are
placed on the output stream, they are interpreted as single
byte or multibyte characters and the field width is
decremented by the length of the character.
+ Precision is given in terms of bytes. As characters are
placed on the output stream, they are interpreted as single
byte or multibyte characters and the precision is decremented
by the length of the character.
+ The return value is given in terms of bytes. As characters
are placed on the output stream, they are interpreted as
single byte or multibyte characters and the byte count that
makes up the return value is incremented by the length of the
character.
The LC_NUMERIC category determines the radix character used to print
floating-point numbers, and the thousands' grouping characters if the
grouping flag ' is on.
International Code Set Support
Single byte character code sets are supported. Multibyte character
code sets are also supported as described in the LC_CTYPE category
above.
So it depends on LC_CTYPE.
next reply other threads:[~2006-03-23 11:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 11:51 Christoph Bauer [this message]
2006-03-23 23:09 ` [Christoph.Bauer@lms-gmbh.de: HP-UX: link error] Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2006-03-27 9:01 Christoph Bauer
2006-03-24 8:47 Christoph Bauer
2006-03-23 11:34 Christoph Bauer
2006-03-23 9:47 Christoph Bauer
2006-03-23 23:09 ` Richard Stallman
2006-03-20 16:29 Bauer, Christoph
2006-03-21 19:22 ` Richard Stallman
2006-03-21 19:23 ` Richard Stallman
2006-03-17 16:30 Richard Stallman
2006-03-19 15:14 ` Chong Yidong
2006-03-19 18:09 ` Sascha Wilde
2006-03-20 15:05 ` Richard Stallman
2006-03-21 6:19 ` Ken Raeburn
2006-03-21 22:29 ` Richard Stallman
2006-03-22 5:08 ` Ken Raeburn
2006-03-22 23:01 ` Kim F. Storm
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=26EB47FDD566A7469FC862DAF373792FE20E62@kaiserslautern1.lmsintl.com \
--to=christoph.bauer@lms-gmbh.de \
--cc=cyd@stupidchicken.com \
--cc=emacs-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 public inbox
https://git.savannah.gnu.org/cgit/emacs.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).