From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII X-Google-Thread: 103376,1c4b8fdfa762b2bb X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-04-05 13:22:10 PST Path: supernews.google.com!sn-xit-03!supernews.com!logbridge.uoregon.edu!feed2.news.rcn.net!rcn!cpk-news-hub1.bbnplanet.com!denver-snf1.gtei.net!news.gtei.net!coop.net!newsfeed1.global.lmco.com!svlnews.lmms.lmco.com!not-for-mail From: Paul Storm Newsgroups: comp.lang.ada Subject: Re: Hebrew language character set Date: Thu, 05 Apr 2001 10:41:58 -0800 Organization: rse Message-ID: <3ACCAE66.712E09B6@lmco.com> References: <3ACA11B0.9AAFDDDD@lmco.com> <3ACB85DF.9E6DBD03@lmco.com> <3ACC6E83.5B860AC5@free.fr> <3ACC9597.14D3B23D@lmco.com> <87lmpfz4by.fsf@deneb.enyo.de> NNTP-Posting-Host: 129.197.210.20 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en Xref: supernews.google.com comp.lang.ada:6526 Date: 2001-04-05T10:41:58-08:00 List-Id: I modified my program as follows, [begin code] with Ada.Characters.Handling; use Ada.Characters.Handling; with Ada.Wide_Text_IO; use Ada.Wide_Text_IO; procedure aleph is begin Ada.Wide_Text_IO.Put (Item => Wide_Character'Val(16#0590#)); end aleph; [end code] Now I get the following results, D:\TEMP>gnatmake -gnatW8 aleph.adb gcc -c -gnatW8 aleph.adb gnatbind -x aleph.ali gnatlink aleph.ali D:\TEMP>aleph.exe +� I made some mistake in coding my character in decimal instead of hex?? I found this in the GNAT User's Guide, btw, -gnatWe Specify the method of encoding for wide characters. e is one of the following: h Hex encoding (brackets coding also recognized) u Upper half encoding (brackets encoding also recognized) s Shift/JIS encoding (brackets encoding also recognized) e EUC encoding (brackets encoding also recognized) 8 UTF-8 encoding (brackets encoding also recognized) b Brackets encoding only (default value) For full details on the these encoding methods see See section Wide Character Encodings. Note that brackets coding is always accepted, even if one of the other options is specified, so for example -gnatW8 specifies that both brackets and UTF-8 encodings will be recognized. The units that are with'ed directly or indirectly will be scanned using the specified representation scheme, and so if one of the non-brackets scheme is used, it must be used consistently throughout the program. However, since brackets encoding is always recognized, it may be conveniently used in standard libraries, allowing these libraries to be used with any of the available coding schemes. scheme. If no -gnatW? parameter is present, then the default representation is Brackets encoding only. Note that the wide character representation that is specified (explicitly or by default) for the main program also acts as the default encoding used for Wide_Text_IO files if not specifically overridden by a WCEM form parameter. Paul Storm