Why is it needed to expand the unicode characters to hex?
________________________________
Modified: trunk/reactos/bootdata/hivesys.inf --- trunk/reactos/bootdata/hivesys.inf 2005-03-01 22:22:56 UTC (rev 13791) +++ trunk/reactos/bootdata/hivesys.inf 2005-03-01 22:56:51 UTC (rev 13792) @@ -257,10 +257,10 @@ ; Subsystems HKLM,"SYSTEM\CurrentControlSet\Control\Session Manager\Subsystems","Debug",0x00020000,"" HKLM,"SYSTEM\CurrentControlSet\Control\Session Manager\Subsystems","Kmode",0x00020000,"%SystemRoot%\system32\win32k.sys" -HKLM,"SYSTEM\CurrentControlSet\Control\Session Manager\Subsystems","Optional",0x00070000,"Posix Os2" +HKLM,"SYSTEM\CurrentControlSet\Control\Session Manager\Subsystems","Optional",0x00070001,50,00,6f,00,73,00,69,00,78,00,00,00,4f,00,73,00,32,00,00,00,00,00 HKLM,"SYSTEM\CurrentControlSet\Control\Session Manager\Subsystems","Os2",0x00020000,"%SystemRoot%\system32\os2ss.exe" HKLM,"SYSTEM\CurrentControlSet\Control\Session Manager\Subsystems","Posix",0x00020000,"%SystemRoot%\system32\psxss.exe" -HKLM,"SYSTEM\CurrentControlSet\Control\Session Manager\Subsystems","Required",0x00070000,"Debug Windows" +HKLM,"SYSTEM\CurrentControlSet\Control\Session Manager\Subsystems","Required",0x00070001,44,00,65,00,62,00,75,00,67,00,00,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,00,00,00,00 HKLM,"SYSTEM\CurrentControlSet\Control\Session Manager\Subsystems","Windows",0x00020000,"%SystemRoot%\system32\csrss.exe" ; 3Com 3c905 Driver
The unicode utf-7 is 16bits no more or less example letter (do not take the asc2 code exacly I always mix the big and small letter asc code) 65 (letter A) in hex 0x41 the utf-7 unicode utf-7 look like this then 0041 for letter A if the was utf-8 it hav been only hex 0x41 for letter A UTF-8 does have 8 to 32bits range
Windows are using utf-7 that why I think the regsiter are being writen in utf-7 hex
----- Original Message ----- From: "Casper Hornstrup" ch@csh-consult.dk To: ros-dev@reactos.com Sent: Wednesday, March 02, 2005 12:46 PM Subject: [ros-dev] RE: [ros-diffs] [ea] 13792: Fix SM\Subsystems\RequiredandSM\Subsystems\Optional.
Why is it needed to expand the unicode characters to hex?
Modified: trunk/reactos/bootdata/hivesys.inf --- trunk/reactos/bootdata/hivesys.inf 2005-03-01 22:22:56 UTC (rev 13791) +++ trunk/reactos/bootdata/hivesys.inf 2005-03-01 22:56:51 UTC (rev 13792) @@ -257,10 +257,10 @@
; Subsystems HKLM,"SYSTEM\CurrentControlSet\Control\Session
Manager\Subsystems","Debug",0x00020000,""
HKLM,"SYSTEM\CurrentControlSet\Control\Session
Manager\Subsystems","Kmode",0x00020000,"%SystemRoot%\system32\win32k.sys"
-HKLM,"SYSTEM\CurrentControlSet\Control\Session
Manager\Subsystems","Optional",0x00070000,"Posix Os2"
+HKLM,"SYSTEM\CurrentControlSet\Control\Session
Manager\Subsystems","Optional",0x00070001,50,00,6f,00,73,00,69,00,78,00,00,0 0,4f,00,73,00,32,00,00,00,00,00
HKLM,"SYSTEM\CurrentControlSet\Control\Session
Manager\Subsystems","Os2",0x00020000,"%SystemRoot%\system32\os2ss.exe"
HKLM,"SYSTEM\CurrentControlSet\Control\Session
Manager\Subsystems","Posix",0x00020000,"%SystemRoot%\system32\psxss.exe"
-HKLM,"SYSTEM\CurrentControlSet\Control\Session
Manager\Subsystems","Required",0x00070000,"Debug Windows"
+HKLM,"SYSTEM\CurrentControlSet\Control\Session
Manager\Subsystems","Required",0x00070001,44,00,65,00,62,00,75,00,67,00,00,0 0,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,00,00,00,00
HKLM,"SYSTEM\CurrentControlSet\Control\Session
Manager\Subsystems","Windows",0x00020000,"%SystemRoot%\system32\csrss.exe"
; 3Com 3c905 Driver
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Magnus Olsen wrote:
The unicode utf-7 is 16bits no more or less example letter (do not take the asc2 code exacly I always mix the big and small letter asc code) 65 (letter A) in hex 0x41 the utf-7 unicode utf-7 look like this then 0041 for letter A if the was utf-8 it hav been only hex 0x41 for letter A UTF-8 does have 8 to 32bits range
Windows are using utf-7 that why I think the regsiter are being writen in utf-7 hex
As far as I know UTF-7 is very similar to UTF-8, using only 7 bits per byte instead of 8, or something similar, it's meant for compatibility with systems that don't like use of the full 8 bits. UTF-16 is a 16bit encoding. I don't know whether Windows NT's wide characters are meant to be UTF-16 or UCS-2 (also 16bit, but without the ability to encode characters that need more than 16bits to encode), but my guess it uses one of those.
Hi
Both UTF-7 and UTF-16 are 16bits UTF-16 encoding are bit diffrent ageinst UTF-7.some link and info about utf-7http://www.faqs.org/rfcs/rfc2152.html
UTF-7 Definition
A UTF-7 stream represents 16-bit Unicode characters using 7-bit US- ASCII octets as follows:
Rule 1: (direct encoding) Unicode characters in set D above may be encoded directly as their ASCII equivalents. Unicode characters in Set O may optionally be encoded directly as their ASCII equivalents, bearing in mind that many of these characters are illegal in header fields, or may not pass correctly through some mail gateways.
andhttp://en.wikipedia.org/wiki/UTF-7----- Original Message ----- From: "Jasper van de Gronde" th.v.d.gronde@hccnet.nl To: "ReactOS Development List" ros-dev@reactos.com Sent: Wednesday, March 02, 2005 2:49 PM Subject: Re: [ros-dev] RE: [ros-diffs] [ea] 13792:Fix SM\Subsystems\RequiredandSM\Subsystems\Optional.
Magnus Olsen wrote:
The unicode utf-7 is 16bits no more or less example letter (do not take the asc2 code exacly I always mix the big
and
small letter asc code) 65 (letter A) in hex 0x41 the utf-7 unicode utf-7 look like this then
0041
for letter A if the was utf-8 it hav been only hex 0x41 for letter A UTF-8 does have
8 to
32bits range
Windows are using utf-7 that why I think the regsiter are being writen
in
utf-7 hex
As far as I know UTF-7 is very similar to UTF-8, using only 7 bits per byte instead of 8, or something similar, it's meant for compatibility with systems that don't like use of the full 8 bits. UTF-16 is a 16bit encoding. I don't know whether Windows NT's wide characters are meant to be UTF-16 or UCS-2 (also 16bit, but without the ability to encode characters that need more than 16bits to encode), but my guess it uses one of those.
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Magnus Olsen wrote:
Both UTF-7 and UTF-16 are 16bits UTF-16 encoding are bit diffrent ageinst UTF-7.some link and info about utf-7http://www.faqs.org/rfcs/rfc2152.html
Now I understand what you mean! This a "different" 16bits than the one I was referring to. I meant UTF-16 uses 16bit code units, while UTF-7 uses 8bit code units (of which it only uses 7bits per code unit for compatibility purposes). The 16 bits you are referring to are for the code points in Unicode 2.0. UTF-16 can be used to encode all code points in Unicode 4.0 (which require more than 16 bits) though (by being a variable-width encoding).
Command Output From Shlwapi most recent SVN
url.c: In function `UrlHashA': url.c:1398: warning: passing arg 1 of `HashData' discards qualifiers fro r target type url.c: In function `UrlHashW': url.c:1420: warning: passing arg 1 of `HashData' discards qualifiers fro r target type [CC] wsprintf.c [STUBS] shlwapi.spec [CC] shlwapi.stubs.c [AR] shlwapi.a [LD] shlwapi.nostrip.dll temp.exp(.edata+0x94):fake: undefined reference to `f1' temp.exp(.edata+0x98):fake: undefined reference to `f2' temp.exp(.edata+0x9c):fake: undefined reference to `f3' temp.exp(.edata+0xa0):fake: undefined reference to `f4' make[1]: *** [shlwapi.nostrip.dll] Error 1 make: *** [shlwapi] Error 2
This Error are comming up again again and again using GNU dlltool 2.13.90 20030111
Tried using dlltool 2.14.90 and also tried using dlltool 2.15.91-20040904
Anybody knows what im doing wrong
What i have allready done is uninstalled mingw completely and installing the two files from your webpage that dident work then tried to use different binutils same error as above more or less some time it allso likes to display f5,f6,f7
Thomas
__________________________________ Celebrate Yahoo!'s 10th Birthday! Yahoo! Netrospective: 100 Moments of the Web http://birthday.yahoo.com/netrospective/