Re: [ros-diffs] [fireball] 20041: Fix for bug #932 (should go into 0.2.9 also)

[Thomas Weidenmueller]

fireball(a)svn.reactos.com wrote:
>   +		if (Pdo)
>  +			IoInvalidateDeviceRelations(Pdo, BusRelations);
>  +		else
>  +			DPRINT1("Pdo == NULL, not sending IoInvalidateDeviceRelations()!"); 
This is going to be a problem if DPRINT1 isn't expanded. You should
create a {...} block for the else branch.

- Thomas

[Thomas Weidenmueller]

Thomas Weidenmueller wrote:
>   This is going to be a problem if DPRINT1 isn't
> expanded. You should
>  create a {...} block for the else branch. 
Never mind, there's a semicolon after DPRINT(...)... ;)

- Thomas

[Raigedas]

Is there a need to translate ros (or parts of it) to other languages now? maybe it 
would be reasonable to start translating it in later versions (when ros will be more 
stable and usable) only? especialy to other than major languages... 

i could help translating ros to my native language - lithuanian (lithuania) if there is 
a need.

Raigedas

[TwoTailedFox]

Translations are always appreciated for ReactOS. Even for Languages
like Lithuanian, Estonia, and Klingon.

On 12/10/05, Raigedas <raigedas(a)dmprojects.com> wrote:
>   Is there a need to translate ros (or parts of it) to
> other languages now? maybe it
>  would be reasonable to start translating it in later versions (when ros will be more
>  stable and usable) only? especialy to other than major languages...
>
>  i could help translating ros to my native language - lithuanian (lithuania) if there is
>  a need.
>
>  Raigedas
>
>
>
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>  

--
"I had a handle on life, but then it broke"

[Raigedas]

I guest you did not read my message carefully:) Let me explain... Yes, I 
understand that it is always good to have as many translations as 
possible. But maybe it is inefficient to make translations at this state 
of ROS:

*** there are going to be a lot of changes to the code and this will/may
affect _all_ the translations also.

*** only one translation (or very few) may be required in the developing 
process and/or for testing.

*** there is no point to make corrections to translations all along the way, 
because ROS can not be used in productional environment in this state 
anyway.

i will be glad to create (or to help creating) a translation to my native 
language, but maybe it is not time for it yet. What do others think?

Raigedas

Hi TwoTailedFox on 2005.12.10, 23:26:19 +0200 you wrote:

>  Translations are always appreciated for ReactOS. Even
> for Languages
> like Lithuanian, Estonia, and Klingon.
>
> On 12/10/05, Raigedas <raigedas(a)dmprojects.com> wrote:
> >Is there a need to translate ros (or parts of it) to other languages
> >now? maybe it would be reasonable to start translating it in later
> >versions (when ros will be morestable and usable) only? especialy to
> >other than major languages...
> >
> >i could help translating ros to my native language - lithuanian
> >(lithuania) if there is a need.
> >
> >Raigedas
> >

[nitro2k01]

I have in fact not looked at the source, but isn't it so that test
resources are stored separated from code? If so, language resources
will just "hang in there".

                                           /nitro2k01

On 12/12/05, Raigedas <raigedas(a)dmprojects.com> wrote:
>   I guest you did not read my message carefully:) Let me
> explain... Yes, I
>  understand that it is always good to have as many translations as
>  possible. But maybe it is inefficient to make translations at this state
>  of ROS:
>
>  *** there are going to be a lot of changes to the code and this will/may
>  affect _all_ the translations also.
>
>  *** only one translation (or very few) may be required in the developing
>  process and/or for testing.
>
>  *** there is no point to make corrections to translations all along the way,
>  because ROS can not be used in productional environment in this state
>  anyway.
>
>  i will be glad to create (or to help creating) a translation to my native
>  language, but maybe it is not time for it yet. What do others think?
>
>  Raigedas
>
>  Hi TwoTailedFox on 2005.12.10, 23:26:19 +0200 you wrote:
>
> >  Translations are always appreciated for ReactOS.
> > Even for Languages
> > like Lithuanian, Estonia, and Klingon.
> >
> > On 12/10/05, Raigedas <raigedas(a)dmprojects.com> wrote:
> > >Is there a need to translate ros (or parts of it) to other languages
> > >now? maybe it would be reasonable to start translating it in later
> > >versions (when ros will be morestable and usable) only? especialy to
> > >other than major languages...
> > >
> > >i could help translating ros to my native language - lithuanian
> > >(lithuania) if there is a need.
> > >
> > >Raigedas
> > > 
>
>
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>  

--
The blog  of nitro2k01: <http://soundandcomplete.blogspot.com/>
Saliga äro de som kan stava till 2k01!

[TwoTailedFox]

Language Resources are contained in seperate files, organised by country code.

On 12/12/05, nitro2k01 <nitro2k01(a)gmail.com> wrote:
>   I have in fact not looked at the source, but isn't
> it so that test
>  resources are stored separated from code? If so, language resources
>  will just "hang in there".
>
>                                             /nitro2k01
>
>  On 12/12/05, Raigedas <raigedas(a)dmprojects.com> wrote:
> >   I guest you did not read my message carefully:)
> > Let me explain... Yes, I
> >  understand that it is always good to have as many translations as
> >  possible. But maybe it is inefficient to make translations at this state
> >  of ROS:
> >
> >  *** there are going to be a lot of changes to the code and this will/may
> >  affect _all_ the translations also.
> >
> >  *** only one translation (or very few) may be required in the developing
> >  process and/or for testing.
> >
> >  *** there is no point to make corrections to translations all along the way,
> >  because ROS can not be used in productional environment in this state
> >  anyway.
> >
> >  i will be glad to create (or to help creating) a translation to my native
> >  language, but maybe it is not time for it yet. What do others think?
> >
> >  Raigedas
> >
> >  Hi TwoTailedFox on 2005.12.10, 23:26:19 +0200 you wrote:
> >
> > >  Translations are always appreciated for ReactOS.
> > > Even for Languages
> > > like Lithuanian, Estonia, and Klingon.
> > >
> > > On 12/10/05, Raigedas <raigedas(a)dmprojects.com> wrote:
> > > >Is there a need to translate ros (or parts of it) to other languages
> > > >now? maybe it would be reasonable to start translating it in later
> > > >versions (when ros will be morestable and usable) only? especialy to
> > > >other than major languages...
> > > >
> > > >i could help translating ros to my native language - lithuanian
> > > >(lithuania) if there is a need.
> > > >
> > > >Raigedas
> > > > 
> >
> >
> >
> >  _______________________________________________
> >  Ros-dev mailing list
> >  Ros-dev(a)reactos.org
> >  http://www.reactos.org/mailman/listinfo/ros-dev
> >  
>
>  --
>  The blog  of nitro2k01: <http://soundandcomplete.blogspot.com/>
>  Saliga äro de som kan stava till 2k01!
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>  

--
"I had a handle on life, but then it broke"

[David Hinz]

I think you're right, but there are some translations, which should be 
available, just to show it is possible.
In my opinion there should be a german, a french and a japanese 
translation, but the japanese translation rather because of the 
technical problems, which could appear (different fonts and so on...) as 
because of the importance of the language itself, whereas the german and 
french translations would be important because of the importance of 
these two languages.

But at this point I think, we shouldn't try to have a translation for 
every single language some grandmas in the last corner of earth speak, 
we have to many changes that would require modified translations at the 
moment, and that's to much work for two old grannies, isn't it?
But if somebody really wants to create a translation, we shouldn't 
hinder him from it, it's just in my opinion there are more important 
tasks to do, if you can do something else than translating.

Greets,

David Hinz

Raigedas schrieb:
>   I guest you did not read my message carefully:) Let me
> explain... Yes, I 
>  understand that it is always good to have as many translations as 
>  possible. But maybe it is inefficient to make translations at this state 
>  of ROS:
>  
>  *** there are going to be a lot of changes to the code and this will/may
>  affect _all_ the translations also.
>  
>  *** only one translation (or very few) may be required in the developing 
>  process and/or for testing.
>  
>  *** there is no point to make corrections to translations all along the way, 
>  because ROS can not be used in productional environment in this state 
>  anyway.
>  
>  i will be glad to create (or to help creating) a translation to my native 
>  language, but maybe it is not time for it yet. What do others think?
>  
>  Raigedas
>  
>  Hi TwoTailedFox on 2005.12.10, 23:26:19 +0200 you wrote:
>  
> > Translations are always appreciated for ReactOS. Even for Languages
> > like Lithuanian, Estonia, and Klingon.

