Preston Landers wrote: > > http://www.postgresql.org/docs/8.0/interactive/multibyte.html#CHARSET-TABLE > > I would humbly suggest a few improvements to that Encodings table to > improve the clarity. > > Many of the entries clearly indicate the language or writing system, such > as WIN1256 = "Windows CP1256 (Arabic)" > > I would suggest that every single entry should be described that way with > the common language or writing system name. Even Unicode could say "All > languages". > > In particular, the "WIN" encoding just says "CP1251" -- this is Cyrillic > (Russian) but some people might just see the WIN and assume it's the > character set that Western/US Windows uses (CP 1252). > > It's an easy mistake to make and one I see repeated frequently on other > web pages (calling Windows "Western" CP 1251.) Someone reading English > language docs and seeing a "WIN" character set might naturally assume that > it is the English Windows character set. (Which BTW is not currently > supported by PG for conversions.) > > Some more examples that might improve clarity: > > LATIN5 should say "Turkish" > > LATIN6 should say "Nordic" > > ALT and KOI8 should say "Cyrillic" (or Russian)
Great. Would you submit a patch to the SGML sources? -- Bruce Momjian | http://candle.pha.pa.us [email protected] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
