Hi, there is one more change regarding the new gsettings schema, the reason
for the change is well described in bug 658242 [1]
- _summaryhpaned value/_summary
- _descriptionThe hpaned value for the main window./_description
+ _summaryHorizontal split/_summary
+
2011/9/7 Kenneth Nielsen k.nielse...@gmail.com
Since these string changes would be a string freeze break, please ask for
approval of this in a separate thread with an appropriate subject line so
the right people see it.
Regards Kenneth
Ok, I'll do it by this way, thanks for the advice!
As Kenneth Nielsen has suggested, I'm creating a new thread for this string
freeze break request.
There is one more change regarding the new gsettings schema, the reason for
the change is well described in bug 658242 [1]
- _summaryhpaned value/_summary
- _descriptionThe hpaned value
2011/9/7 Andre Klapper ak...@gmx.net
We're not under Hardcode Freeze yet and I don't consider this a UI
change as these are GSettings strings (both would be release team
territory).
This is about String Freeze, hence the L10N Coordination team has to
decide...
See
2011/9/4 Piotr Drąg piotrd...@gmail.com
You did not include the new GSettings schema in POTFILES.in file, so
it's not translatable at the moment.
Resolved!
Thanks Piotr!
--
Javier Hernández Antúnez
Área de Operaciones
Emergya Consultoría
Tlfno: +34 954 51 75 77
Fax: +34 954 51 64 73
I've removed the old gconf schema for to include the new gsettings one due
to the 'Port to GSettings' work. [1][2]
Best regards!
[1] https://bugzilla.gnome.org/show_bug.cgi?id=625902
[2] commit:
http://git.gnome.org/browse/accerciser/commit/?id=85fc11dc5503dfd826f27b55f680d8c1b16ca469
--
There is a slightly modification in about dialog:
- COPYRIGHT = _('accerciser Copyright © 2006, 2007 IBM Corporation (BSD)')
+ COPYRIGHT = _('accerciser Copyright (c) 2006, 2007 IBM Corporation (BSD)')
commit:
2011/8/29 F Wolff frie...@translate.org.za
Hi Javier
Is this change needed?
I thought there is a general move towards more
typographically correct characters and punctuation? There is no problem
to have non-ASCII characters in the translatable strings:
