To clarify with an analogy, it's the exact same
thing as if IANA granted Harbour exclusive use
for the _function name_ 'HARBOUR_PROJECT()'.
This would allow us to implement whatever
functionality behind it, but the name would be
ours. Similarly to domain names.
Brgds,
Viktor
On 2008.11.06., at 1
Hi Randy,
Hi Viktor,
Sorry to jump in mid-stream, but my understanding is that the
Windows-1252 codepage would be required for backwards DOS/Cl*pper
compatibility - Is that not true?
No. DOS/Clipper used the 'IBM*' or DOS*/MS-DOS*
codepages, which are also covered in Harbour
(albeit not a
Hi Viktor,
Sorry to jump in mid-stream, but my understanding
is that the Windows-1252 codepage would be
required for backwards DOS/Cl*pper compatibility - Is that not true?
Regards,
Randy
At 01:14 PM 11/6/2008, you wrote:
Miguel,
IANA assigns _names_.
This only means that this object what
Miguel,
IANA assigns _names_.
This only means that this object what is the non-official
codepage created by Microsoft, has a standard name
"Windows-1252" (and not "Win-1252", or "Win1252"). It
also assures that this name won't be assigned for other
purposes.
Such names can be used in certain in
Please read this page:
http://en.wikipedia.org/wiki/Windows-1252
seem Windows-1252 is aproved too by iana (Internet Assigned Numbers
Authority (IANA))
What more do you need ?
Best regards
Miguel Angel Marchuet
Szakáts Viktor escribió:
ormation:
"Code page name" are to "
Przemyslaw Czerpak escribió:
On Wed, 05 Nov 2008, Miguel Angel Marchuet wrote:
Hi Miguel,
Please, STOP
this is part of MSDN documentation:
MS documentsion does not creates any standards in my country
and I hope will never do but you can contact with my government
and try to change it ;-)
Actually they managed to do this locally with their
office document standards a while ago :( I'm not sure
what was the deal with Poland, but MS did use dirty
tricks in several countries.
Brgds,
Viktor
On 2008.11.05., at 18:00, Przemyslaw Czerpak wrote:
On Wed, 05 Nov 2008, Miguel Angel Marchue
Miguel, if you're using MSDN as the sole source of your
information, you shouldn't wonder it's centering the world
around Microsoft, since they are the authors.
Please read other facts. "Windows-1252" was derived from
ISO-8859-1 standard (by Microsoft) with added (non-standard)
features ("embrace
ormation:
"Code page name" are to "Char Set" as you see some times are
confused by the alias name, any people can think incorrectly
that iso-8859-1 is the same than windows-1252 but are real
different Char Set
Yes, exactly. Very important that ISO-8859-1 is an official
standard, while Windo
On Wed, 05 Nov 2008, Miguel Angel Marchuet wrote:
Hi Miguel,
> Please, STOP
> this is part of MSDN documentation:
MS documentsion does not creates any standards in my country
and I hope will never do but you can contact with my government
and try to change it ;-)
best regards,
Przemek
Please, STOP
this is part of MSDN documentation:
as can be possible read are different code page of the same family.
I'm not talking about of its aliases.
Spanish (Modern Sort) | Western European (Windows)
Code page: 1252 <--
family code page:1252
Code page n
On Wed, 05 Nov 2008, Miguel Angel Marchuet wrote:
Hi Miguel,
> Windows-1252 is the standard used at windows application.
CP-1252 is local MS name. Nothing more.
> ISO-8859-1 is the standard used at Linux and html application,
ISO-8859-1 is standardized name and official standard encoding in
ma
ormation:
"Code page name" are to "Char Set" as you see some times are confused
by the alias name, any people can think incorrectly
that iso-8859-1 is the same than windows-1252 but are real different
Char Set
Yes, exactly. Very important that ISO-8859-1 is an official
standard, while Window
3) Add ES850 according to the 'modern' collation.
+1) Think about a way to 'map' old ESMWIN name to new ESWIN.
Ok, but for blackguard compatibilities will be needed alias ESMWIN.
I'm not sure if there is a better way to do it, but
maybe I'll just add an additional file with a new
file and old
To me it looks like we'd need to do three things:
1) Fix the internal CP in current ESWIN and ESWINM files.
(I'll do this ASAP)
2) Rename Clipper compatibility ESWIN, ESISO, ES850 files
to ESWINC, ESISOC, ES850C and add comment that these
are 'legacy' or Clipper compatibility ones (some
the named code page ESMWIN is the correct to use at ansi spanish
applications. all other are invalids to work or only to read old buggy
indexes incorrect ordered.
"ANSI" means Windows in this context.
ESMWIN is based on:
Windows locale: Spanish (Modern Sort)
Locale ID: 0xC0A
Lo
the named code page ESMWIN is the correct to use at ansi spanish
applications. all other are invalids to work or only to read old buggy
indexes incorrect ordered.
ESMWIN is based on:
Windows locale: Spanish (Modern Sort)
Locale ID: 0xC0A
Location designator: Modern_Spanish
Code pa
If what you wanted was to create a ESISO, you can add only this, but
do it well and not copying the codepage ESMWIN
About doing it well.
Current eswin and eswinm (esmwin) is setup to use ISO-8859-1
CP internally. If this is right, they are in fact wrongly named
es_win_, and they should be name
If the intention was to break code on the whim of changing the name,
you've accomplished.
Miguel, keep out your comments of this kind of tone
from this list, if I may kindly ask you.
First of all it's not obligatory to participate (or even
to use Harbour), secondly you can have exactly one gue
If the intention was to break code on the whim of changing the name, you've
accomplished.
If what you wanted was to create a ESISO, you can add only this, but do it well
and not copying the codepage ESMWIN
ESMWIN codepage is a consensus among various programmers to make it compatible with the
2008-11-03 11:20 UTC+0200 Viktor Szakats (harbour.01 syenar hu)
* common.mak
* source/codepage/Makefile
- source/codepage/cpesmwin.c
+ source/codepage/cpeswinm.c
+ source/codepage/cpesiso.c
+ source/codepage/cpesisom.c
* Renamed cpesmwin -> cpeswinm (ESMWIN -> ESWINM) (INCOMPATIBLE)
21 matches
Mail list logo
