Vitaly Lipatov l...@etersoft.ru wrote:
+LanguageNames=(RUS=0x19:winerr)
+CodePages=(FRA=65001:0)
'FRA'? This doesn't look correct.
--
Dmitry.
Dmitry Timoshkov dmi...@codeweavers.com wrote:
Vitaly Lipatov l...@etersoft.ru wrote:
+LanguageNames=(RUS=0x19:winerr)
+CodePages=(FRA=65001:0)
'FRA'? This doesn't look correct.
Also it doesn't make much sense to send a half completed translation.
--
Dmitry.
On 06/30/2010 03:43 PM, Dmitry Timoshkov wrote:
Dmitry Timoshkovdmi...@codeweavers.com wrote:
Vitaly Lipatovl...@etersoft.ru wrote:
+LanguageNames=(RUS=0x19:winerr)
+CodePages=(FRA=65001:0)
'FRA'? This doesn't look correct.
Also it doesn't make much sense to send a half completed
André Hentschel n...@dawncrow.de wrote:
This fixes bug 22862 which blocks bug 12804 (1.2)
We already do a similar recursion in DEFDLG_FindDefButton and
GetNextDlgGroupItem
I didnt found any other changes in the tests... i expected some more Test
succeeded inside todo block
You need to
Hi, wine-devel
I'm working on implementation of Windows Game Explorer interfaces
for Wine. The work is in advanced stage now, but I have problem with
implementation of conformance tests.
Thing I want to test is loading and parsing so-called Game Definition Files.
GDF are not separate files, but
Hi,
I happened to stumble across some code which didn't look quite right in
dlls/ntdll/serial.c. However, I have no expertise in serial comms or termios.
Also, I have no means to test the change I propose. On the other hand, the
change seems clearly right and conforms to what I learn from
I've been reading the Wine code and noticed that some of the external
interfaces are practically undocumented. I did a web search on some of
the names and found descriptions in MSDN.
I realize that copying the information from MSDN directly into the code
is a poor idea (like copyright
Hi Max,
1) Would including the URL of the MSDN article be useful/a good idea?
No. MSDN is in the habit of changing its URLs all too frequently.
A more general response: I'm not sure that a lot of documentation
patches will be accepted. MSDN has to be considered the definitive
resource for
Am 30.06.2010 19:25, schrieb Max TenEyck Woodbury:
I've been reading the Wine code and noticed that some of the external
interfaces are practically undocumented. I did a web search on some of
the names and found descriptions in MSDN.
I realize that copying the information from MSDN directly
В сообщении от Среда 30 июня 2010 Вы написали:
Dmitry Timoshkov dmi...@codeweavers.com wrote:
...
Also it doesn't make much sense to send a half completed translation.
You are welcome :)
I have no time for translate stupid, obsoleted, unexisted errors.
Later, as next step, I will do review
No. MSDN is in the habit of changing its URLs all too frequently.
For what it's worth, while MSDN seems to like changing its URLs a lot,
it does seem to be quite good at maintaining forwarders for the old URLs
- most API documentation URLs I've randomly found from 5 years ago still
work,
On Wed, Jun 30, 2010 at 11:44 AM, Juan Lang juan.l...@gmail.com wrote:
...
A more general response: I'm not sure that a lot of documentation
patches will be accepted. MSDN has to be considered the definitive
resource for the Windows API. It's often incorrect, of course, and
our regression
On Jun 30, 2010, at 11:47 AM, Ken Thomases wrote:
I happened to stumble across some code which didn't look quite right in
dlls/ntdll/serial.c. However, I have no expertise in serial comms or
termios. Also, I have no means to test the change I propose. On the other
hand, the change seems
Juan Lang:
grin Of course one of the reasons to add documentation is precisely
because the information on MSDN is less than perfect. Having a good
interface definition makes things easier. I'm still in the process of
learning how to submit patches. These would be low risk but useful
changes so
Erich Hoover ehoo...@mines.edu writes:
Personally, I think that it would be really good to do a better job of
documenting the API functions (particularly edge cases). I'm
currently very busy with work, but if Alexandre is ok with
documentation-only patches then this is something I'm tempted
On Wed, Jun 30, 2010 at 12:44 PM, Alexandre Julliard
julli...@winehq.org wrote:
Erich Hoover ehoo...@mines.edu writes:
Personally, I think that it would be really good to do a better job of
documenting the API functions (particularly edge cases). I'm
currently very busy with work, but if
Erich Hoover ehoo...@mines.edu writes:
Alright, well then I won't do it. Is the existing documentation going
to be stripped at some point? It seems to me like we would benefit
from more-detailed function descriptions in the auto-generated API
documentation. I think it would save a lot of
On 06/30/2010 03:13 PM, Alexandre Julliard wrote:
Erich Hooverehoo...@mines.edu writes:
Alright, well then I won't do it. Is the existing documentation going
to be stripped at some point? It seems to me like we would benefit
from more-detailed function descriptions in the auto-generated API
Alexandre Julliard julli...@winehq.org wrote:
Erich Hoover ehoo...@mines.edu writes:
Alright, well then I won't do it. Is the existing documentation going
to be stripped at some point? It seems to me like we would benefit
from more-detailed function descriptions in the auto-generated API
On Wed, Jun 30, 2010 at 1:36 PM, James Mckenzie
jjmckenzi...@earthlink.net wrote:
...
How about some place on the Wiki along with an implementation status. That
way we can also annotate items that are missing in MSDN (I just re-stumbled
across something in my latest Richedit tests) as well.
Erich Hoover ehoo...@mines.edu wrote:
Sent: Jun 30, 2010 12:43 PM
To: James Mckenzie jjmckenzi...@earthlink.net
Cc: Alexandre Julliard julli...@winehq.org, Max TenEyck Woodbury
m...@mtew.isa-geek.net, wine-devel@winehq.org
Subject: Re: (Resent) Documentation - Reference to MSDN?
On Wed, Jun 30,
On 7/1/2010 02:20, Scott Ritchie wrote:
Translation by Sven Augustin
@@ -20,7 +21,12 @@ Name[sr]=Wine - аДаИаЗаАб� Windows аПб�аОаГб�аАаМаА
name...@latin]=wine - diza� Windows programa
Name[hr]=Wine - diza� Windows programa
Exec=wine start /unix %f
+ HEAD
On 06/30/2010 03:46 PM, Nikolay Sivov wrote:
On 7/1/2010 02:20, Scott Ritchie wrote:
Translation by Sven Augustin
@@ -20,7 +21,12 @@ Name[sr]=Wine - аДаИаЗаАб� Windows аПб�аОаГб�аАаМаА
name...@latin]=wine - diza� Windows programa
Name[hr]=Wine - diza� Windows programa
Exec=wine
I've been reading the Wine code and noticed that some of the external
interfaces are practically undocumented. I did a web search on some of
the names and found descriptions in MSDN.
I realize that copying the information from MSDN directly into the code
is a poor idea (like copyright
On 06/30/2010 03:43 PM, Erich Hoover wrote:
On Wed, Jun 30, 2010 at 1:36 PM, James Mckenzie
jjmckenzi...@earthlink.net wrote:
...
How about some place on the Wiki along with an implementation status. That way
we can also annotate items that are missing in MSDN (I just re-stumbled across
Max TenEyck Woodbury m...@mtew.isa-geek.net wrote:
I created the top page as a table and populated it with all the
directory entries in the 'dll' directory. Somebody immediately deleted
it. WTF?
Creating a MSDN clone does not belong to the Wine project.
--
Dmitry.
26 matches
Mail list logo
