Opened 16 years ago

Closed 16 years ago

Last modified 16 years ago

#264 closed defect (fixed)

ISO dump contains UTF characters

Reported by: christoph Owned by: christoph
Priority: major Milestone: 2.5 release
Component: database Version:
Keywords: Cc:

Description

please check both mysql and postgresql

Attachments (1)

test_utf8.sed (660 bytes ) - added by christoph 16 years ago.
for the utf dump...it also contained weird characters

Download all attachments as: .zip

Change History (9)

comment:1 by christoph, 16 years ago

Component: administrationdatabase

comment:2 by christoph, 16 years ago

Owner: changed from mapbender_dev@… to christoph

comment:3 by christoph, 16 years ago

I guess its due to some WMS data. Check the WMS and remove those with faulty data.

comment:4 by arnulf, 16 years ago

Owner: changed from christoph to arnulf

comment:5 by jml, 16 years ago

Here is a quick and dirty search-and-replace script that converts the faulty chars in the actual pgsql-data.sql (2.5.rc6) to normal ASCII chars using sed.

1) Create a named e.g. 'replaceunicode.sed' in the iso directory with the following contents:

s/A?AE'A...A,/ss/g;
s/A?AE'A,A?/ae/g;
s/A?AE'A,A 1\/4/ue/g;
s/A?AE'A?a,?AA 3\/4 /Ae/g;
s/A?aEUR?A?a,?AA?/l/g;
s/A?AE'A+aEUR(TM)A?aEURsA,A?/o/g;
s/A?AE'A+aEUR(TM)A?aEURsA,A-/i/g;
s/A?AE'A+aEUR(TM)A?aEURsA,A(C)/e/g;
s/A?AE'A,A(C)/e/g;
s/A?AE'A,A-/i/g;

2) call sed using:

sed -f replaceunicode.sed pgsql_data.sql > pgsql_data.latin1.sql

3) after creating the schema, load the pgsql_data.latin1.sql instead of the (unchanged) pgsql_data.sql into the db.

Note: It worked fine for me with 2.5.rc6, but: no warranty :)

comment:6 by christoph, 16 years ago

Owner: changed from arnulf to christoph

comment:7 by christoph, 16 years ago

Resolution: fixed
Status: newclosed

thanks jml for this great workaround!! It has been a great help.

by christoph, 16 years ago

Attachment: test_utf8.sed added

for the utf dump...it also contained weird characters

Note: See TracTickets for help on using tickets.