I'v sent Greg the files, edit in Excel with all umlauts in the german language. With a regular GIS-application is this not possible - the umlauts appears correct.

with Excel:





with qGIS:





Another sample for problems with dbf processing in Excel You can test self.
- Open the dbf in Excel (for me v2003),
- Change the FONT values (it's a text column)
- If You save in Excel, this will be a numeric column and the result: the VALUE-text in the AT5 is disappeared!


Best wishes
Jörg

In order to avoid problems with DBF files because of Excel, I am using DBF Viewer 2000 to edit DBF files in a fast way, without any problems uptil now.

Seems like Excel is exporting in the IBM 850 codepage.

en.wikipedia.org/wiki/Code_page_850

Your o-umlaut is encoded as code point 0x94 (148) which is a double quote in the Win 1252 codepage.
Your u-umlaut is encoded as code point 0x81 (129)
Your SS is encoded as code point 0xE1 (225)

This is a simple fix.

Create a file called "IMC_Wegpunkte.cpg" with the following text in it "850" - no double quotes.

The IMC will know to interpret this file as IBM 850 rather than Windows 1252.

The IMC has functional support for 59 different codepages on shapefiles.

The names can either be specified for their formal text values or the ESRI aliasing values - support.esri.com/cn/knowledgebase/techarticles/detail/21106

"Apple Roman"
"Big5"
"Big5-HKSCS"
"EUC-JP"
"EUC-KR"
"GB18030-0"
"IBM 850"/"850"
"IBM 866"/"866"
"IBM 874"/"874"
"ISO 2022-JP"
"ISO 8859-1"/"88591"
"ISO 8859-2"/"88592"
"ISO 8859-3"/"88593"
"ISO 8859-4"/"88594"
"ISO 8859-5"/"88595"
"ISO 8859-6"/"88596"
"ISO 8859-7"/"88597"
"ISO 8859-8"/"88598"
"ISO 8859-9"/"88599"
"ISO 8859-10"/"885910"
"ISO 8859-13"/"885913"
"ISO 8859-14"
"ISO 8859-15"/"885915"
"ISO 8859-16"
"ISCII-Bng"
"ISCII-Dev"
"ISCII-Gjr"
"ISCII-Knd"
"ISCII-Mlm"
"ISCII-Ori"
"ISCII-Pnj"
"ISCII-Tlg"
"ISCII-Tml"
"JIS X 0201"
"JIS X 0208"
"KOI8-R"
"KOI8-U"
"MuleLao-1"
"ROMAN8"
"Shift-JIS"/"SJIS"
"TIS-620"
"TSCII"
"UTF-8"/"65001"
"UTF-16"
"UTF-16BE"
"UTF-16LE"
"UTF-32"
"UTF-32BE"
"UTF-32LE"
"Windows-1250"/"1250"
"Windows-1251"/"1251"
"Windows-1252"/"1252"
"Windows-1253"/"1253"
"Windows-1254"/"1254"
"Windows-1255"/"1255"
"Windows-1256"/"1256"
"Windows-1257"/"1257"
"Windows-1258"/"1258"
"WINSAMI2"

Yes Greg, this is very interesting and can help all professional users with GIS attainments. We all learn more and more and that make fun!!!


But the conclusion for the non-proffesional user is yet - do not use Excel for dbf-editing.

And i believe, it's better so.

The possibilities in qGis are sufficient for all IMC-requirements.

Danny's tip is also a really good help.

And i think we all wait for Matt's AT5-point-solution in RM ...


Best wishes
Jörg