Re: UTF-8
[email protected] Mon, 20 Sep 2021 15:45:00 +0200
| Newsgroups | gmane.comp.lang.4gl.aubit.general |
|---|---|
| Message-ID | <[email protected]> |
Thank you. For now I have recreated the database and changed the locale of the debian system to iso-8859-15 locales and all works immediate correct. Perhaps I try your suggestions later. Are you sure your Postgres database is also utf-8? I created the database with iso-8859-15 encoding this way: CREATE DATABASE <dbname> LC_COLLATE 'en_US.iso885915' LC_CTYPE 'en_US.iso885915' ENCODING ISO885915 TEMPLATE template0; I did likewise to create the database with utf-8 encoding CREATE DATABASE <dbname> LC_COLLATE 'en_US.utf8' LC_CTYPE 'en_US.utf8' ENCODING UTF8 TEMPLATE template0; On 17-9-2021 13:14, Bernard Moreton wrote: > I've used Aubit with Postgres and UTF-8 characters for the last 14 years or so. > I had problems at first, but resolved (most of) them by setting > A4GL_UI=TUI_wide > in my .aubitrc > > There would still be problems if a utf8 character occurred at the end boundary of a form field, I guess; but that hasn't been a problem for me. Yet! > > And because Aubit counts bytes not characters, string slicing (string_var[n,m]) is hazardous, as is upshift/downshift - but such things can be got round by using psql functions (not wholly transportable), or C code. > > Let me know if I can help with any particular problem. > > Best wishes, > R.J. Baart _______________________________________________ Aubit4gl-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/aubit4gl-discuss