[DOCS] Suggestion for Encodings table
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) ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [DOCS] Bibliography updates for new editions?
Am Dienstag, 15. Februar 2005 18:11 schrieb Michael Fuhr: > Sure, but why not save them the effort? If somebody (me) is willing > to track down the links, what benefit is there in not providing them? > The Bibliography already provides links to other items -- why not the > books as well? I don't think the publisher's web site is particularly relevant. You might as well link to the authors' home pages as well. And then we start attaching links to everything all over the documentation. In an XLink world, this might make sense, but not right now, I think. The other links lead to the actual document, which is relevant. If there were a functional URN namespace for ISBNs then I would support linking the ISBNs to that. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(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
Re: [DOCS] Bibliography updates for new editions?
Am Mittwoch, 16. Februar 2005 02:07 schrieb Michael Fuhr: > Should I update the biblioentry id's, Yes. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
