Attachments (1)
Change History (9)
comment:1 by , 16 years ago
Component: | administration → database |
---|
comment:2 by , 16 years ago
Owner: | changed from | to
---|
comment:3 by , 16 years ago
comment:4 by , 16 years ago
Owner: | changed from | to
---|
comment:5 by , 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 , 16 years ago
Owner: | changed from | to
---|
comment:7 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
thanks jml for this great workaround!! It has been a great help.
by , 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.
I guess its due to some WMS data. Check the WMS and remove those with faulty data.