Hallo Richard
Thanks for adding all the translator comments. I read the pot quickly
and a few things still made me wonder. They are listed below. Hope it
helps.
Regards Kenneth Nielsen
#: ../data/gnome-color-manager.schemas.in.h:4
msgid ""
"If set to TRUE then the __ICC_PROFILE atom will be set,
On 20 February 2010 16:28, Philip Withnall wrote:
> In addition to the comments Bruce has made, I've got a few:
Thanks guys, I've committed quite a few fixes. Cheers.
Richard.
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailm
On Fri, 2010-02-19 at 11:12 +, Richard Hughes wrote:
> Hey,
>
> I've attached the gnome-color-manager.pot file for current git master.
> I would very much appreciate it if you language legends could take a
> look at my attempts to make calibrating color easy, and suggest better
> sentences if
On Fri, 2010-02-19 at 11:12 +, Richard Hughes wrote:
> Hey,
>
> I've attached the gnome-color-manager.pot file for current git master.
> I would very much appreciate it if you language legends could take a
> look at my attempts to make calibrating color easy, and suggest better
> sentences if
Hey,
I've attached the gnome-color-manager.pot file for current git master.
I would very much appreciate it if you language legends could take a
look at my attempts to make calibrating color easy, and suggest better
sentences if my words do not make sense. If there are any difficult to
translate s
Hi,
resending this.
Danilo Šegan wrote:
Today at 21:08, Vincent Untz wrote:
The difficult part is, however, to make maintainers use this database
when they add new strings. I don't know how we could do this.
I think it would be simple to make them use it provided we have a good
"similarity"
On 22 Sep 2005, at 12:14, Calum Benson wrote:
On 21 Sep 2005, at 19:49, Christian Persch wrote:
To fix this, I think we need:
- a String Guidelines addendum to the HIG. The HIG already tells
us what
capitalisation to use in which circumstances; we need a complete
style
guide;
I'd ce
On 21 Sep 2005, at 19:49, Christian Persch wrote:
To fix this, I think we need:
- a String Guidelines addendum to the HIG. The HIG already tells us
what
capitalisation to use in which circumstances; we need a complete style
guide;
I'd certainly be quite happy for the HIG to include a list
Hi,
Danilo Šegan wrote:
Today at 21:08, Vincent Untz wrote:
The difficult part is, however, to make maintainers use this database
when they add new strings. I don't know how we could do this.
I think it would be simple to make them use it provided we have a good
"similarity" matching algorit
Today at 21:08, Vincent Untz wrote:
> The difficult part is, however, to make maintainers use this database
> when they add new strings. I don't know how we could do this.
I think it would be simple to make them use it provided we have a good
"similarity" matching algorithm.
Also, this will onl
To fix this, I think we need:
> - a String Guidelines addendum to the HIG. The HIG already tells us what
> capitalisation to use in which circumstances; we need a complete style
> guide;
> - a database of all (present and past) string in all GNOME modules, and
> ways to find 'si
the file X, is it
'called' X, or 'named' X?
- the varying presentation of the message, i.e. how the variable data
(%s) is embedded in it: no quotes, single quotes, double quotes, pango
markup.
To fix this, I think we need:
- a String Guidelines addendum to the HIG. The HIG alr
12 matches
Mail list logo
