Re: Release set inclusion criteria?

2012-09-11 Thread Claude Paroz
Le lundi 10 septembre 2012 à 19:48 -0400, Chris Leonard a écrit :
 Dear Release Set maintainers,
 
 What exactly qualifies a package for inclusion in the Release Set
 External Dependencies (GNOME)?

Hi Chris,

The (GNOME) part implies that the code is hosted in the GNOME git
infrastructure.

 Given that Epiphany Web Browser
 http://l10n.gnome.org/module/epiphany/
 
 has a dependency on WebKitGTK+ (and it's L10n), does WebKitGTK+
 qualify for that or some other more prominent Release Set?
 
 http://l10n.gnome.org/module/webkit/
 
 Note these tickets (from Epiphany dev asking for WebKitGTK+ L10n):
 
 https://bugzilla.gnome.org/buglist.cgi?quicksearch=610094%2C+610095%2C+610102%2C+610103%2C+610106%2C+610109%2C+610110%2C+610111%2C+610112%2C+610113%2C+610115%2C+610118%2C+610120%2C+610125%2C+610128%2C+610129%2C+610135%2C+610138%2C+610139%2C+610142%2C+610144%2C+610145%2C+610146%2C+610147%2C+610149%2C+610150%2C+610151%2C+610153%2C+610155%2C+610158%2C+610159%2C+610160%2C+610161%2C+610162%2C+610163%2C+610164%2C+610165
 
 The importance of this is that WebKitGTK+ is not presently a member of
 any Release Set (other than OLPC) and it is not getting the L10n it
 deserves.
 
 Yes, it is absolutely true that WebKitGTK+ has other issues with it's
 i18n at present, but making it more visible can only help that i18n
 issue get the attention it requires.

There are several other external packages that contain visible strings
in GNOME (notably those hosted on the Translation Project). We (I?)
choose at some point to limit ourselves to GNOME git + some freedesktop
translation stats. It's somewhat arbitrary and we can decide to change
it or add more exceptions. But generally-speaking I find it rather
frustrating to have statistics on packages you may have to wait several
months before anyone react upstream :-/

As for WebKitGTK+, it's not an option to make it more visible until DL
can generate a proper POT file. The last time it succeeded was on
2010-12-27!

Claude
-- 
www.2xlibre.net

___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: Release set inclusion criteria?

2012-09-11 Thread Chris Leonard
On Tue, Sep 11, 2012 at 3:26 AM, Claude Paroz cla...@2xlibre.net wrote:

 The importance of this is that WebKitGTK+ is not presently a member of
 any Release Set (other than OLPC) and it is not getting the L10n it
 deserves.

 Yes, it is absolutely true that WebKitGTK+ has other issues with it's
 i18n at present, but making it more visible can only help that i18n
 issue get the attention it requires.

 There are several other external packages that contain visible strings
 in GNOME (notably those hosted on the Translation Project). We (I?)
 choose at some point to limit ourselves to GNOME git + some freedesktop
 translation stats. It's somewhat arbitrary and we can decide to change
 it or add more exceptions. But generally-speaking I find it rather
 frustrating to have statistics on packages you may have to wait several
 months before anyone react upstream :-/

 As for WebKitGTK+, it's not an option to make it more visible until DL
 can generate a proper POT file. The last time it succeeded was on
 2010-12-27!

Yes, I am painfully aware of the failure of WebKitGTK+ to provide an
adequate fix for their i18n issue.  Part of my reasoning for wanting
it to make it more visible (other than the fact that all GNOME-based
web-browsing depends on it) is to draw greater attention to the i18n
issue.

It is with sorrow that I understand localizers staying away from
WebKitGTK+ work, but I feel that the fact that WebKitGTK+ is somewhat
hidden by not appearing in any DL release set is only aiding and
abetting the failure of the WebKitGTK+ i18n when we should be shining
a harsh spotlight on this long-standing issue.

cjl
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: Release set inclusion criteria?

2012-09-11 Thread Claude Paroz
Le mardi 11 septembre 2012 à 03:55 -0400, Chris Leonard a écrit :
 On Tue, Sep 11, 2012 at 3:26 AM, Claude Paroz cla...@2xlibre.net wrote:
 
  The importance of this is that WebKitGTK+ is not presently a member of
  any Release Set (other than OLPC) and it is not getting the L10n it
  deserves.
 
  Yes, it is absolutely true that WebKitGTK+ has other issues with it's
  i18n at present, but making it more visible can only help that i18n
  issue get the attention it requires.
 
  There are several other external packages that contain visible strings
  in GNOME (notably those hosted on the Translation Project). We (I?)
  choose at some point to limit ourselves to GNOME git + some freedesktop
  translation stats. It's somewhat arbitrary and we can decide to change
  it or add more exceptions. But generally-speaking I find it rather
  frustrating to have statistics on packages you may have to wait several
  months before anyone react upstream :-/
 
  As for WebKitGTK+, it's not an option to make it more visible until DL
  can generate a proper POT file. The last time it succeeded was on
  2010-12-27!
 
 Yes, I am painfully aware of the failure of WebKitGTK+ to provide an
 adequate fix for their i18n issue.  Part of my reasoning for wanting
 it to make it more visible (other than the fact that all GNOME-based
 web-browsing depends on it) is to draw greater attention to the i18n
 issue.

Hey Gil, stuff for your next blog post :-)

