From: "euloanty at live dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/29023] ti_ER locale can cause confusion for parser
Date: Mon, 04 Apr 2022 10:35:23 +0000 [thread overview]
Message-ID: <bug-29023-716-ywKwJXGykZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29023-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29023
--- Comment #4 from cqwrteur <euloanty at live dot com> ---
(In reply to Andreas Schwab from comment #3)
> Inline comments are common in locale definition files. A parser will have
> to cope.
but how the parse is going to know here?
it cannot differentiate whether it is string or part of string.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-04-04 10:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 10:07 [Bug localedata/29023] New: " euloanty at live dot com
2022-04-04 10:11 ` [Bug localedata/29023] " euloanty at live dot com
2022-04-04 10:12 ` euloanty at live dot com
2022-04-04 10:15 ` schwab@linux-m68k.org
2022-04-04 10:35 ` euloanty at live dot com [this message]
2022-04-06 0:05 ` carlos at redhat dot com
2022-04-06 0:11 ` carlos at redhat dot com
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=bug-29023-716-ywKwJXGykZ@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@sourceware.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.
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).