[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #30172] Converting strings lossy results to different strings than
From: |
Fred Kiefer |
Subject: |
[bug #30172] Converting strings lossy results to different strings than on OS X |
Date: |
Mon, 16 Aug 2010 15:00:32 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-0.1.1 Firefox/3.6.8 |
Follow-up Comment #6, bug #30172 (project gnustep):
GNUstep is doing the lossy conversion by using the translit flag of iconv.
The documentation for iconv states:
"When the string "//TRANSLIT" is appended to tocode, transliteration is
activated. This means that when a character cannot be represented in the
target character set, it can be approximated through one or several characters
that look similar to the original character."
This sounds just like the thing we want to do. And your example shows that
this conversion is really eager to provide the best possible transliteration.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?30172>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bug #30172] Converting strings lossy results to different strings than on OS X,
Fred Kiefer <=