[David Johnson]

IMHO, German, French, Japanese maybe Chinese are the most important for now.

Dave Johnson
San Diego, ReactOS Users Group

On 12/12/05, David Hinz <post.center(a)gmail.com> wrote:
>  
>  I think you're right, but there are some translations, which should be
>  available, just to show it is possible.
>  In my opinion there should be a german, a french and a japanese
>  translation, but the japanese translation rather because of the
>  technical problems, which could appear (different fonts and so on...) as
>  because of the importance of the language itself, whereas the german and
>  french translations would be important because of the importance of
>  these two languages.
>
>  But at this point I think, we shouldn't try to have a translation for
>  every single language some grandmas in the last corner of earth speak,
>  we have to many changes that would require modified translations at the
>  moment, and that's to much work for two old grannies, isn't it?
>  But if somebody really wants to create a translation, we shouldn't
>  hinder him from it, it's just in my opinion there are more important
>  tasks to do, if you can do something else than translating.
>
>  Greets,
>
>  David Hinz
>
>  Raigedas schrieb:
> >   I guest you did not read my message carefully:)
> > Let me explain... Yes, I
> >  understand that it is always good to have as many translations as
> >  possible. But maybe it is inefficient to make translations at this state
> >  of ROS:
> >
> >  *** there are going to be a lot of changes to the code and this will/may
> >  affect _all_ the translations also.
> >
> >  *** only one translation (or very few) may be required in the developing
> >  process and/or for testing.
> >
> >  *** there is no point to make corrections to translations all along the 
>  way,
> >   because ROS can not be used in productional
> > environment in this state
> >  anyway.
> >
> >  i will be glad to create (or to help creating) a translation to my 
>  native
> >   language, but maybe it is not time for it yet.
> > What do others think?
> >
> >  Raigedas
> >
> >  Hi TwoTailedFox on 2005.12.10, 23:26:19 +0200 you wrote:
> >
> > > Translations are always appreciated for ReactOS. Even for Languages
> > > like Lithuanian, Estonia, and Klingon. 
> _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>  


--
David Johnson
http://www.davefilms.us
DaveFilms Digital Media - Audio [TM]
Producer

[Royce Mitchell III]

David Hinz wrote:

>   But at this point I think, we shouldn't try to
> have a translation for 
>  every single language some grandmas in the last corner of earth speak, 
>  we have to many changes that would require modified translations at 
>  the moment, and that's to much work for two old grannies, isn't it?
>  But if somebody really wants to create a translation, we shouldn't 
>  hinder him from it, it's just in my opinion there are more important 
>  tasks to do, if you can do something else than translating. 
OTOH, as networking stabilizes, there is the distinct possibility that 
ReactOS could be useful enough for special-purpose applications. Say a 
company in one of the poorer nations wants to put together some 
workstations to run a small number of applications. We're possibly not 
far off from being able to serve in this sort of role.

[David Hinz]

But that's at least 9 months away, consider the latest explorer bugs 
1106/1107 and 1118 (hope I'm not wrong with the numbers) and I believe, 
the interface will stabilize in 6 months or so, before that time it 
doesn't make _much_ sense to work on a translation. If you want to 
translate something here and something there, I don't see a problem, but 
a (nearly) complete translation would be nonsense at the moment.

Greets,

David Hinz

Royce Mitchell III schrieb:
>   David Hinz wrote:
>  
> >   But at this point I think, we shouldn't try
> > to have a translation for 
> >  every single language some grandmas in the last corner of earth speak, 
> >  we have to many changes that would require modified translations at 
> >  the moment, and that's to much work for two old grannies, isn't it?
> >  But if somebody really wants to create a translation, we shouldn't 
> >  hinder him from it, it's just in my opinion there are more important 
> >  tasks to do, if you can do something else than translating. 
>  
>  OTOH, as networking stabilizes, there is the distinct possibility that 
>  ReactOS could be useful enough for special-purpose applications. Say a 
>  company in one of the poorer nations wants to put together some 
>  workstations to run a small number of applications. We're possibly not 
>  far off from being able to serve in this sort of role.
>  
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>