26450abe18
* src/rtl/cdpapi.c
+ Extended to accept real codepage names where Harbour
"codepage" names (which are really codepage + collation
combinations, like "HUWIN") are accepted. It makes it
possible to do:
hb_translate( "stuff", "cp1250", "cp852" )
This mod is implemented on the surface in simple way,
which implies some notices and warnings:
- real codepages are accepted also in places where
you're better to specify a Harbour CP tied to a
collation, f.e. in hb_cdpSelect() or Set( _SET_DBCODEPAGE ).
In such case it's important to see that an arbitrary
Harbour CP will be selected from those linked to the
requested real codepage.
- 'hb_cdpSelect( "iso8859-2" ); ? hb_cdpSelect()'
will not show "iso8859-2", but one of the corresponding
Harbour CPs.
- you cannot REQUEST a specific real codepage,
but you can request all of them which are linked
to a Harbour CPs using '#include "hbextcdp.ch"'.
; NOTE: With more deep rework, which I most probably
won't be able to ever do, Harbour's concept of
CPs should be split into real codepages and
collation modules, than interfaces identified
where a collation is expected vs. real codepages,
or both, question how to do that without break
too much compatibility and question how to fit
current HB_CP_RAW CPs into that model. For former
problem, notation like 'HU.cp852' might be possible
solution, where any of the parts can be omitted,
depending on context: 'HU' or 'cp852'.