public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/14943] Artificial languages
Date: Mon, 11 Mar 2013 22:19:00 -0000 [thread overview]
Message-ID: <bug-14943-131-52i2FPMYPe@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14943-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14943
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
--- Comment #14 from Carlos O'Donell <carlos at redhat dot com> 2013-03-11 22:19:05 UTC ---
(In reply to comment #13)
> So what's the next steps to get this patch landed? Does someone specific need
> to review it?
>
> I think the comments by Keld cover the concerns with the radix point. There are
> also some clarification in a widely respected book about Esperanto grammar
> here:
>
> http://bertilow.com/pmeg/gramatiko/nombroj/matematiko.html
>
> Roughly translated, it says “Don't use a period instead of a comma for
> decimals. The period is used as a decimal sign only in a few countries.
> Esperanto, like most countries and languages, uses a decimal comma”. It also
> shows some examples of using the comma in mathematical writing.
The next step is to post a final patch to libc-alpha@sourceware.org, CC the
people who made comments here, and ask for final review. The post description
of the problem should address the concerns raised in v1 of the patch and if any
changes were made it should list them under a v2 entry.
Make sure to follow:
http://sourceware.org/glibc/wiki/Contribution%20checklist
One you have consensus then a developer with commit permission can check the
patch into master.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-03-11 22:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 12:37 [Bug localedata/14943] New: " michael.moroni at mailoo dot org
2012-12-11 21:26 ` [Bug localedata/14943] " aj at suse dot de
2012-12-11 23:18 ` bugdal at aerifal dot cx
2012-12-12 8:07 ` aj at suse dot de
2012-12-12 8:44 ` schwab@linux-m68k.org
2012-12-12 9:14 ` fweimer at redhat dot com
2012-12-12 21:32 ` bugtrack at roumenpetrov dot info
2012-12-13 1:28 ` bugdal at aerifal dot cx
2012-12-13 6:53 ` aj at suse dot de
2013-01-09 6:05 ` hpa at zytor dot com
2013-03-03 17:51 ` bpeeluk at yahoo dot co.uk
2013-03-04 0:18 ` bugdal at aerifal dot cx
2013-03-04 5:44 ` keld at keldix dot com
2013-03-04 14:34 ` bpeeluk at yahoo dot co.uk
2013-03-08 12:25 ` bpeeluk at yahoo dot co.uk
2013-03-11 22:19 ` carlos at redhat dot com [this message]
2013-11-19 19:25 ` cjlhomeaddress at gmail dot com
2013-11-23 16:59 ` cjlhomeaddress at gmail dot com
2013-11-25 14:55 ` carlos at redhat dot com
2014-06-14 5:37 ` fweimer at redhat dot com
2014-08-28 17:21 ` eichi237 at mailoo dot org
2015-10-16 14:53 ` 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-14943-131-52i2FPMYPe@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).