2010/7/2 Francois Gouget :
> As expected Wallon and Finnish are truncated:
> http://fgouget.free.fr/tmp/reshack/comdlg32_Wa.jpg
> http://fgouget.free.fr/tmp/reshack/comdlg32_Fi.jpg
I wonder how we will handle these cases once we switch to using PO files.
A more generic approach will surely be need
Dmitry wrote:
> > These were picked at random. Isn't it strange how all these
> > translated controls have the same size as the English version
> > despite widely different text content?
>
> There is nothing strange there, if the text still fits and doesn't get
> clipped out.
Let's check it out
Francois Gouget wrote:
[skipped]
> These were picked at random. Isn't it strange how all these translated
> controls have the same size as the English version despite widely
> different text content?
There is nothing strange there, if the text still fits and doesn't get
clipped out.
> So in
On Fri, 25 Jun 2010, Dmitry Timoshkov wrote:
> Francois Gouget wrote:
>
> > Requiring that translators master both skills severly limits the pool of
> > translators we can draw from.
>
> Doesn't this sound similar to so called limitation that exists for people
> willing to work on Wine code, b
Michael Stefaniuc wrote:
> > How is that different from transalting an .rc file and generating a patch
> > from
> > the resulting translation?
> For Alexandre there is no difference; he gets a patch on wine-patches
> and does his emacs magic on it. But we do not care about Alexandre here ;)
>
>
Dmitry Timoshkov wrote:
> Michael Stefaniuc wrote:
>
>> What we see is that there are several people who want to help us with
>> the translation part but have no idea how to code (or are actually
>> willing to code). We could use them, especially for the more exotic (or
>> let's c
Michael Stefaniuc wrote:
> What we see is that there are several people who want to help us with
> the translation part but have no idea how to code (or are actually
> willing to code). We could use them, especially for the more exotic (or
> let's call it less mainstream) lang
Dmitry Timoshkov wrote:
> Paul Vriens wrote:
>
What we see is that there are several people who want to help us with
the translation part but have no idea how to code (or are actually
willing to code). We could use them, especially for the more exotic (or
let's call it less ma
On 06/25/2010 12:08 PM, Dmitry Timoshkov wrote:
Paul Vriens wrote:
What we see is that there are several people who want to help us with
the translation part but have no idea how to code (or are actually
willing to code). We could use them, especially for the more exotic (or
let's call it less
Paul Vriens wrote:
> >> What we see is that there are several people who want to help us with
> >> the translation part but have no idea how to code (or are actually
> >> willing to code). We could use them, especially for the more exotic (or
> >> let's call it less mainstream) languages.
> >
> >
On 06/25/2010 11:44 AM, Dmitry Timoshkov wrote:
Paul Vriens wrote:
For the actual resources and their size/placements it would be nice to
have a tool/website as well that could be used to show how the
translated language actually looks in a menu/dialog/whatever with even
the possibility to cha
Paul Vriens wrote:
> >> For the actual resources and their size/placements it would be nice to
> >> have a tool/website as well that could be used to show how the
> >> translated language actually looks in a menu/dialog/whatever with even
> >> the possibility to change things. Is that feasible?
>
On 6/25/2010 13:29, Paul Vriens wrote:
On 06/25/2010 11:23 AM, Dmitry Timoshkov wrote:
Paul Vriens wrote:
For the actual resources and their size/placements it would be nice to
have a tool/website as well that could be used to show how the
translated language actually looks in a menu/dialog/
On Fri, Jun 25, 2010 at 11:14, Paul Vriens wrote:
> On 06/25/2010 11:04 AM, Dmitry Timoshkov wrote:
>
>> Francois Gouget wrote:
>>
>>> We will still need people to take on the somwhat unsexy control resizing
>>>
>>> task and that may be a problem. If it turns out we lack volunteers for
>>> that w
On 06/25/2010 11:23 AM, Dmitry Timoshkov wrote:
Paul Vriens wrote:
For the actual resources and their size/placements it would be nice to
have a tool/website as well that could be used to show how the
translated language actually looks in a menu/dialog/whatever with even
the possibility to cha
Paul Vriens wrote:
> For the actual resources and their size/placements it would be nice to
> have a tool/website as well that could be used to show how the
> translated language actually looks in a menu/dialog/whatever with even
> the possibility to change things. Is that feasible?
What's wr
On 06/25/2010 11:04 AM, Dmitry Timoshkov wrote:
Francois Gouget wrote:
We will still need people to take on the somwhat unsexy control resizing
task and that may be a problem. If it turns out we lack volunteers for
that we may turn to some automatic layout scheme, for instance describe
the reso
Francois Gouget wrote:
> Requiring that translators master both skills severly limits the pool of
> translators we can draw from.
Doesn't this sound similar to so called limitation that exists for people
willing to work on Wine code, but have no appropriate skills? I.e. there is
always a choice
On Wed, 23 Jun 2010, Dmitry Timoshkov wrote:
> Francois Gouget wrote:
>
> > James never meant that Wine would not use rc files at all. What he meant
> > is that rc files would lose their status as the autoritative source for
> > the resource strings and would be mostly generated from po files.
Francois Gouget wrote:
> James never meant that Wine would not use rc files at all. What he meant
> is that rc files would lose their status as the autoritative source for
> the resource strings and would be mostly generated from po files.
The .rc files are much more than just strings, in any
On Sun, 20 Jun 2010, Dmitry Timoshkov wrote:
> James McKenzie wrote:
>
> > Another good reason to drop .rc files and go with the po flow...
>
> Not really. If you'd know what stuff the .rc files contain you wouldn't do
> such claims. The .rc files can't go away in general.
James never meant th
Dmitry Timoshkov wrote:
James McKenzie wrote:
Another good reason to drop .rc files and go with the po flow...
Not really. If you'd know what stuff the .rc files contain you wouldn't do
such claims. The .rc files can't go away in general. James, please learn
subject before commenting
James McKenzie wrote:
> Another good reason to drop .rc files and go with the po flow...
Not really. If you'd know what stuff the .rc files contain you wouldn't do
such claims. The .rc files can't go away in general. James, please learn
subject before commenting.
--
Dmitry.
Michael Stefaniuc wrote:
On 06/19/2010 04:09 PM, Frédéric Delanoy wrote:
Sometimes, when a developer adds a string to En resource file, (s)he
adds it as well to all other non-En resource files.
Isn't that unnecessary?
http://wiki.winehq.org/SublangNeutral says the search order is
1. LANG_N
On 06/19/2010 04:09 PM, Frédéric Delanoy wrote:
Sometimes, when a developer adds a string to En resource file, (s)he
adds it as well to all other non-En resource files.
Isn't that unnecessary?
http://wiki.winehq.org/SublangNeutral says the search order is
1. LANG_NEUTRAL, SUBLANG_NEUTRAL
Sometimes, when a developer adds a string to En resource file, (s)he adds it
as well to all other non-En resource files.
Isn't that unnecessary?
http://wiki.winehq.org/SublangNeutral says the search order is
1. LANG_NEUTRAL, SUBLANG_NEUTRAL
2. LANG_FRENCH, SUBLANG_FRENCH_BELGIAN
3. LANG
26 matches
Mail list logo
