Re: BUG #15548: Unaccent does not remove combining diacritical characters
От | Hugh Ranalli |
---|---|
Тема | Re: BUG #15548: Unaccent does not remove combining diacritical characters |
Дата | |
Msg-id | CAAhbUMOHkoN3Jeti4dp1jz3VY=XZPcCqpX=sW=mgmJbdMS--ng@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #15548: Unaccent does not remove combining diacriticalcharacters ("Daniel Verite" <daniel@manitou-mail.org>) |
Ответы |
Re: BUG #15548: Unaccent does not remove combining diacritical characters
|
Список | pgsql-bugs |
On Thu, 13 Dec 2018, 11:26 Daniel Verite <daniel@manitou-mail.org wrote:
Tom Lane wrote:
> Hm, I thought the OP's proposal was just to make unaccent drop
> combining diacriticals independently of context, which'd avoid the
> combinatorial-growth problem.
That's what I was thinking. Given that the accent is separate from the characters, simply dropping it should result in the correct unaccented character.
In that case, this could be achieved by simply appending the
diacriticals themselves to unaccent.rules, since replacement of a
string by an empty string is already supported as a rule.
It doesn't seem like the current file has any of these, but from
https://www.postgresql.org/docs/11/unaccent.html :
"Alternatively, if only one character is given on a line, instances
of that character are deleted; this is useful in languages where
accents are represented by separate characters"
Yes, I had read that in the docs, and that's the approach I planned to take. I'll go ahead and develop a patch, then.
Best wishes,
Hugh
В списке pgsql-bugs по дате отправления: