On 10/10/2017 01:04 PM, Dietmar Maurer wrote:
> I don't really like that, because it is an additional string to translate.
>
I had never a problem to run a translation cycle before every
release, the problem is that I am only able to maintain German
and Italian (with the great review help of our community).
If we cannot maintain a single one-time translation for a language
and must fight with nails an teeth each time we want to improve/change
meaning then maybe its worth a thought if we should just remove those
translations completely?
As then its highly likely that there were no such translation made
quite a while and thus the whole translation is outdated or misses
big parts, rendering it unusable.
A short evaluation of how many non-obsolete fuzzy (i.e. new or
outdated) translations are there shows:
# for f in *.po; do (echo "$f:" $(awk '/fuzzy/{getline; if (/^msgid/) print}'
"$f" | wc -l)); done | sort -n -r -k2
sv.po: 147
tr.po: 140
pt_BR.po: 140
pl.po: 140
da.po: 140
ca.po: 140
ru.po: 139
sl.po: 138
zh_CN.po: 112
fa.po: 111
eu.po: 109
es.po: 89
gl.po: 88
nn.po: 67
nb.po: 67
hu.po: 66
fr.po: 64
ja.po: 21
de.po: 7
it.po: 6
FYI, we have 572 unique non-obsolete `msgid` strings.
German and Italian look OK, picked up a few this cycle but all in
all manageable - I plan to do another translation cycle before 5.1
getting back to 0 here.
The other ones are not quite that good looking.
IMHO, it's not the problem that nobody of the community wants to
step up here but rather that for most there is too much hassle
involved to do so - at least for people not used to git and/or
development in general (which would need to sign the CLA here too).
If there was a simple interface where a user could just edit/confirm
translations (i.e. a display and a input field pro msgid) we probably
could motivate enough people to sanely maintain the most used or
wanted translation. I looked at Pootle [1] and Zanata [2] as such
interfaces but was rather disappointed, both monsters and not even
that simple to use from a translator POV (IMHO).
Fabian just pointed me to weblate [3][4] which looks acceptable.
So even if I'd prefer that, maybe its could be an option tell people
to use POEdit [3], or another offline PO Editor and let them send the
updated files directly to use where we can add it to the repo (I would
gladly take care of that). I simply see no disadvantage there as there
is no upfront work needed and we could just win as I really do not think
that this would result in less translations :)
Also, dropping those translations which we cannot maintain our self
and where nobody from the community has interest in doing so makes
sense too, IMHO.
[1] http://pootle.translatehouse.org/
[2] http://zanata.org/
[3] https://hosted.weblate.org/
[4] https://github.com/WeblateOrg/weblate
[5] https://poedit.net/
>
>> On October 10, 2017 at 12:49 PM Thomas Lamprecht <t.lampre...@proxmox.com>
>> wrote:
>>
>>
>> To make it more clear that this will always end you on the
>> Manual index.
>>
>> Also, multiple Help buttons which all may or may not do something
>> different are a bit weird/confusing - thus distinction is important
>> IMO.
>>
>> Adapt the icon displayed to `fa-book` which resembles the icon which
>> is often used for manuals and is clearer than a '?', IMO.
>> ---
>> www/manager6/Workspace.js | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/www/manager6/Workspace.js b/www/manager6/Workspace.js
>> index 9376cea5..6e50abcb 100644
>> --- a/www/manager6/Workspace.js
>> +++ b/www/manager6/Workspace.js
>> @@ -326,9 +326,10 @@ Ext.define('PVE.StdWorkspace', {
>> xtype: 'pveHelpButton',
>> hidden: false,
>> baseCls: 'x-btn',
>> - iconCls: 'fa fa-info-circle
>> x-btn-icon-el-default-toolbar-small ',
>> + iconCls: 'fa fa-book
>> x-btn-icon-el-default-toolbar-small ',
>> listenToGlobalEvent: false,
>> onlineHelp: 'pve_documentation_index',
>> + text: gettext('Manual'),
>> margin: '0 5 0 0'
>> },
>> createVM,
>> --
>> 2.11.0
>>
>>
>> _______________________________________________
>> pve-devel mailing list
>> pve-devel@pve.proxmox.com
>> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
_______________________________________________
pve-devel mailing list
pve-devel@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
