Tillbaka till svenska Fidonet
English   Information   Debug  
OS2BBS   0/787
OS2DOSBBS   0/580
OS2HW   0/42
OS2INET   0/37
OS2LAN   0/134
OS2PROG   0/36
OS2REXX   0/113
OS2USER-L   207
OS2   0/4779
OSDEBATE   0/18996
PASCAL   0/490
PERL   0/457
PHP   0/45
POINTS   0/405
POLITICS   0/29554
POL_INC   0/14731
PSION   103
R20_ADMIN   1117
R20_AMATORRADIO   0/2
R20_BEST_OF_FIDONET   13
R20_CHAT   0/893
R20_DEPP   0/3
R20_DEV   399
R20_ECHO2   1379
R20_ECHOPRES   0/35
R20_ESTAT   0/719
R20_FIDONETPROG...
...RAM.MYPOINT
  0/2
R20_FIDONETPROGRAM   0/22
R20_FIDONET   0/248
R20_FILEFIND   0/24
R20_FILEFOUND   0/22
R20_HIFI   0/3
R20_INFO2   2632
R20_INTERNET   0/12940
R20_INTRESSE   0/60
R20_INTR_KOM   0/99
R20_KANDIDAT.CHAT   42
R20_KANDIDAT   28
R20_KOM_DEV   112
R20_KONTROLL   0/13030
R20_KORSET   0/18
R20_LOKALTRAFIK   0/24
R20_MODERATOR   0/1852
R20_NC   76
R20_NET200   245
R20_NETWORK.OTH...
...ERNETS
  0/13
R20_OPERATIVSYS...
...TEM.LINUX
  0/44