Claude

___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: BoF item 12/14: improvements to gtranslator

2012-09-11 Thread Daniel Mustieles García
Also, please excuse me if my previous mail was so rude... it was no my
intention! :)

I'm a bit sad because I think GT is a good tool, but I can't find a
maintainer to give it some love. I talked with Nacho several months ago
about the possibility of mergin both Virtaal an GT; both have great
features, and creating a tool with them, would be really useful for
translators.

In the other hand, I didn't want to start a flamewar against KDE tools, but
is hard to believe that several GNOME translators use Lokalize... I think
the first step we should do is have our own tools to develope and translate
our own project, isn't it? Having the tools, we will be able to create high
quality software.

Working together, I'm sure we will be able to grow up GT and translation
teams. I don't know how difficult is the issue about locales in glib, but
if I cand help with it, please let me know.

Best regards

2012/9/10 Chris Leonard cjlhomeaddr...@gmail.com

 On Mon, Sep 10, 2012 at 4:36 AM, Daniel Mustieles García
 daniel.mustie...@gmail.com wrote:
  Sorry, but I disagree with you.

 Absolutely no need to apologize.   I asked the question 'Why and
 you've given me an answer, thank you.  I respect your opinion even if
 ti differs from mine, we share far too much in our common interest in
 bringing Gnome to as many languages as possible to not be able to have
 a perfectly civil conversation (as we are) about the optimal tactics
 for achieving common goals.

 I sincerely have no wish to start a flame war or a My favorite tool
 is better than yours back and forth..  I do apologize if my
 enthusiasm for Virtaal came across as speaking ill of other tools.
 Choice is good.

 
  Gtranslator is a very powerful, easy and intuitive translation
 application.
  It's interface is simple, because it hasn't floating elements in the
 window,
  and it has separated boxes for original string, translated string and
  messages table.
 
  Also, having several tools for the same purpose is not a bad thing; if we
  just had one tool for translating, and its maintainer decided to leave
 the
  project... what would we do? Use Lokalize? ;-)
 
  Gtranslator has a really good plugins system, which allows to expand it
  easily. Instead of killing it, we should fight to create a development
 group
  to fix and improve it. Also, as I said at GUADEC, I think GT should be
 part
  of the GNOME desktop applications (since Anjuta is the official IDE, GT
  should be the official translation app). Maybe it would help to find
 someone
  to maintain it.

 I would agree with you that promoting gtranslator from Extra GNOME
 applications to a more prominent Release Set might be a good tactic
 for raising it's profile within the GNOME project.

  GT is done, it's working, and a lot of people uses it. Why don't we try
 to
  fix it? It isn't completely broken; just 2 or 3 important bugs, but it
 works
  perfectly... are you sure you want to drop it? I don't agree and I'll
 keep
  myself trying to improve it, and looking for a maintainer. If we can't
  create or fix our own tools, what are we doing? I'm sure you'll agree
 with
  me it's stupid, por example, to develope GNOME Shell under .NET Framework
  isn't it? Is the same case with GNOME translations and Lokalize. Many
 people
  uses Lokalize to translate GNOME... WTF! GNOME is a big project, with a
  great Marketing and a really great i18n teams... aren't we able to find a
  developer and/or a maintainer to fix and improve our translation tool? I
  don't think so.
 
  Instead of deprecating a working application, help us to fix and improve
 it.
  Please, don't let it die.

 I concede that it would be potentially embarrassing and very possibly
 send the wrong message about GNOME's commitment to L10n, but in the
 end of the day, developers and users will vote with their fingers and
 eyeballs.

 I suspect that I obscured my main message with my expression
 enthusiasm for Virtaal.  The GNOME project (like any) has limited
 developer resources, it is my opinion that improving the submission
 process for glibc locales would have a higher impact on overall GNOME
 i18n than improving gtranslator, given the plethora of options
 available for PO file editing.

 cjl

