Thread: Cleaning up a text import
Hi
I imported some text using the Quantum GIS dxf2postgis which somehow became distorted through the import.
What should have been imported was TK-208.
What I got was %%UTK-208%%U.
Perhaps I did something wrong while using dxf2postgis?
Otherwise, I can trim the text using - select trim (both '% U' from '%%UTK-208%%U') .
However I would need to know what it is that needs to be trimmed from future imports, which isn't always possible.
I would appreciate any suggestions on how to resolve this.
Many thanks in advance.
Bob
I imported some text using the Quantum GIS dxf2postgis which somehow became distorted through the import.
What should have been imported was TK-208.
What I got was %%UTK-208%%U.
Perhaps I did something wrong while using dxf2postgis?
Otherwise, I can trim the text using - select trim (both '% U' from '%%UTK-208%%U') .
However I would need to know what it is that needs to be trimmed from future imports, which isn't always possible.
I would appreciate any suggestions on how to resolve this.
Many thanks in advance.
Bob
On 06/28/2013 09:36 AM, Bob Pawley wrote: > Hi > > I imported some text using the Quantum GIS dxf2postgiswhich somehow > became distorted through the import. > > What should have been imported was TK-208. > > What I got was %%UTK-208%%U. > > Perhaps I did something wrong while using dxf2postgis? > > Otherwise, I can trim the text using - select trim (both '% U' from > '%%UTK-208%%U') . > > However I would need to know what it is that needs to be trimmed from > future imports, which isn't always possible. > > I would appreciate any suggestions on how to resolve this. Have not used dxf2postgis, but at a guess the %%U markers are used to denote Unicode? Maybe look in the dxf2postgis docs to see what it has to say about encoding? > > Many thanks in advance. > > Bob > -- Adrian Klaver adrian.klaver@gmail.com