R20_PROGRAMVAROR   0/1
R20_REC2NEC   534
R20_SFOSM   0/340
R20_SF   0/108
R20_SPRAK.ENGLISH   0/1
R20_SQUISH   107
R20_TEST   2
R20_WORST_OF_FIDONET   12
RAR   0/9
RA_MULTI   106
RA_UTIL   0/162
REGCON.EUR   0/2055
REGCON   0/13
SCIENCE   0/1206
SF   0/239
SHAREWARE_SUPPORT   0/5146
SHAREWRE   0/14
SIMPSONS   0/169
STATS_OLD1   0/2539.065
STATS_OLD2   0/2530
STATS_OLD3   0/2395.095
STATS_OLD4   0/1692.25
SURVIVOR   0/495
SYSOPS_CORNER   0/3
SYSOP   0/84
TAGLINES   0/112
TEAMOS2   0/4530
TECH   0/2617
TEST.444   0/105
TRAPDOOR   0/19
TREK   0/755
TUB   0/290
UFO   0/40
UNIX   0/1316
USA_EURLINK   0/102
USR_MODEMS   0/1
VATICAN   0/2740
VIETNAM_VETS   0/14
VIRUS   0/378
VIRUS_INFO   0/201
VISUAL_BASIC   0/473
WHITEHOUSE   0/5187
WIN2000   0/101
WIN32   0/30
WIN95   0/4275
WIN95_OLD1   0/70272
WINDOWS   0/1517
WWB_SYSOP   0/419
WWB_TECH   0/810
ZCC-PUBLIC   0/1
ZEC   4

 
4DOS   0/134
ABORTION   0/7
ALASKA_CHAT   0/506
ALLFIX_FILE   0/1313
ALLFIX_FILE_OLD1   0/7997
ALT_DOS   0/152
AMATEUR_RADIO   0/1039
AMIGASALE   0/14
AMIGA   0/331
AMIGA_INT   0/1
AMIGA_PROG   0/20
AMIGA_SYSOP   0/26
ANIME   0/15
ARGUS   0/924
ASCII_ART   0/340
ASIAN_LINK   0/651
ASTRONOMY   0/417
AUDIO   0/92
AUTOMOBILE_RACING   0/105
BABYLON5   0/17862
BAG   135
BATPOWER   0/361
BBBS.ENGLISH   0/382
BBSLAW   0/109
BBS_ADS   0/5290
BBS_INTERNET   0/507
BIBLE   0/3563
BINKD   0/1119
BINKLEY   0/215
BLUEWAVE   0/2173
CABLE_MODEMS   0/25
CBM   0/46
CDRECORD   0/66
CDROM   0/20
CLASSIC_COMPUTER   0/378
COMICS   0/15
CONSPRCY   0/899
COOKING   27601
COOKING_OLD1   0/24719
COOKING_OLD2   0/40862
COOKING_OLD3   0/37489
COOKING_OLD4   0/35496
COOKING_OLD5   9370
C_ECHO   0/189
C_PLUSPLUS   0/31
DIRTY_DOZEN   0/201
DOORGAMES   0/1974
DOS_INTERNET   0/196
duplikat   5999
ECHOLIST   0/18295
EC_SUPPORT   0/318
ELECTRONICS   0/359
ELEKTRONIK.GER   1534
ENET.LINGUISTIC   0/13
ENET.POLITICS   0/4
ENET.SOFT   0/11701
ENET.SYSOP   33773
ENET.TALKS   0/32
ENGLISH_TUTOR   0/2000
EVOLUTION   0/1335
FDECHO   0/217
FDN_ANNOUNCE   0/7068
FIDONEWS   23436
FIDONEWS_OLD1   0/49742
FIDONEWS_OLD2   0/35949
FIDONEWS_OLD3   0/30874
FIDONEWS_OLD4   0/37224
FIDO_SYSOP   12841
FIDO_UTIL   0/180
FILEFIND   0/209
FILEGATE   0/212
FILM   0/18
FNEWS_PUBLISH   4155
FN_SYSOP   41520
FN_SYSOP_OLD1   71952
FTP_FIDO   0/2
FTSC_PUBLIC   0/13556
FUNNY   0/4886
GENEALOGY.EUR   0/71
GET_INFO   105
GOLDED   0/408
HAM   0/16041
HOLYSMOKE   0/6791
HOT_SITES   0/1
HTMLEDIT   0/71
HUB203   466
HUB_100   264
HUB_400   39
HUMOR   0/29
IC   0/2851
INTERNET   0/424
INTERUSER   0/3
IP_CONNECT   719
JAMNNTPD   0/233
JAMTLAND   0/47
KATTY_KORNER   0/41
LAN   0/16
LINUX-USER   0/19
LINUXHELP   0/1155
LINUX   0/22002
LINUX_BBS   0/957
mail   18.68
mail_fore_ok   249
MENSA   0/341
MODERATOR   0/102
MONTE   0/992
MOSCOW_OKLAHOMA   0/1245
MUFFIN   0/783
MUSIC   0/321
N203_STAT   894
N203_SYSCHAT   313
NET203   321
NET204   69
NET_DEV   0/10
NORD.ADMIN   0/101
NORD.CHAT   0/2572
NORD.FIDONET   189
NORD.HARDWARE   0/28
NORD.KULTUR   0/114
NORD.PROG   0/32
NORD.SOFTWARE   0/88
NORD.TEKNIK   0/58
NORD   0/453
OCCULT_CHAT   0/93
Möte OSDEBATE, 18996 texter
 lista första sista föregående nästa
Text 2622, 165 rader
Skriven 2005-02-19 21:37:14 av Rich (1:379/45)
Ärende: Re: ESB / XML / Unicode vs 8-bit characters ?
=====================================================
From: "Rich" <@>

This is a multi-part message in MIME format.

------=_NextPart_000_07A0_01C516CB.2E275930
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   You need to be more specific than "8-bit characters".  There are many =
8-bit character encodings.  If you are using Windows to generate your = data
you most likely are using Windows-1252 which is the default 8-bit = character
set for U.S. English in Windows.  Windows supports many 8-bit = encodings so
you could be using something else too.

   Unicode is a character set not an encoding.  There are multiple =
encodings the main ones being UTF-8, UTF-16, and UTF-32.  You can use = any of
these for XML as well as non-Unicode encodings.  For = interoperability you
should use Unicode preferably UTF-8.

   What comes out when the XML is parsed depends on the XML parser.  XML =
is logically expressed in Unicode.  The Windows XML parsers provide a = Unicode
interface.  Other parsers could do differently.

Rich


  "Ellen K." <72322.1016@compuserve.com> wrote in message =
news:4o2g11pu048kafbdilg46u77vs5ls0be55@4ax.com...
  Our new enterprise system is going to be built around an Enterprise
  Service Bus.  I don't have the full specs yet but as I understand it =
the
  main apps (starting with SalesForce) are going to be out on the =
internet
  and the Sonic ESB will be the messaging piece.  There will  be an
  Operational Data Store in house that will get updated every night on a
  batch basis from the main apps. =20

  My data warehouse will continue to be the data warehouse and will =
