Daniël Mantione wrote:
Before Windows 2000 Windows used fixed length, after Windows 2000 it was
variable length.
And what about windows 2000 itself? :-)
Micha
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mail
Op Tue, 4 Dec 2007, schreef Jonas Maebe:
>
> On 02 Dec 2007, at 20:40, Florian Klaempfl wrote:
>
> > BTW: for other encodings it doesn't work either on unix ...
>
> Are widestrings supposed to be UTF-16 or UCS-2 on unix? Currently they are
> UTF-16, but a lot of routines seem to assume UCS-2
y
Op Tue, 4 Dec 2007, schreef Jonas Maebe:
> Marc Weustink wrote on di, 04 dec 2007:
>
> > Jonas Maebe wrote:
> > >
> > > Are widestrings supposed to be UTF-16 or UCS-2 on unix? Currently
> > > they are UTF-16, but a lot of routines seem to assume UCS-2 (like
> > > the generic WideStringToUCS4S
Marc Weustink wrote on di, 04 dec 2007:
Jonas Maebe wrote:
Are widestrings supposed to be UTF-16 or UCS-2 on unix? Currently
they are UTF-16, but a lot of routines seem to assume UCS-2 (like
the generic WideStringToUCS4String, and the unix
Lower/UpperWideString)
It is a bit confusin
Jonas Maebe wrote:
On 02 Dec 2007, at 20:40, Florian Klaempfl wrote:
BTW: for other encodings it doesn't work either on unix ...
Are widestrings supposed to be UTF-16 or UCS-2 on unix? Currently they
are UTF-16, but a lot of routines seem to assume UCS-2 (like the generic
WideStringToUCS4S
On 02 Dec 2007, at 20:40, Florian Klaempfl wrote:
BTW: for other encodings it doesn't work either on unix ...
Are widestrings supposed to be UTF-16 or UCS-2 on unix? Currently
they are UTF-16, but a lot of routines seem to assume UCS-2 (like the
generic WideStringToUCS4String, and the uni
On 03 Dec 2007, at 08:44, Florian Klaempfl wrote:
Making such tests is not easy because they depend on the system
locale.
Using only latin characters make it work on all systems but with latin
only also the default implemenation works and renders the test
useless.
Using non-latin character
Jonas Maebe schrieb:
> Florian Klaempfl wrote on zo, 02 dec 2007:
>
>> Felipe Monteiro de Carvalho schrieb:
>
>> Well, unix people don't seem to care about completing the cwstring unit
>> :)
>
> At least this unix person didn't know those routines were mandatory,
> otherwise I would have added t
> Florian Klaempfl wrote on zo, 02 dec 2007:
>
> > Felipe Monteiro de Carvalho schrieb:
>
> > Well, unix people don't seem to care about completing the cwstring unit
> > :)
>
> At least this unix person didn't know those routines were mandatory,
> otherwise I would have added them a long time
Florian Klaempfl wrote on zo, 02 dec 2007:
Felipe Monteiro de Carvalho schrieb:
Well, unix people don't seem to care about completing the cwstring unit
:)
At least this unix person didn't know those routines were mandatory,
otherwise I would have added them a long time ago. There don't se
Florian Klaempfl wrote:
Marc Weustink schrieb:
Florian Klaempfl wrote:
Marc Weustink schrieb:
Florian Klaempfl wrote:
Felipe Monteiro de Carvalho schrieb:
On Dec 2, 2007 1:04 AM, Marc Weustink <[EMAIL PROTECTED]> wrote:
From the logs I understand that there is a "real" managed utf8string
t
Marc Weustink schrieb:
> Florian Klaempfl wrote:
>> Marc Weustink schrieb:
>>> Florian Klaempfl wrote:
Felipe Monteiro de Carvalho schrieb:
> On Dec 2, 2007 1:04 AM, Marc Weustink <[EMAIL PROTECTED]> wrote:
>> From the logs I understand that there is a "real" managed utf8string
>>
Felipe Monteiro de Carvalho schrieb:
> On Dec 2, 2007 12:27 PM, Florian Klaempfl <[EMAIL PROTECTED]> wrote:
>> No. The rtl assumes that ansistrings always use the encoding used by the
>> system.
>
> And what if utf-8 is the system encoding? Which is the case on many unixes.
Then ansistrings are u
On Dec 2, 2007 12:27 PM, Florian Klaempfl <[EMAIL PROTECTED]> wrote:
> No. The rtl assumes that ansistrings always use the encoding used by the
> system.
And what if utf-8 is the system encoding? Which is the case on many unixes.
Not to mention that on this case AnsiStrUpper already doesn't work.
Florian Klaempfl wrote:
Marc Weustink schrieb:
Florian Klaempfl wrote:
Felipe Monteiro de Carvalho schrieb:
On Dec 2, 2007 1:04 AM, Marc Weustink <[EMAIL PROTECTED]> wrote:
From the logs I understand that there is a "real" managed utf8string
type (other than utf8string = type string).
No, c
Marc Weustink schrieb:
> Florian Klaempfl wrote:
>> Felipe Monteiro de Carvalho schrieb:
>>> On Dec 2, 2007 1:04 AM, Marc Weustink <[EMAIL PROTECTED]> wrote:
From the logs I understand that there is a "real" managed utf8string
type (other than utf8string = type string).
>>> No, currently
Florian Klaempfl wrote:
Felipe Monteiro de Carvalho schrieb:
On Dec 2, 2007 1:04 AM, Marc Weustink <[EMAIL PROTECTED]> wrote:
From the logs I understand that there is a "real" managed utf8string
type (other than utf8string = type string).
No, currently utf8string = type string is about all su
Marco van de Voort schrieb:
>> Marco van de Voort schrieb:
the beginning this is okay.
The API, however, should be solid and future proof, as it needs to be
backward compatible.
>>> Since we are talking about expanding the widestringmanager, I'm considering
>>> adding mblen. Th
> Marco van de Voort schrieb:
> >> the beginning this is okay.
> >>
> >> The API, however, should be solid and future proof, as it needs to be
> >> backward compatible.
> >
> > Since we are talking about expanding the widestringmanager, I'm considering
> > adding mblen. This because I encountered
Felipe Monteiro de Carvalho schrieb:
> On Dec 2, 2007 1:04 AM, Marc Weustink <[EMAIL PROTECTED]> wrote:
>> From the logs I understand that there is a "real" managed utf8string
>> type (other than utf8string = type string).
>
> No, currently utf8string = type string is about all support
> implemen
Marco van de Voort schrieb:
>> Op Fri, 30 Nov 2007, schreef Felipe Monteiro de Carvalho:
>>
>>> What do other FPC developers think of this?
>>>
>>> Should it be the responsability of the fpc user to write it's own
>>> routines to override the output of the widestring manager or should
>>> FPC provi
On Dec 2, 2007 1:04 AM, Marc Weustink <[EMAIL PROTECTED]> wrote:
> From the logs I understand that there is a "real" managed utf8string
> type (other than utf8string = type string).
No, currently utf8string = type string is about all support
implemented for such type.
--
Felipe Monteiro de Carv
Florian Klaempfl wrote:
Felipe Monteiro de Carvalho schrieb:
Hello,
Today I took a look at what would be necessary to implement
controlling the output of the widestring manager, and implementing
this looks rather trivial.
The only thing we need is a switch, to control if widestrings should
be
> Op Fri, 30 Nov 2007, schreef Felipe Monteiro de Carvalho:
>
> > What do other FPC developers think of this?
> >
> > Should it be the responsability of the fpc user to write it's own
> > routines to override the output of the widestring manager or should
> > FPC provide this mechanism?
>
> The
Felipe Monteiro de Carvalho schrieb:
> Hello,
>
> Today I took a look at what would be necessary to implement
> controlling the output of the widestring manager, and implementing
> this looks rather trivial.
>
> The only thing we need is a switch, to control if widestrings should
> be converted t
Op Fri, 30 Nov 2007, schreef Felipe Monteiro de Carvalho:
> What do other FPC developers think of this?
>
> Should it be the responsability of the fpc user to write it's own
> routines to override the output of the widestring manager or should
> FPC provide this mechanism?
The default widestri
What do other FPC developers think of this?
Should it be the responsability of the fpc user to write it's own
routines to override the output of the widestring manager or should
FPC provide this mechanism?
thanks,
--
Felipe Monteiro de Carvalho
___
fpc
Ummm, I didn't think of it this way before, but it could be a solution.
--
Felipe Monteiro de Carvalho
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
Felipe Monteiro de Carvalho wrote:
Hello,
Today I took a look at what would be necessary to implement
controlling the output of the widestring manager, and implementing
this looks rather trivial.
The only thing we need is a switch, to control if widestrings should
be converted to the current lo
Op Tue, 27 Nov 2007, schreef Felipe Monteiro de Carvalho:
> On Nov 27, 2007 8:58 PM, Daniël Mantione <[EMAIL PROTECTED]> wrote:
> > This function has a code page parameter, which allows you to specify
> > the code page you want to use?
>
> umm ... I missread it and thougth that only the values
On Tue, 27 Nov 2007, Daniël Mantione wrote:
>
>
> Op Tue, 27 Nov 2007, schreef Felipe Monteiro de Carvalho:
>
> > On Nov 27, 2007 8:37 PM, Daniël Mantione <[EMAIL PROTECTED]> wrote:
> > > A more generic solution is necessary; one can want to output strings in a
> > > specific encoding, utf-8
On Nov 27, 2007 8:58 PM, Daniël Mantione <[EMAIL PROTECTED]> wrote:
> This function has a code page parameter, which allows you to specify
> the code page you want to use?
umm ... I missread it and thougth that only the values on the table
are possible =)
ok, so:
OutputFormat: TEncoding;
TEncod
Op Tue, 27 Nov 2007, schreef Felipe Monteiro de Carvalho:
> On Nov 27, 2007 8:37 PM, Daniël Mantione <[EMAIL PROTECTED]> wrote:
> > A more generic solution is necessary; one can want to output strings in a
> > specific encoding, utf-8 is only one of the specific encodings that are
> > demanded.
On Nov 27, 2007 8:37 PM, Daniël Mantione <[EMAIL PROTECTED]> wrote:
> A more generic solution is necessary; one can want to output strings in a
> specific encoding, utf-8 is only one of the specific encodings that are
> demanded. Therefore a boolean is not a good solution.
Win32Wide2Ansi just call
Op Tue, 27 Nov 2007, schreef Felipe Monteiro de Carvalho:
> Hello,
>
> Today I took a look at what would be necessary to implement
> controlling the output of the widestring manager, and implementing
> this looks rather trivial.
>
> The only thing we need is a switch, to control if widestrings
Hello,
Today I took a look at what would be necessary to implement
controlling the output of the widestring manager, and implementing
this looks rather trivial.
The only thing we need is a switch, to control if widestrings should
be converted to the current locale or to utf-8. In the case of curr
36 matches
Mail list logo
