From: "Jeroen Roovers (jer)" <jer@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in dev-python/unidecode: metadata.xml ChangeLog
Date: Thu, 16 Jan 2014 17:20:53 +0000 (UTC) [thread overview]
Message-ID: <20140116172053.F0E432004C@flycatcher.gentoo.org> (raw)
jer 14/01/16 17:20:53
Modified: metadata.xml ChangeLog
Log:
Spelling.
(Portage version: 2.2.8/cvs/Linux x86_64, signed Manifest commit with key A792A613)
Revision Changes Path
1.3 dev-python/unidecode/metadata.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/unidecode/metadata.xml?rev=1.3&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/unidecode/metadata.xml?rev=1.3&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/unidecode/metadata.xml?r1=1.2&r2=1.3
Index: metadata.xml
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-python/unidecode/metadata.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- metadata.xml 20 Oct 2013 19:25:03 -0000 1.2
+++ metadata.xml 16 Jan 2014 17:20:53 -0000 1.3
@@ -7,7 +7,7 @@
<longdescription lang="en">
This is a Python port of Text::Unidecode Perl module
-It often happens that you have text data in Unicode, but you need to represent it in ASCII. For example when integrating with legacy code that doesn't support Unicode, or for ease of entry of non-Roman names on a US keyboard, or when constructing ASCII machine identifiers from human-readable Unicode strings that should still be somewhat intelligeble (a popular example of this is when making an URL slug from an article title).
+It often happens that you have text data in Unicode, but you need to represent it in ASCII. For example when integrating with legacy code that doesn't support Unicode, or for ease of entry of non-Roman names on a US keyboard, or when constructing ASCII machine identifiers from human-readable Unicode strings that should still be somewhat intelligible (a popular example of this is when making a URL slug from an article title).
In most of these examples you could represent Unicode characters as "???" or "\15BA\15A0\1610", to mention two extreme cases. But that's nearly useless to someone who actually wants to read what the text says.
1.9 dev-python/unidecode/ChangeLog
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/unidecode/ChangeLog?rev=1.9&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/unidecode/ChangeLog?rev=1.9&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/unidecode/ChangeLog?r1=1.8&r2=1.9
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-python/unidecode/ChangeLog,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- ChangeLog 20 Oct 2013 19:25:03 -0000 1.8
+++ ChangeLog 16 Jan 2014 17:20:53 -0000 1.9
@@ -1,6 +1,9 @@
# ChangeLog for dev-python/unidecode
-# Copyright 1999-2013 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/dev-python/unidecode/ChangeLog,v 1.8 2013/10/20 19:25:03 sochotnicky Exp $
+# Copyright 1999-2014 Gentoo Foundation; Distributed under the GPL v2
+# $Header: /var/cvsroot/gentoo-x86/dev-python/unidecode/ChangeLog,v 1.9 2014/01/16 17:20:53 jer Exp $
+
+ 16 Jan 2014; Jeroen Roovers <jer@gentoo.org> metadata.xml:
+ Spelling.
20 Oct 2013; Stanislav Ochotnicky <sochotnicky@gentoo.org> metadata.xml:
Move to maintainer-needed
next reply other threads:[~2014-01-16 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 17:20 Jeroen Roovers (jer) [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-06-04 7:28 [gentoo-commits] gentoo-x86 commit in dev-python/unidecode: metadata.xml ChangeLog Justin Lecher (jlec)
2013-10-20 19:25 Stanislav Ochotnicky (sochotnicky)
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=20140116172053.F0E432004C@flycatcher.gentoo.org \
--to=jer@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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