| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Unacccented Fractions |
| Date: | 2017-03-22 02:05:39 |
| Message-ID: | a229da9a-f47b-7953-d61c-0c47bf5ec29b@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/13/17 23:01, David E. Wheeler wrote:
> I noticed that unaccent.rules has spaces in front of the unaccented representation of fraction glyphs:
> This makes sense to me, as I’d like “1¼”, for example to become “1 1/4”. However, that’s not what seems to happen:
These leading spaces come all the way from the input files that are used
to produce the unaccent rules, where they are presumably put for exactly
the reason you point out. However, the unaccent lexer is not prepared
for that. It just looks for any amount of whitespace separating the two
data columns. So that might have to be fixed.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-03-22 02:10:59 | Re: Speedup twophase transactions |
| Previous Message | Haribabu Kommi | 2017-03-22 01:51:54 | Re: [WIP] RE: DECLARE STATEMENT setting up a connection in ECPG |