[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug-gnu-libiconv] Feature request on translitterate
From: |
Laurent Lyaudet |
Subject: |
Re: [bug-gnu-libiconv] Feature request on translitterate |
Date: |
Tue, 17 Apr 2018 20:05:54 +0200 |
Hello,
I also created a feature request for glibc iconv here:
https://sourceware.org/bugzilla/show_bug.cgi?id=23076
And I subscribed to address@hidden
Best regards,
Laurent Lyaudet
2018-04-17 19:22 GMT+02:00 Laurent Lyaudet <address@hidden>:
> Hello,
>
> I have a feature request for libiconv.
> It would be useful if translitteration could be done only from one
> character to one character long string.
> In the context of EDIFACT, or flat files, the length in number of
> characters matters.
> So translitterating "€" to "EUR" is not an option.
> Hence I deactivated //TRANSLIT in our source code.
>
> However if translitteration could be done only when the result is one
> character long that would still be useful.
> It could also truncate the translitteration to one character, like "€" to "E".
> I don't know what would be the best way to implement a feature
> //TRANSLITONETOONE.
>
> Maybe the more general way of implementing it would be to have a new
> parameter for choosing the "translitteration profile", which yields
> two choices : either predefined translitteration profiles (classic,
> onetoonetruncate, onetoonediscard), integrated in libiconv, or user
> defined profiles.
>
> Let me know what you think about it, please.
>
> Best regards,
> Laurent Lyaudet
>
> PS : I'm not subscribed to address@hidden
>
> PPS : You can also iconv first, using translitteration, and then
> truncate your fields for EDIFACT or flat files, but it's not a
> satisfactory method since information at the end of a field may be
> more important than 10 new characters from the translitteration part.