___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


String additions to 'gtk+.master'

2012-09-11 Thread GNOME Status Pages
This is an automatic notification from status generation scripts on:
http://l10n.gnome.org.

There have been following string additions to module 'gtk+.master':

+ Primary button warps slider
+ Whether a primary click on the trough should warp the slider into 
position

Note that this doesn't directly indicate a string freeze break, but it
might be worth investigating.
http://git.gnome.org/browse/gtk+/log/?h=master
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


String additions to 'folks.master'

2012-09-11 Thread GNOME Status Pages
This is an automatic notification from status generation scripts on:
http://l10n.gnome.org.

There have been following string additions to module 'folks.master':

+ Failed to change property ‘%s’: No suitable personas were found.

Note that this doesn't directly indicate a string freeze break, but it
might be worth investigating.
http://git.gnome.org/browse/folks/log/?h=master
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Requesting (small) string break for gnome-disk-utility

2012-09-11 Thread David Zeuthen
Hey,

In GNOME 3.6 the window manager now displays window titles even if the
dialog is transient for its parent window (In GNOME 3.0 through 3.4
the WM displayed the window as a sheet - e.g. without the window
title). As no name has been set for most dialogs, the window manager
now simply shows gnome-disks which is not very friendly. The fix is
simply to give each dialog a meaningful title

I have patches to fix this - it adds only five new strings - see

 https://bugzilla.gnome.org/show_bug.cgi?id=683831

for details.

OK to push these patches? Thanks!

David
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: Requesting string break and (small) UI break freeze for gnome-control-center

2012-09-11 Thread Shaun McCance
On Mon, 2012-09-10 at 22:34 -0400, Matthias Clasen wrote:
 On Mon, Sep 10, 2012 at 5:22 AM, Matthias Clasen
 matthias.cla...@gmail.com wrote:
  On Mon, Sep 10, 2012 at 5:06 AM, Richard Hughes hughsi...@gmail.com wrote:
  Hi all,
 
  Matthias has spent his weekend fixing some of the glaring UI bugs in
  the control center network panel.
 
  The new changes primarily address this bug:
  https://bugzilla.gnome.org/show_bug.cgi?id=682270 and the new UI looks
  a little different from before and much closer to the mockups provided
  by Allan: http://bugzilla-attachments.gnome.org/attachment.cgi?id=223831
 
  There are 6 new strings:
 
  * today (shown in the wireless panel last-used page)
  * yesterday (shown in the same place)
  * never (shown in the same place)
  * %i day ago(shown in the same place)
  * Out of range (shown in the main wireless panel)
  * Not connected (shown in the VPN window)
 
  I think only the first 2 are new strings, the others were already used
  elsewhere.
  There is one other string change, though. I've added a period at the end of
 
  Network details for %s including password and any custom configuration
  will be lost
 
  That is obviously mostly cosmetic, and can easily be left for later if
  you prefer.
 
 Actually, the 'never', 'today' and 'yesterday' string additions are
 also cosmetic and can easily be left out.
 
 Aaand... now I realize that Richard forgot to cc the docs and i18n
 teams, so we'll never get their ok... CCing them now.

Fine by me. We still need to redo many of those pages anyway.


___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n