David Hinz wrote:
> Somewhere in reactos/lib/cabinet I found sourcecode calling functions
> like err, and the strings it gave to these functions looked like
> something output to the user e.g. errormessages like file * couldn't
> be found or something like this, so I wondered, if this should be
> translatable.
> As I don't know what kind of stings should be translatable, I
> just asked.
You need to understand the context in which the message is used. If it's
system debug message, it will normally be hardcoded in. If it's a generic
Win32 error message it should be picked up with FormatMessage. These will be
output in the users preferred language via the LANG_SYSTEM_DEFAULT or
LANG_USER_DEFAULT flags. Then you have simple MessageBox outputs which can
be picked out of a resource file, but are generally hardcoded in. There are
many other situations and usages, but I'll stop there.
As already said, becoming a programmer is the only real way of understanding
it all.
> Well, you say I should learn some things like structures of resource
> files, do you have any links for me?
There are thousands of C tutorials on the net. Here are a few:
Tutorials : http://www.cprogramming.com/tutorial.html
Forgers win32 : http://www.winprog.org/tutorial/
Everyone has their favourite books, but these are probably the most popular
for learning C and Windows programming:
K & R :
http://www.amazon.com/gp/product/0131103628/qid=1135081344/sr=2-1/ref=pd_bbs
_b_2_1/104-6581600-7986334?s=books&v=glance&n=283155
C Primer Plus :
http://www.amazon.com/gp/product/0672326965/qid=1135081234/sr=1-1/ref=sr_1_1
/104-6581600-7986334?s=books&v=glance&n=283155
Petzold :
http://www.amazon.com/gp/product/157231995X/qid=1135081418/sr=1-1/ref=sr_1_1
/104-6581600-7986334?s=books&v=glance&n=283155
Have fun,
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
We're coming close to the 0.2.9 release now, we need to get the changes into
the wiki sooner rather than later :)
http://www.reactos.org/wiki/index.php/ChangeLog-0.2.9
<http://www.reactos.org/wiki/index.php/ChangeLog-0.2.9>
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
As GreatLord said, you will need programming knowledge to do this.
If you want to start making progress with this, you could start by getting a
sound understanding of C and basic Windows programming, including resource
file syntax. Then work from there.
You will generally find though that most stuff that should be in a resource
file, already is.
What have you found to make you think otherwise?
-----Original Message-----
From: David Hinz [mailto:post.center@gmail.com]
Sent: 20 December 2005 07:08
To: ReactOS Development List
Subject: Re: [ros-dev] Hardcoded strings
Sure, but the problem is, I don't really know which strings this are,
and how I can find them.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Hey all,
at the moment I try to create an overview on the current German
translation of ReactOS and for this I need to know one important little
thing:
Which hardcoded strings should be moved to rc-files?
And is there a howto on this topic?
I would be very happy about some fast responses, I want to get the
German translation ready before the 0.3.0 release...
Greets,
David Hinz
And yes, I know I should post this to the ros-translate list, but it
seems to be inactive...
Hi,
I was testing with drivers.exe from the W2K DDK. It worked once before about
a month ago. Now it crashes the system w/o any display at all. WinObj.exe works
fine.
Revision: 19187
Node Kind: directory
Schedule: normal
Last Changed Author: hbirr
Last Changed Rev: 19187
Last Changed Date: 2005-11-12 23:45:32 +0000 (Sat, 12 Nov 2005)
Properties Last Updated: 2005-10-01 16:19:41 +0000 (Sat, 01 Oct 2005)
(subsys/win32k/objects/gdiobj.c:585) Attempted to free global gdi handle 0x13080
1fb, caller needs to get ownership first!!!
lib/rtl/unicode.c:916: Pagable code called at IRQL > APC_LEVEL (2)
KeBugCheck at ntoskrnl/rtl/libsupp.c:139
(ntoskrnl/mm/mm.c:275) Page fault at high IRQL was 2, address c5b62
A problem has been detected and ReactOS has been shut down to prevent damage to
your computer.
Technical information:
*** STOP: 0x00000000 (0x00000000,0x00000000,0x00000000,0x00000000)
Frames:
<ntoskrnl.exe:2585 (ntoskrnl/ke/bug.c:479 (KeBugCheckEx))>
<ntoskrnl.exe:25bd (ntoskrnl/ke/bug.c:500 (KeBugCheck))>
<ntoskrnl.exe:8d20d (ntoskrnl/rtl/libsupp.c:139 (CHECK_PAGED_CODE_RTL))>
<ntoskrnl.exe:b9bda (lib/rtl/unicode.c:918 (RtlUnicodeStringToAnsiString))>
<ntoskrnl.exe:554cd (ntoskrnl/ldr/loader.c:435 (LdrpQueryModuleInformation))>
<ntoskrnl.exe:27f6a (ntoskrnl/ex/sysinfo.c:803 (QSISystemModuleInformation))>
<ntoskrnl.exe:28e5d (ntoskrnl/ex/sysinfo.c:1558 (NtQuerySystemInformation))>
<ntoskrnl.exe:9c57c ({standard input}:373 (KiSystemService))>
<drivers.EXE:146f>
Entered debugger on embedded INT3 at 0x0008:0x800b2376.
kdb:> bt
Eip:
<ntoskrnl.exe:b2377 ({standard input}:28 (DbgBreakPointWithStatus))>
Frames:
<ntoskrnl.exe:2585 (ntoskrnl/ke/bug.c:479 (KeBugCheckEx))>
<ntoskrnl.exe:25bd (ntoskrnl/ke/bug.c:500 (KeBugCheck))>
<ntoskrnl.exe:8d20d (ntoskrnl/rtl/libsupp.c:139 (CHECK_PAGED_CODE_RTL))>
<ntoskrnl.exe:b9bda (lib/rtl/unicode.c:918 (RtlUnicodeStringToAnsiString))>
<ntoskrnl.exe:554cd (ntoskrnl/ldr/loader.c:435 (LdrpQueryModuleInformation))>
<ntoskrnl.exe:27f6a (ntoskrnl/ex/sysinfo.c:803 (QSISystemModuleInformation))>
<ntoskrnl.exe:28e5d (ntoskrnl/ex/sysinfo.c:1558 (NtQuerySystemInformation))>
<ntoskrnl.exe:9c57c ({standard input}:373 (KiSystemService))>
<drivers.EXE:146f>
<drivers.EXE:170f>
<kernel32.dll:31635 (lib/kernel32/process/create.c:68 (BaseProcessStartup))>
<00000000>
kdb:>
Ge van Geldorp wrote:
> Reminder to devs: with the release of 0.2.9-RC2 we're now in
> code freeze for
> the branch. During code freeze, the only allowed commits are
> bugfixes to
> release-blocking bugs. These fixes are generally discussed on
> the mailing
> list prior to committing a fix.
>
> GvG
I'm not sure if I'm missing something here, but these rules seem to
contradict themselves.
According to the rules :
We don't move from Feature Freeze to Code Freeze until, and I quote "the
testing coordinator indicates that all blocker bugs in the release branch
have been fixed"
I interpret this as, we move to Code Freeze, when and only when all blockers
have been fixed.
We then dictate that "During code freeze, the only allowed commits are
bugfixes to release-blocking bugs"
If all blockers must be fixed before we move to Code Freeze, and we can only
commit bug fixes to free up blockers during Feature Freeze, what is the
actual point in having a Code Freeze as we will never have any blockers to
fix.
I hope that reads ok.
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
