On Sat, Jul 13, 2013 at 12:36 AM, Francois Gouget wrote:
> On Fri, 12 Jul 2013, Frédéric Delanoy wrote:
> [...]
>> The "grand dictionnaire terminologique"
>> (http://gdt.oqlf.gouv.qc.ca/Resultat.aspx) gives
>
> The thing is this dictionary is not actually French... it's Québécois.
> One of the dif
On Fri, 12 Jul 2013, Frédéric Delanoy wrote:
[...]
> The "grand dictionnaire terminologique"
> (http://gdt.oqlf.gouv.qc.ca/Resultat.aspx) gives
The thing is this dictionary is not actually French... it's Québécois.
One of the differences is that Québécois is a lot more strict about not
using Eng
On Fri, Jul 12, 2013 at 10:29 PM, GOUJON Alexandre wrote:
> This is particularly true among programmers/network admins.. (who use a lot
> of technical and english terms) but casual users also tend to reject the
> always-translate-into-french idea. Quoting an article that made me laugh so
> hard I
On 07/12/2013 07:30 PM, Frédéric Delanoy wrote:
On Fri, Jul 12, 2013 at 4:33 PM, Francois Gouget wrote:
---
Surprisingly enough (for me) the existing translations match the term
used in Microsoft's Terminology file:
"broadcast address" -> "adresse de di
On Fri, Jul 12, 2013 at 4:33 PM, Francois Gouget wrote:
> ---
>
> Surprisingly enough (for me) the existing translations match the term
> used in Microsoft's Terminology file:
>"broadcast address" -> "adresse de diffusion"
>&quo
Aurimas Fišeras wrote:
> What about something like the attached patch? I resized both check boxes
> and the direction group, positioned radio buttons in the direction group
> one above the other.
>
> I checked this dialog on Windows XP Lithuanian UI, and it had similar
> differences from the Eng
2012.12.02 20:32, Dmitry Timoshkov rašė:
> Aurimas Fišeras wrote:
>
>>>> Controls resized to fit translations for more languages. Tested with
>>>> resource editor.
>>>
>>> Did you see a comment in that file just before dialog templates?
>>
Aurimas Fišeras wrote:
> >> Controls resized to fit translations for more languages. Tested with
> >> resource editor.
> >
> > Did you see a comment in that file just before dialog templates?
> >
> Hello,
> I obviously didn't notice that
2012.12.02 07:46, Dmitry Timoshkov rašė:
> Aurimas Fišeras wrote:
>
>> Controls resized to fit translations for more languages. Tested with
>> resource editor.
>
> Did you see a comment in that file just before dialog templates?
>
Hello,
I obviously didn't noti
Aurimas Fišeras wrote:
> Controls resized to fit translations for more languages. Tested with
> resource editor.
Did you see a comment in that file just before dialog templates?
--
Dmitry.
you would rather translate
from the new English version to keep the different translations in sync
though, I'll go ahead and clean up the wiki some more.
- Kyle
Le 13/03/2012 14:51, Frédéric Delanoy a écrit :
On Tue, Mar 13, 2012 at 11:52, Christian Costa wrote:
Never heard of this rule for french or never paid attention but I'm fine
with it if this is so.
Actually there should sometimes also be thin non-breakable spaces in
po, but those are very badl
when editing the registry. Wine traces
functions also
but I would it is more normal.
Hmm... odd indeed
I think regedit uses the ANSI codepage for the registry, while the
translations are in UTF-8. I experienced this when importing .reg-files
in UTF-8 with special characters in them.
The umlauts in
Le 13/03/2012 16:23, Frédéric Delanoy a écrit :
On Tue, Mar 13, 2012 at 14:30, Henri Verbeet wrote:
On 13 March 2012 00:42, Christian Costa wrote:
BTW, is there an editor that shows them ? gvim doesn't.
Assuming gvim is similar enough to normal vim, you can use listchars
to highlight various
Le 13/03/2012 14:40, Frédéric Delanoy a écrit :
On Tue, Mar 13, 2012 at 00:42, Christian Costa wrote:
BTW, is there an editor that shows them ? gvim doesn't.
Emacs does.
Non-breakable space are only present in french translations. Between a name
and a ':'.
Also after/before
ng the registry. Wine traces
> > functions also
> > but I would it is more normal.
> Hmm... odd indeed
I think regedit uses the ANSI codepage for the registry, while the
translations are in UTF-8. I experienced this when importing .reg-files
in UTF-8 with special characters in them.
The
On Tue, Mar 13, 2012 at 11:52, Christian Costa wrote:
> Never heard of this rule for french or never paid attention but I'm fine
> with it if this is so.
Actually there should sometimes also be thin non-breakable spaces in
po, but those are very badly supported, so are not used here.
Some links
On Tue, Mar 13, 2012 at 00:42, Christian Costa wrote:
> BTW, is there an editor that shows them ? gvim doesn't.
Emacs does.
> Non-breakable space are only present in french translations. Between a name
> and a ':'.
Also after/before '«' and '»&q
On Mon, Mar 12, 2012 at 20:32, Christian Costa wrote:
> Le 12/03/2012 21:02, Nikolay Sivov a écrit :
>
>> On 3/12/2012 21:52, Christian Costa wrote:
>>>
>>> They are displayed as a single space in a text editor but visible with an
>>> hex editor.
>>
>> I guess this is a non-breakable space.
>>
>>
On 13 March 2012 00:42, Christian Costa wrote:
> BTW, is there an editor that shows them ? gvim doesn't.
Assuming gvim is similar enough to normal vim, you can use listchars
to highlight various things. Use nbsp for non-breaking spaces. You can
use Ctrl+K to insert digraphs. Use "NS" for non-break
tch still applies.
> >> I will resend the patch with a description that reflects that.
> > BTW, is there an editor that shows them ? gvim doesn't.
> I see them as normal space in vim but searching for a normal space
> doesn't highlight them. You can use the "high
hat.
> BTW, is there an editor that shows them ? gvim doesn't.
I see them as normal space in vim but searching for a normal space
doesn't highlight them. You can use the "highlight" and "match" command
to show them in a different color.
> Non-breakable space
ay it produces garbage for what the string is used
for so the patch still applies.
I will resend the patch with a description that reflects that.
BTW, is there an editor that shows them ? gvim doesn't.
Non-breakable space are only present in french translations. Between a
name and a ':'.
Le 12/03/2012 21:02, Nikolay Sivov a écrit :
On 3/12/2012 21:52, Christian Costa wrote:
They are displayed as a single space in a text editor but visible
with an hex editor.
I guess this is a non-breakable space.
I don't know. Anyway it produces garbage for what the string is used for
so the
On 3/12/2012 21:52, Christian Costa wrote:
They are displayed as a single space in a text editor but visible with an hex
editor.
I guess this is a non-breakable space.
thank you for taking on this task! i have not had the time to look at
this for 1.4.
some remarks:
#: gdi32.rc:25
msgid "Western"
-msgstr ""
+msgstr "Oriental"
Ocidental?
#: ieframe.rc:46
-#, fuzzy
msgid "&Standard bar"
-msgstr "Barra de &Estado"
+msgstr "&Barra padrão"
i think "Barra de Estad
On 2012-02-22 22:45, Frédéric Delanoy wrote:
4) There has been discussions about some translation websites. Is
there a
chance that such a website would allow easy tagging of potential
errors?
Problem is attribution of changes to respective authors (+ potential
license conflicts). Search the wi
ah-checkouts/gnu/gettext/manual/html_node/Contexts.html#Contexts)
Which is from a section about solving collisions where the same string
is used in two contexts that should receive different translations.
> [speaking of short strings]
> "The problem is that many of the strings which hav
[speaking of short strings]
"The problem is that many of the strings which have to be translated
are very short. They have to appear in pull-down menus which restricts
the length. But strings which are not containing entire sentences or
at least large fragments of a sentence may appear in more
On Wed, 22 Feb 2012, Frédéric Delanoy wrote:
> 2012/2/22 Lauri Kenttä :
> > Hi,
> >
> > Wine has many texts, especially error messages, that are almost impossible
> > to translate without knowing what they're really about. Some are also easy
> > to misunderstand.
> >
> > An example from dlls/kerne
#x27;s not guaranteed.
You can use git-blame to find the last author of a specific line
Spamming bugzilla is not an option IMO.
> , or send patches to add #fuzzy comments and hope I'm right?
If you only *hope* to be right, don't send such patches
> And if it's wrong in many of the l
Hi,
Wine has many texts, especially error messages, that are almost
impossible to translate without knowing what they're really about. Some
are also easy to misunderstand.
An example from dlls/kernel32/winerror.mc:
msgid "Notify change request in progress.\n"
Some interpretations:
de, nb: "A
;.
Sorry, I did not mean to imply you're too slow or anything. I also
meant
to CC you to be sure you'd have a chance to review my patches and I'm
not sure how you got left out of my emails.
I got the copy, but considering that AJ applies the submitted patches
each day, it was just
ade the connection. I'm not sure how the colon helps
as this is meant to form just one sentence 'Key every 9 frames' but I'll
just trust you on that.
> My opinion is that the original text should be in one piece or at
> least have a msgctxt to allow better translation
"Thai" is right, "Thain" is wrong. Please don't mess with Finnish if
you don't know it. As I've said, I'm working on it. If you feel I'm too
slow, feel free to hire me and I'll do it faster. ;)
I'm currently away from my computer, but I'll send my patch this
weekend. It will have almost everyt
Luca Bennati writes:
> 2- Are the following highlighted strings (and similar) translatable or they
> were wrongly recognized by script?
>
> http://source.winehq.org/transl/resource.php?branch=master&lang=010%3A00&resfile=dlls%2Fdinput&type=5&id=1&pedantic=
>
> http://source.winehq.org/transl/reso
Hi all, I would like to clarify some doubts I have about Wine translations
and its po/rc files:
1- Are the following highlighted strings errors from the script converting
from rc to po or due to malformatted po files (seems not to recognize
msgctx lines)?
http://source.winehq.org/transl
On Mon, Sep 26, 2011 at 11:14 AM, Michael Stefaniuc wrote:
> Also when Alexandre does "git am" the patch it will fail too.
I just asked Alexandre, and he agrees with you that buildbot should
reject patches that require fuzz.
On 09/26/2011 06:32 PM, Dan Kegel wrote:
> On Mon, Sep 26, 2011 at 2:59 AM, Jerome Leclanche wrote:
>> On Mon, Sep 26, 2011 at 8:46 AM, Francois Gouget wrote:
>>> On Sun, 25 Sep 2011, Dan Kegel wrote:
Patch fails to apply here?
error: patch failed: po/ko.po:11305
error: po/ko.
On Mon, Sep 26, 2011 at 2:59 AM, Jerome Leclanche wrote:
> On Mon, Sep 26, 2011 at 8:46 AM, Francois Gouget wrote:
>> On Sun, 25 Sep 2011, Dan Kegel wrote:
>>> Patch fails to apply here?
>>>
>>> error: patch failed: po/ko.po:11305
>>> error: po/ko.po: patch does not apply
>>
>> That's strange. Th
Sounds like encoding/charset issues. Dan, is buildbot's the same as
the file and/or patch?
On Mon, Sep 26, 2011 at 8:46 AM, Francois Gouget wrote:
> On Sun, 25 Sep 2011, Dan Kegel wrote:
>
>> Patch fails to apply here?
>>
>> error: patch failed: po/ko.po:11305
>> error: po/ko.po: patch does not a
On Sun, 25 Sep 2011, Dan Kegel wrote:
> Patch fails to apply here?
>
> error: patch failed: po/ko.po:11305
> error: po/ko.po: patch does not apply
That's strange. The patch attached to the email I received on
wine-patches applies fine on a pristine tree here.
--
Francois Gouget
Patch fails to apply here?
error: patch failed: po/ko.po:11305
error: po/ko.po: patch does not apply
-- Forwarded message --
From:
Date: Sun, Sep 25, 2011 at 5:35 PM
Subject: Re: 79310: po: Mark translations with mismatched printf
format directives as fuzzy.
To: d...@kegel.com
Am 23.08.2011 22:57, schrieb Francois Gouget:
>
> On Mon, 22 Aug 2011, Alexandre Julliard wrote:
>
>> Module: wine
>> Branch: master
>> Commit: aeb9f621292dec7a6366209106468da8d0371684
>> URL:
>> http://source.winehq.org/git/wine.git/?a=commit;h=aeb9f621292dec7a6366209106468da8d0371684
>
> I
On Mon, 22 Aug 2011, Alexandre Julliard wrote:
> Module: wine
> Branch: master
> Commit: aeb9f621292dec7a6366209106468da8d0371684
> URL:
> http://source.winehq.org/git/wine.git/?a=commit;h=aeb9f621292dec7a6366209106468da8d0371684
I think the string below should really be translated. It's dis
Frédéric Delanoy writes:
> It's just that it feels weird to add a context for a specific form of
> a specific language
> Ex: HKY_NONE "None" in comctl32.rc:44
>
> converted to HKY_NONE "#msgctxt#feminine agreement#None"
>
> since this agreement doesn't exist in English
>
> Is it the way it shoul
2011/4/22 Alexandre Julliard :
> Frédéric Delanoy writes:
>
>> OTOH, creating a distinct msgcontext for every agreement in every
>> supported language may be overkill, although the number of affected
>> msgids is limited.
>>
>> What's your opinion on how to handle that, folks?
>
> Feel free to add
Frédéric Delanoy writes:
> OTOH, creating a distinct msgcontext for every agreement in every
> supported language may be overkill, although the number of affected
> msgids is limited.
>
> What's your opinion on how to handle that, folks?
Feel free to add contexts where necessary.
--
Alexandre
ing to context, it can be translated (in French) as either
"Aucun" or "Aucune" (agreements on the same word).
Admitedly, it could be translated with "Aucun(e)" but that seems more
like a workaround and feels a bit weird (user shouldn't see partially
incorrect/odd
On 01/05/2011 09:44 PM, Sven Baars wrote:
Hey all,
since today, the "N" string shows up as missing on
http://source.winehq.org/transl/ even though it's there in the po file.
This happened for both xcopy and cmd. In the po file it says
#: cmd.rc:257 xcopy.rc:41
msgctxt "No key"
msgid "N"
msgstr
Hey all,
since today, the "N" string shows up as missing on
http://source.winehq.org/transl/ even though it's there in the po file.
This happened for both xcopy and cmd. In the po file it says
#: cmd.rc:257 xcopy.rc:41
msgctxt "No key"
msgid "N"
msgstr "N"
so this is probably because the str
Amine Khaldi wrote:
[nothing]
Can you please put some sort of tracking information when resubmitting a
patch like [try2].
This will keep those of us who are manually tracking and applying your
fixes in sync.
Thank you.
James McKenzie
On Mon, Jul 12, 2010 at 6:08 AM, Dmitry Timoshkov
wrote:
> Michael Stefaniuc wrote:
>
>> This affects the Bg, Cs, Da, Eo, Fi, Hu, Sk, Tr and Wa translations.
>
> It's better to have it, even not translated. String resources should be
> fully filled up. Why do remove thi
Michael Stefaniuc wrote:
> This affects the Bg, Cs, Da, Eo, Fi, Hu, Sk, Tr and Wa translations.
It's better to have it, even not translated. String resources should be
fully filled up. Why do remove this one and leave the others?
--
Dmitry.
Hi,
Łukasz did it, Polish translations of Wine reached the 100% mark !!!
Great job done.
--
Cheers,
Paul.
Hi,
Just a note to thank Ricardo for getting the Portuguese translations
back to 100%.
--
Cheers,
Paul.
On 6/11/2010 09:30, Dmitry Timoshkov wrote:
Igor Paliychuk wrote:
Updating Ukrainian translations to kernel32(ukr.nls).
file : ukrainian-kernel32-ukr-nls.patch
You forgot to mention what's wrong with current ukr.nls.
I asked Igor to update genitive months names, so i
Igor Paliychuk wrote:
> Updating Ukrainian translations to kernel32(ukr.nls).
> file : ukrainian-kernel32-ukr-nls.patch
You forgot to mention what's wrong with current ukr.nls.
--
Dmitry.
Paul Vriens writes:
> Just saw that your original patches where created from the
> top-level. I guess it's due to the patchwatcher site disliking non Git
> patches?
Yes, the filtering script has some issues with non-git patches that only
create new files. I put in some fixes, but using git patch
On 02/12/2010 04:41 PM, Paul Vriens wrote:
On 02/11/2010 02:36 PM, José Manuel Ferrer Ortiz wrote:
As requested, I'll resend these patches, splitting them one message per
module. This way it looks a lot more professional :D
I've also fixed a few things that were wrong or could be better:
- Swit
On 02/11/2010 02:36 PM, José Manuel Ferrer Ortiz wrote:
As requested, I'll resend these patches, splitting them one message per
module. This way it looks a lot more professional :D
I've also fixed a few things that were wrong or could be better:
- Switched to UTF-8 encoding, and added the requir
On 2/10/2010 20:28, José Manuel Ferrer Ortiz wrote:
Hello all. Here you are a few newly translated Spanish resource files,
for hhctrl, iccvid, localspl and mapi32 dlls.
Regards,
José Manuel
Hi, Jose.
Use UTF-8 encoding with corresponding pragma directive.
+#include "localspl_private.h"
+
+LA
Hi Paul,
Paul Vriens wrote:
> If a module does not have any translatable resources (for examples
> dlls/atl) we don't show this module on the language pages.
>
> We do however show it on the "English (United States)" one:
yeah, that confused me too when splitting out the rc file handling in
the M
Hi,
If a module does not have any translatable resources (for examples
dlls/atl) we don't show this module on the language pages.
We do however show it on the "English (United States)" one:
http://source.winehq.org/transl/lang.php?lang=009%3A01
Do we still want that, or can it be removed so
Paul Vriens wrote:
Ken Sharp wrote:
Can someone tell me what's going on on this page
http://source.winehq.org/transl/lang.php?lang=009%3A00 ?
If you click on the bottom links (locales) I see a message "Invalid
resource file". Does this mean the resource file doesn't exist, or is
there a lit
Ken Sharp wrote:
Can someone tell me what's going on on this page
http://source.winehq.org/transl/lang.php?lang=009%3A00 ?
If you click on the bottom links (locales) I see a message "Invalid
resource file". Does this mean the resource file doesn't exist, or is
there a little oops in the link
Can someone tell me what's going on on this page
http://source.winehq.org/transl/lang.php?lang=009%3A00 ?
If you click on the bottom links (locales) I see a message "Invalid
resource file". Does this mean the resource file doesn't exist, or is
there a little oops in the links?
Thanks,
Ken.
Paul Vriens writes:
> Hi,
>
> This question came to me when I saw Austin's patch about adjusting
> notepad resources to more closely match XP.
>
> Is there some kind of copyright on the resources? Are we allowed to
> use the same strings or should it always be our own words (like with
> comments
Austin English wrote:
On Tue, Jul 7, 2009 at 12:46 AM, Paul Vriens wrote:
Hi,
This question came to me when I saw Austin's patch about adjusting notepad
resources to more closely match XP.
Is there some kind of copyright on the resources? Are we allowed to use the
same strings or should it alw
On Tue, Jul 7, 2009 at 12:46 AM, Paul Vriens wrote:
> Hi,
>
> This question came to me when I saw Austin's patch about adjusting notepad
> resources to more closely match XP.
>
> Is there some kind of copyright on the resources? Are we allowed to use the
> same strings or should it always be our ow
Hi,
This question came to me when I saw Austin's patch about adjusting
notepad resources to more closely match XP.
Is there some kind of copyright on the resources? Are we allowed to use
the same strings or should it always be our own words (like with
comments in the source)?
--
Cheers,
P
Davide Pizzetti wrote:
i've got a question: how i produce a patch with 'git diff'? what is the
correct syntax of the command?
Il giorno mer, 24/06/2009 alle 19.17 +0400, Nikolay Sivov ha scritto:
Davide Pizzetti wrote:
Here are the italian translations for winecfg.
Davide Pizzetti wrote:
Here are the italian translations for winecfg.
1. Use 'git diff' format to produce patches
2. Use plain text attachments.
Feel free to ask here any related questions.
Frans Kool wrote:
Beat you to it ;)
http://www.winehq.org/pipermail/wine-patches/2009-June/074719.html
--
Cheers,
Paul.
Francois Gouget writes:
> On Mon, 22 Jun 2009, Frédéric Delanoy wrote:
> [...]
>> Furthermore,
>> - the "65001" should probably be replaced by "utf8" (I checked in
>> tools/wrc/parser.l:373) [ which would be better IMNSHO in new/updated
>> resource file]
>
> Do the Windows/Mingw resource compiler
On Mon, 22 Jun 2009, Frédéric Delanoy wrote:
[...]
> Furthermore,
> - the "65001" should probably be replaced by "utf8" (I checked in
> tools/wrc/parser.l:373) [ which would be better IMNSHO in new/updated
> resource file]
Do the Windows/Mingw resource compilers support utf8 there?
--
Francois G
Hi all,
According to http://wiki.winehq.org/Developers-Hints on the
"http://wiki.winehq.org/Developers-Hints";, AFAICT the resource
files should generally
- use the default Windows codepage for the specified language
or
- use UTF-8 surround with "#pragma code_page(65001)" at the top of the
file a
Frans Kool wrote:
You're mixing tabs and spaces.
--
Cheers,
Paul.
2008/11/16 Kario <[EMAIL PROTECTED]>:
> hi, my name is Mario Kacmar, I am from Slovakia
>
> and I made this patch with Slovak translations
>
> please commit my patch, or if is something wrong
>
> please contact me back
>
>
&
Michael Stefaniuc wrote:
> there are a couple resource file translations that are so way out of
> sync that they are commented out of the main rc file of the relevant
> module.
>
> programs/winecfg/winecfg.rc:
>
> - Pt.rc - Portuguese (Brazi
Hello guys,
there are a couple resource file translations that are so way out of
sync that they are commented out of the main rc file of the relevant
module.
programs/progman/rsrc.rc:
-
- Da.rc - Danish
- Fi.rc - Finnish
- Sk.rc - Slovak
- Sw.rc - Swedish (correct
I think the release candidate phase for Wine 1.0 is a good time to add
new translations and it's also important to fix out-of-sync resources.
They may cause programs to run incorrectly when running under with a
different language (I've filled a bug about it:
http://bugs.
ame phrase already translated in other projects.
> * pick the most appropriate suggestion.
> * watch the percentage bars go up.
I think the problem is extracting the strings to translate from the rc
files, and combining the translations with the reference rc file to
generate a translated rc fi
Hello Lei,
Lei Zhang wrote:
> On Tue, Mar 18, 2008 at 5:30 AM, Michael Stefaniuc <[EMAIL PROTECTED]> wrote:
>> We should try to update the translations of Wine to other languages for
>> 1.0. The code freeze during the release candidate time frame is perfect
>> f
On Tue, Mar 18, 2008 at 5:30 AM, Michael Stefaniuc <[EMAIL PROTECTED]> wrote:
> Hello!
>
> We should try to update the translations of Wine to other languages for
> 1.0. The code freeze during the release candidate time frame is perfect
> for this as the translations
Michael Stefaniuc wrote:
> Hello!
>
> We should try to update the translations of Wine to other languages for
> 1.0. The code freeze during the release candidate time frame is perfect
> for this as the translations don't have to track a moving target.
>
> Somebody had s
Paul Vriens wrote:
> Michael Stefaniuc wrote:
>> Hello!
>>
>> We should try to update the translations of Wine to other languages for
>> 1.0. The code freeze during the release candidate time frame is perfect
>> for this as the translations don't have to tra
Hello!
We should try to update the translations of Wine to other languages for
1.0. The code freeze during the release candidate time frame is perfect
for this as the translations don't have to track a moving target.
Somebody had scripts/a web page to check for missing translations or
b
"Frans Kool" <[EMAIL PROTECTED]> wrote:
> From 2e5bda68273038f924f8f0d1b325a2a4c71f17ae Mon Sep 17 00:00:00 2001
> From: Frans Kool <[EMAIL PROTECTED]>
> Date: Tue, 12 Feb 2008 12:04:56 +0100
> Subject: Oleview: Added Dutch translations
This your patch as
Daniel Nylander wrote:
> I have translated a lot of programs and dlls to Swedish.
> Would be great if someone could commit this to git.
>
> http://home.danielnylander.se/translations/wine/wine-sv.tar.gz
>
>
> Please also add the following to the ./tools/wine.desktop
>
>
On 10/15/07, Daniel Nylander <[EMAIL PROTECTED]> wrote:
>
> I have translated a lot of programs and dlls to Swedish.
> Would be great if someone could commit this to git.
>
It's your responsibility to get your own patches accepted.
> http://home.danielnylander.se/transl
> I have translated alot of programs and dlls to Swedish now.
> Would be great if someone could commit this to git
>
> http://home.danielnylander.se/translations/wine/wine-sv.tar.gz
Please also add the following to the ./tools/wine.desktop
Name[sv]=Windows-emulatorn Wine
--
Dan
t if someone could commit this to git
http://home.danielnylander.se/translations/wine/wine-sv.tar.gz
--
Daniel Nylander (CISSP, GCUX, GCFA)
Stockholm, Sweden
http://www.DanielNylander.se
[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
fre 2007-10-12 klockan 14:02 +0200 skrev Marcus Meissner:
> > I would really like to translate the graphical tools (such as winecfg)
> > but as I can see it, it's not possible at the moment.
> >
> > Have you thought about implementing some sort of i18n/l10n framework?
>
> This is done via the Wi
On Fri, Oct 12, 2007 at 01:44:45PM +0200, Daniel Nylander wrote:
>
> I would like to contribute to the Wine project by submitting Swedish
> translations.
>
> I would really like to translate the graphical tools (such as winecfg)
> but as I can see it, it's not possible a
I would like to contribute to the Wine project by submitting Swedish
translations.
I would really like to translate the graphical tools (such as winecfg)
but as I can see it, it's not possible at the moment.
Have you thought about implementing some sort of i18n/l10n framework?
Regards,
D
On 9/25/06, Mikołaj Zalewski <[EMAIL PROTECTED]> wrote:
Yes, I could try to do it. However I would need to know where could I
find some winehq.org pages source codes that could be used as an
example, how to send my code (also through wine-patches?) and how to
update the data files for the pages
uot; equivalent as well...
Yes, currently every resource is counted as one (also a string table
that could have up to 16 strings or a menu with many items). Maybe if
someone will start translating the kernel32 message table I'll look into it.
As of the German translations I've fou
To check what needs to be translated I have played a bit with wrc
--verify-translation and made some HTML from it's results. As this
might interest other translators I've put the statistics at
http://pf128.krakow.sdi.tpnet.pl/wine-transl/ .
Very nice! It would be cool if we could integra
On 25.09.2006 13:29, Mikołaj Zalewski wrote:
> To check what needs to be translated I have played a bit with wrc
> --verify-translation and made some HTML from it's results. As this might
> interest other translators I've put the statistics at
> http://pf128.krakow.sdi.tpnet.pl/wine-transl/ .
Nice
1 - 100 of 117 matches
Mail list logo
