public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pebolle at tiscali dot nl" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug manual/12047] [PATCH] [TRIVIAL] Fix typo (LC_TYPE -> LC_CTYPE)
Date: Tue, 06 Mar 2012 11:45:00 -0000	[thread overview]
Message-ID: <bug-12047-131-1Ev4wkwspw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12047-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=12047

--- Comment #4 from Paul Bolle <pebolle at tiscali dot nl> 2012-03-06 11:44:43 UTC ---
(In reply to comment #3)
> Thanks, I've committed the manual patch. 

0) Thanks.

> You'll need to send the translation
> fixes to the respective translation teams; we only import translations
> unmodified from the Translation Project, not change them locally in glibc.

1) Looking at my patch again it seems these are just outdated translations (ie,
the typo in the original string was corrected but the translations aren't yet
based on the corrected string). So once these translations are redone they will
use the correct string. There's little point in sending these fixes to the
translations teams. These are probably aware that their translations aren't up
to date.

2) It looks like I have an excuse to do nothing about the translations!

-- 
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.


  parent reply	other threads:[~2012-03-06 11:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-12047-131@http.sourceware.org/bugzilla/>
2012-02-17 17:56 ` jsm28 at gcc dot gnu.org
2012-03-06 11:45 ` pebolle at tiscali dot nl [this message]
2014-06-30  8:00 ` fweimer at redhat dot com
2010-09-21 17:44 [Bug manual/12047] New: " pebolle at tiscali dot nl
2010-09-21 17:45 ` [Bug manual/12047] " pebolle at tiscali dot nl
2010-09-21 17:49 ` pebolle at tiscali dot nl

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-12047-131-1Ev4wkwspw@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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).