remain
  in house.  The dimensions will stay the same but I might have to =
create
  separate measures for the data from the new apps and then create views
  to keep everything transparent to the users.  =20

  I'm thinking if we're going to have an ODS in house already, I may as
  well do the ETL from there.   But I'm worrying that the new data will
  probably be unicode (because Java defaults to that and SalesForce is
  written in Java).  Right now I am storing everything (except our blobs
  of course) in 8-bit characters.  =20

  Anyone here who's up on this stuff, can the XML that goes back and =
forth
  convert between unicode and 8-bit characters, or am I gonna have to
  redefine all my data?   For example, if unicode data is put into an =
XML
  document that specifies UTF-8, what comes out when the document is
  parsed?  How about vice versa?  If this is too simplistic to work, =
what
  is needed?

  (We actually have no substantive need for unicode -- we are bilingual
  Spanish but all the special Spanish characters exist in the ascii
  character set.)
------=_NextPart_000_07A0_01C516CB.2E275930
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.3790.1289" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; You need to be more =
specific than=20
"8-bit characters".&nbsp; There are many 8-bit character = encodings.&nbsp; If
you=20
are using Windows to generate your data you most likely are using =
Windows-1252=20
which is the default 8-bit character set for U.S. English in =
Windows.&nbsp;=20
Windows supports many 8-bit encodings so you could be using something = else=20
too.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; Unicode is a character set =
not an=20
encoding.&nbsp; There are multiple encodings the main ones being UTF-8, =
UTF-16,=20
and UTF-32.&nbsp; You can use any of these for XML as well as = non-Unicode=20
encodings.&nbsp; For interoperability you should use Unicode preferably=20
UTF-8.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; What comes out when the =
XML is parsed=20
depends on the XML parser.&nbsp; XML is logically expressed in =
Unicode.&nbsp;=20
The Windows XML parsers provide a Unicode interface.&nbsp; Other parsers =
could=20
do differently.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Rich</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV>"Ellen K." &lt;<A=20
  =
href=3D"mailto:72322.1016@compuserve.com">72322.1016@compuserve.com</A>&g=
t;=20
  wrote in message <A=20
  =
href=3D"news:4o2g11pu048kafbdilg46u77vs5ls0be55@4ax.com">news:4o2g11pu048=
kafbdilg46u77vs5ls0be55@4ax.com</A>...</DIV>Our=20
  new enterprise system is going to be built around an =
Enterprise<BR>Service=20
  Bus.&nbsp; I don't have the full specs yet but as I understand it =
the<BR>main=20
  apps (starting with SalesForce) are going to be out on the =
internet<BR>and the=20
  Sonic ESB will be the messaging piece.&nbsp; There will&nbsp; be=20
  an<BR>Operational Data Store in house that will get updated every =
night on=20
  a<BR>batch basis from the main apps.&nbsp; <BR><BR>My data warehouse =
will=20
  continue to be the data warehouse and will remain<BR>in house.&nbsp; =
The=20
  dimensions will stay the same but I might have to create<BR>separate =
measures=20
  for the data from the new apps and then create views<BR>to keep =
everything=20
  transparent to the users.&nbsp;&nbsp; <BR><BR>I'm thinking if we're =
going to=20
  have an ODS in house already, I may as<BR>well do the ETL from=20
  there.&nbsp;&nbsp; But I'm worrying that the new data will<BR>probably =
be=20
  unicode (because Java defaults to that and SalesForce is<BR>written in =

  Java).&nbsp; Right now I am storing everything (except our blobs<BR>of =
course)=20
  in 8-bit characters.&nbsp;&nbsp; <BR><BR>Anyone here who's up on this =
stuff,=20
  can the XML that goes back and forth<BR>convert between unicode and =
8-bit=20
  characters, or am I gonna have to<BR>redefine all my data?&nbsp;&nbsp; =
For=20
  example, if unicode data is put into an XML<BR>document that specifies =
UTF-8,=20
  what comes out when the document is<BR>parsed?&nbsp; How about vice=20
  versa?&nbsp; If this is too simplistic to work, what<BR>is =
needed?<BR><BR>(We=20
  actually have no substantive need for unicode -- we are =
bilingual<BR>Spanish=20
  but all the special Spanish characters exist in the ascii<BR>character =

set.)</BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_07A0_01C516CB.2E275930--

--- BBBS/NT v4.01 Flag-5
 * Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)