Re: More Code Page wierdness
| От | Magnus Hagander |
|---|---|
| Тема | Re: More Code Page wierdness |
| Дата | |
| Msg-id | 6BCB9D8A16AC4241919521715F4D8BCE47657B@algol.sollentuna.se обсуждение исходный текст |
| Ответ на | More Code Page wierdness (Simon Riggs <simon@2ndquadrant.com>) |
| Ответы |
Re: More Code Page wierdness
Re: More Code Page wierdness Re: More Code Page wierdness |
| Список | pgsql-hackers-win32 |
> > Not sure what would be involved in requiring the file to be UTF8. > > Notepad can certainly handle UTF8, but I wonder how much > would need to > > bec hanged in pg... > > I think it would Just Work, since UTF8 is an ASCII superset, Ok. > whereas apparently some of Windows' code pages are not :-( > (which is proof of brain death in Redmond if I ever saw it). I've never seen one that changes any chars <= 127. But it's possible the editor in this case wrote down a file in the wrong charset. Looking at http://www.microsoft.com/globaldev/reference/wincp.mspx, "*" is 002A in *every single one*, inlcuding japanese. Looking at http://www.microsoft.com/globaldev/reference/oem/437.htm, it shows that it's 002A in the very encoding Simon said was used in this case. So it is in http://www.microsoft.com/globaldev/reference/oem/850.htm, which is the OEM codepage used in Swedish windows. I'm having trouble seeing why '*' would have a different value in different codepages. I'm wondering if we're going down the wrong road completely here? //Magnus
В списке pgsql-hackers-win32 по дате отправления: