- 14 Mar, 2005 2 commits
-
-
Bruce Momjian authored
Roland Volkmann
-
Bruce Momjian authored
-
- 07 Mar, 2005 1 commit
-
-
Bruce Momjian authored
UNICODE => UTF8 ALT => WIN866 WIN => WIN1251 TCVN => WIN1258 The old codes continue to work.
-
- 03 Dec, 2004 1 commit
-
-
Bruce Momjian authored
-
- 02 Dec, 2004 1 commit
-
-
Bruce Momjian authored
John Hansen
-
- 17 Sep, 2004 1 commit
-
-
Peter Eisentraut authored
-
- 29 Aug, 2004 1 commit
-
-
Bruce Momjian authored
-
- 15 Mar, 2004 1 commit
-
-
Tatsuo Ishii authored
Still some works needed: - UTF-8, MULE_INTERNAL always returns 1
-
- 29 Nov, 2003 1 commit
-
-
PostgreSQL Daemon authored
make sure the $Id tags are converted to $PostgreSQL as well ...
-
- 25 Sep, 2003 1 commit
-
-
Peter Eisentraut authored
terms, add some clarifications, fix some untranslatable attempts at dynamic message building.
-
- 04 Aug, 2003 1 commit
-
-
Bruce Momjian authored
-
- 27 Jul, 2003 1 commit
-
-
Tom Lane authored
the bulk of the heavy lifting ...
-
- 11 Jan, 2003 1 commit
-
-
Tatsuo Ishii authored
-
- 04 Sep, 2002 1 commit
-
-
Bruce Momjian authored
-
- 03 Sep, 2002 1 commit
-
-
Peter Eisentraut authored
referring to "multibyte" where it really means character encoding.
-
- 13 Jun, 2002 1 commit
-
-
Tatsuo Ishii authored
(ODBC support has not been committed yet. left for Hiroshi...)
-
- 05 Mar, 2002 1 commit
-
-
Bruce Momjian authored
> > > > It was made to cope with encoding such as an Asian bloc in 7.2Beta2. > > > > > > > > Added ServerEncoding > > > > Korean (JOHAB), Thai (WIN874), > > > > Vietnamese (TCVN), Arabic (WIN1256) > > > > > > > > Added ClientEncoding > > > > Simplified Chinese (GBK), Korean (UHC) > > > > > > > > > > > > > http://www.sankyo-unyu.co.jp/Pool/postgresql-7.2b2.newencoding.diff.tar.gz > > > > (608K) > > > > > > Looks good. I need some people to review this for me. > > > > For me they look good too. The only missing part is a > > documentation. I will ask him to write it up. If he couldn't, I will > > do it for him. > > > The diff is 3mb > > > but appears to address only additions to multibyte. I have attached a > > > list of files it modifies. Also, look at the sizes of the mb/ > > > directory. It is getting large: > > > > > > 4 ./CVS > > > 6 ./Unicode/CVS > > > 3433 ./Unicode > > > 6197 . > > > > Yes. We definitely need the on-the-fly encoding addition capability: > > i.e. CREATE CHRACTER SET in the future... > > -- > > Tatsuo Ishii > > > > Address chainge. http://www.sankyo-unyu.co.jp/Pool/postgresql-7.2.newencoding.diff.gz Add PsqlODBC and document ...etc patch. Eiji Tokuya
-
- 28 Oct, 2001 1 commit
-
-
Bruce Momjian authored
spacing. Also adds space for one-line comments.
-
- 25 Oct, 2001 1 commit
-
-
Bruce Momjian authored
tests pass.
-
- 15 Oct, 2001 1 commit
-
-
Tatsuo Ishii authored
-
- 11 Oct, 2001 1 commit
-
-
Tatsuo Ishii authored
-
- 23 Sep, 2001 1 commit
-
-
Tatsuo Ishii authored
-
- 21 Sep, 2001 1 commit
-
-
Tom Lane authored
Avoid use of prototype-less function pointers in MB code.
-
- 11 Sep, 2001 1 commit
-
-
Tatsuo Ishii authored
* Reject character sequences those are not valid in their charset
-
- 06 Sep, 2001 1 commit
-
-
Tatsuo Ishii authored
------------------------------------------------------------------- Subject: Re: [PATCHES] encoding names From: Karel Zak <zakkr@zf.jcu.cz> To: Peter Eisentraut <peter_e@gmx.net> Cc: pgsql-patches <pgsql-patches@postgresql.org> Date: Fri, 31 Aug 2001 17:24:38 +0200 On Thu, Aug 30, 2001 at 01:30:40AM +0200, Peter Eisentraut wrote: > > - convert encoding 'name' to 'id' > > I thought we decided not to add functions returning "new" names until we > know exactly what the new names should be, and pending schema Ok, the patch not to add functions. > better > > ...(): encoding name too long Fixed. I found new bug in command/variable.c in parse_client_encoding(), nobody probably never see this error: if (pg_set_client_encoding(encoding)) { elog(ERROR, "Conversion between %s and %s is not supported", value, GetDatabaseEncodingName()); } because pg_set_client_encoding() returns -1 for error and 0 as true. It's fixed too. IMHO it can be apply. Karel PS: * following files are renamed: src/utils/mb/Unicode/KOI8_to_utf8.map --> src/utils/mb/Unicode/koi8r_to_utf8.map src/utils/mb/Unicode/WIN_to_utf8.map --> src/utils/mb/Unicode/win1251_to_utf8.map src/utils/mb/Unicode/utf8_to_KOI8.map --> src/utils/mb/Unicode/utf8_to_koi8r.map src/utils/mb/Unicode/utf8_to_WIN.map --> src/utils/mb/Unicode/utf8_to_win1251.map * new file: src/utils/mb/encname.c * removed file: src/utils/mb/common.c -- Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/ C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
-
- 19 Apr, 2001 1 commit
-
-
Tatsuo Ishii authored
given.
-
- 22 Mar, 2001 1 commit
-
-
Bruce Momjian authored
-
- 08 Mar, 2001 1 commit
-
-
Tom Lane authored
of a counted input string. Marinos Yannikos' recent crash report turns out to be due to applying pg_ascii2wchar_with_len to a TEXT object that is smack up against the end of memory. This is the second just-barely- reproducible bug report I have seen that traces to some bit of code fetching one more byte than it is allowed to. Let's be more careful out there, boys and girls. While at it, I changed the code to not risk a similar crash when there is a truncated multibyte character at the end of an input string. The output in this case might not be the most reasonable output possible; if anyone wants to improve it further, step right up...
-
- 11 Feb, 2001 1 commit
-
-
Tatsuo Ishii authored
-
- 10 Feb, 2001 1 commit
-
-
Tom Lane authored
are now separate files "postgres.h" and "postgres_fe.h", which are meant to be the primary include files for backend .c files and frontend .c files respectively. By default, only include files meant for frontend use are installed into the installation include directory. There is a new make target 'make install-all-headers' that adds the whole content of the src/include tree to the installed fileset, for use by people who want to develop server-side code without keeping the complete source tree on hand. Cleaned up a whole lot of crufty and inconsistent header inclusions.
-
- 12 Oct, 2000 1 commit
-
-
Tatsuo Ishii authored
currently ISO8859-[1-5] and EUC_JP are supported. support for other encodings will be coming soon.
-
- 27 Aug, 2000 1 commit
-
-
Tatsuo Ishii authored
to int so that they return the number of whcars.
-
- 12 Apr, 2000 1 commit
-
-
Bruce Momjian authored
-
- 25 Jan, 2000 1 commit
-
-
Tatsuo Ishii authored
(EUC_CN does have only code set 0 and 1)
-
- 11 Jul, 1999 1 commit
-
-
Tatsuo Ishii authored
-
- 25 May, 1999 1 commit
-
-
Bruce Momjian authored
-
- 25 Apr, 1999 1 commit
-
-
Tom Lane authored
it failed to cover the case where high bits of char are 100 or 101. Not sure if fix is right, but it agrees with pg_utf_mblen ... and it doesn't lock up ...
-
- 24 Mar, 1999 1 commit
-
-
Tatsuo Ishii authored
-
- 02 Feb, 1999 1 commit
-
-
Bruce Momjian authored
o allow to use Big5 (a Chinese encoding used in Taiwan) as a client encoding. In this case the server side encoding should be EUC_TW o add EUC_TW and Big5 test cases to the regression and the mb test (contributed by Jonah Kuo) o fix mistake in include/mb/pg_wchar.h. An encoding id for EUC_TW was not correct (was 3 and now is 4) o update documents (doc/README.mb and README.mb.jp) o update psql helpfile (bin/psql/psqlHelp.h) -- Tatsuo Ishii t-ishii@sra.co.jp
-
- 01 Sep, 1998 1 commit
-
-
Bruce Momjian authored
-