I18n bugs in kspread: untranslatable strings

Hi,

again some untranslatable strings, this time in KSpread.

In the Extras menu:
"Script Editor" ->
plugins/scripting/scripts/scripteditor/ScriptEditor.rc
"Export to HTML File..." ->
plugins/scripting/scripts/exporthtml/ExportHtml.rc
"Script Manager..." in
kspread/plugins/scripting/scripting.cc with 
i18n("Script Manager...")

In addition all strings in the dialog "Export to HTML
File" and all menuitems 
in the dialog "Script Editor" are untranslatable.

All these strings are not extracted to kspreads message
catalog, possibly an 
error in the messages target?

Burkhard Lück
_______________________________________________
koffice-devel mailing list
koffice-develkde.org
h
ttps://mail.kde.org/mailman/listinfo/koffice-devel

Hi Burkhard,

On Sunday 22 October 2006 21:05, Burkhard Lück wrote:
> again some untranslatable strings, this time in
KSpread.
>
> In the Extras menu:
> "Script Editor" ->
plugins/scripting/scripts/scripteditor/ScriptEditor.rc
> "Export to HTML File..." ->
> plugins/scripting/scripts/exporthtml/ExportHtml.rc
"Script Manager..." in
> kspread/plugins/scripting/scripting.cc with
i18n("Script Manager...")
>
> In addition all strings in the dialog "Export to
HTML File" and all
> menuitems in the dialog "Script Editor" are
untranslatable.
>
> All these strings are not extracted to kspreads message
catalog, possibly
> an error in the messages target?

i18n("Script Manager") comes from
libs/kross/core/guimanager.* and there it's 
translated, or?
Re the both *.rc files; we have for sure the same prob with
all scripts (also 
those one the user is able to fetch via GHNS). I am not sure
such strings 
really belong to KSpread since e.g. the CopyCenter-script is
used within Kexi 
and KSpread. The scripts do not use any translation-tech so
far. Once in a 
while the idea was to use PyQt's/QtRuby's tr/i18n for it,
but that could be 
only done for scripts that use on of them while there are
scripts (like 
pilimport/pilexport in trunk) that don't.
So, I am currently not sure what could be the best way to
have scripts in 
future translated. Maybe use just some dummy-method like
"def TranslateMe(self, s): return s" and then grep
for "TranslateMe()"? But 
that could only work for scripts that are actualy
distributed by default 
since other scripts may change even after release (cause
they are distributed 
outside of any release-circle). Well, same goes somewhat for
the with 
applications distributed scripts since a new release of a
script could be any 
time appear at kde-files.org even after release and the new
script may 
contain new/changed strings as well.
Anyway, at least for the captions of the menuitem's
displayed at 
Tools=>Scripts it could be for sure done since imho they
won't change in 
there lifetime anyway...

Any idea/feedback on that issue is for sure wanted 

-- 
Sebastian Sauer aka dipesh[sebsauer]
http://www.dipe.or
g/public_key.asc
Fingerprint: 8F1E 219B 16E6 4EC7 29CC F408 E193 65E2 9134
2221
Coder in http://www.koffice.org
&& http://www.kmldonkey.org
_______________________________________________
koffice-devel mailing list
koffice-develkde.org
h
ttps://mail.kde.org/mailman/listinfo/koffice-devel

Sebastian Sauer said the following, On 2006-10-23 12:28:

>>again some untranslatable strings, this time in
KSpread.
>>
>>In the Extras menu:
>>"Script Editor" ->
plugins/scripting/scripts/scripteditor/ScriptEditor.rc
>>"Export to HTML File..." ->
>>plugins/scripting/scripts/exporthtml/ExportHtml.rc
"Script Manager..." in
>>kspread/plugins/scripting/scripting.cc with
i18n("Script Manager...")
>>
>>In addition all strings in the dialog "Export
to HTML File" and all
>>menuitems in the dialog "Script Editor"
are untranslatable.
>>
>>All these strings are not extracted to kspreads
message catalog, possibly
>>an error in the messages target?
> 
> 
> i18n("Script Manager") comes from
libs/kross/core/guimanager.* and there it's 
> translated, or?
> Re the both *.rc files; we have for sure the same prob
with all scripts (also 
> those one the user is able to fetch via GHNS). I am not
sure such strings 
> really belong to KSpread since e.g. the
CopyCenter-script is used within Kexi 
> and KSpread. The scripts do not use any
translation-tech so far. Once in a 
> while the idea was to use PyQt's/QtRuby's tr/i18n for
it, but that could be 
> only done for scripts that use on of them while there
are scripts (like 
> pilimport/pilexport in trunk) that don't.
> So, I am currently not sure what could be the best way
to have scripts in 
> future translated. Maybe use just some dummy-method
like
> "def TranslateMe(self, s): return s" and then
grep for "TranslateMe()"? But 
> that could only work for scripts that are actualy
distributed by default 
> since other scripts may change even after release
(cause they are distributed 
> outside of any release-circle). Well, same goes
somewhat for the with 
> applications distributed scripts since a new release of
a script could be any 
> time appear at kde-files.org even after release and the
new script may 
> contain new/changed strings as well.
> Anyway, at least for the captions of the menuitem's
displayed at 
> Tools=>Scripts it could be for sure done since imho
they won't change in 
> there lifetime anyway...
> 
> Any idea/feedback on that issue is for sure wanted 

This is similar problem to the soon-to-be-identified one
with translation of 
Kexi Form's labels. Since scripting (and maybe forms) will
be spread over 
KOffice for next releases, the problem will be even more
visible.
My proposed solution (for KOffice 2.x of course) is to have
the translation 
system more user-friendly and separated from SVN:

i.e. to have an option for storing translations within a
project file (with 
optional language packs, but without a need for packaging
the content (no 
dependency on packagers: moved to user-space), thus having
the stuff GHNS-friendly

Until something like this is developed, Sebastian's advice
seems to be the 
only workaround.

No doubt there can be reuse of some existing translation
infrastructure, I 
hope that internals can be hidden.

For Qt bindings void QApplication::installTranslator (
QTranslator * )  could 
be used; see also KDETranslator class.

-- 
regards / pozdrawiam, Jaroslaw Staniek
  Sponsored by OpenOffice Polska (http://www.openoffice
.com.pl/en) to work on
  Kexi & KOffice: http://www.kexi-project.o
rg, http://www.koffice.org
  KDE3 & KDE4 Libraries for MS Windows: http://kdelibs.com, http://www.kde.org
_______________________________________________
koffice-devel mailing list
koffice-develkde.org
h
ttps://mail.kde.org/mailman/listinfo/koffice-devel

Am Montag, 23. Oktober 2006 12:28 schrieb Sebastian Sauer:
>
> On Sunday 22 October 2006 21:05, Burkhard Lück wrote:
> > again some untranslatable strings, this time in
KSpread.
> >
> > In the Extras menu:
> > "Script Editor" ->
plugins/scripting/scripts/scripteditor/ScriptEditor.rc
> > "Export to HTML File..." ->
> > plugins/scripting/scripts/exporthtml/ExportHtml.rc
"Script Manager..." in
> > kspread/plugins/scripting/scripting.cc with
i18n("Script Manager...")
> >
> > In addition all strings in the dialog "Export
to HTML File" and all
> > menuitems in the dialog "Script Editor"
are untranslatable.
> >
> > All these strings are not extracted to kspreads
message catalog, possibly
> > an error in the messages target?
>
Sorry, forgot to say I found this in branch.

> i18n("Script Manager") comes from
libs/kross/core/guimanager.* and there
> it's translated, or?

No, it is untranslatable in trunk, because there is no
string "Script Manager" 
in the message catalogs in trunk used by kspread.

> Re the both *.rc files; we have for sure the same prob
with all scripts
> (also those one the user is able to fetch via GHNS). I
am not sure such
> strings really belong to KSpread since e.g. the
CopyCenter-script is used
> within Kexi and KSpread. The scripts do not use any
translation-tech so
> far. Once in a while the idea was to use
PyQt's/QtRuby's tr/i18n for it,
> but that could be only done for scripts that use on of
them while there are
> scripts (like pilimport/pilexport in trunk) that don't.

But these scripts are shipped with kspread, and a german Joe
User would expect 
them to be translated.
Worst is, all menuitems with a shortcut in the dialog
"Script Editor" are 
partly translated, e.g. in file menu the item "New
Ctrl+N" ist translated 
to "New Strg+N", in the edit menu the item
"Redo Ctrl+Shift+Z" ist translated 
to "Redo Strg+Umschalt+Z"  etc. in a german locale
with recent kspread 1.6.
This looks really strange!

Burkhard Lück
_______________________________________________
koffice-devel mailing list
koffice-develkde.org
h
ttps://mail.kde.org/mailman/listinfo/koffice-devel

On Monday 23 October 2006 18:17, Burkhard Lück wrote:
> > i18n("Script Manager") comes from
libs/kross/core/guimanager.* and there
> > it's translated, or?
>
> No, it is untranslatable in trunk, because there is no
string "Script
> Manager" in the message catalogs in trunk used by
kspread.

uh, damn. You are right. It's actualy i18n("Scripts
Manager...") in lib/kross, 
so with an additional "s" :-/ ...
but in koffice1.6/kspread/plugins/scripting/scripting.cc
line #62 it's defined 
as
new KAction(i18n("Script Manager..."), ...

hmmm... so, beside the "Script" vs.
"Scripts" difference, the question is why 
the string isn't in the catalog?!

> > Re the both *.rc files; we have for sure the same
prob with all scripts
> > (also those one the user is able to fetch via
GHNS). I am not sure such
> > strings really belong to KSpread since e.g. the
CopyCenter-script is used
> > within Kexi and KSpread. The scripts do not use
any translation-tech so
> > far. Once in a while the idea was to use
PyQt's/QtRuby's tr/i18n for it,
> > but that could be only done for scripts that use
on of them while there
> > are scripts (like pilimport/pilexport in trunk)
that don't.
>
> But these scripts are shipped with kspread, and a
german Joe User would
> expect them to be translated.

y, true. So, solution - at least for the ScriptEditor -
would be then to use 
qt.tr(). Is it a good idea to change it now? I would like to
rewrite it 
anyway for trunk once PyKDE4 is out and then pykde.i18n()
could be used.

> Worst is, all menuitems with a shortcut in the dialog
"Script Editor" are
> partly translated, e.g. in file menu the item "New
Ctrl+N" ist translated
> to "New Strg+N", in the edit menu the item
"Redo Ctrl+Shift+Z" ist
> translated to "Redo Strg+Umschalt+Z"  etc. in
a german locale with recent
> kspread 1.6. This looks really strange!

I didn't know before that there exists a german translation
file for PyQt3 (it 
does not use KDE translations at all). Since I am not that
familar with 
translations at all; would you see here a high priority to
get the 
ScriptEditor-package translated? or would it be ok to try to
take care of it 
for KSpread2/KDE4?

-- 
Sebastian Sauer aka dipesh[sebsauer]
http://www.dipe.or
g/public_key.asc
Fingerprint: 8F1E 219B 16E6 4EC7 29CC F408 E193 65E2 9134
2221
Coder in http://www.koffice.org
&& http://www.kmldonkey.org
_______________________________________________
koffice-devel mailing list
koffice-develkde.org
h
ttps://mail.kde.org/mailman/listinfo/koffice-devel

it would be nicer to have a kross function for translation,
it would avoid to 
rely on PyQt or QtRuby. (just loading both of those beast
just for 
translation should be avoid)
-- 
--- Cyrille Berger ---
_______________________________________________
koffice-devel mailing list
koffice-develkde.org
h
ttps://mail.kde.org/mailman/listinfo/koffice-devel

Am Dienstag, 24. Oktober 2006 14:48 schrieb Sebastian Sauer:
> On Monday 23 October 2006 18:17, Burkhard Lück wrote:
> > > i18n("Script Manager") comes from
libs/kross/core/guimanager.* and
> > > there it's translated, or?
> >
> > No, it is untranslatable in trunk, because there
is no string "Script
> > Manager" in the message catalogs in trunk
used by kspread.
>
> uh, damn. You are right. It's actualy
i18n("Scripts Manager...") in
> lib/kross, so with an additional "s" :-/ ...
> but in
koffice1.6/kspread/plugins/scripting/scripting.cc line #62
it's
> defined as
> new KAction(i18n("Script Manager..."), ...
>
> hmmm... so, beside the "Script" vs.
"Scripts" difference, the question is
> why the string isn't in the catalog?!
>
I suppose in branch there is someting wrong in the messags
target in the 
Makefile, but I can not find out what :-(

> I didn't know before that there exists a german
translation file for PyQt3
> (it does not use KDE translations at all). 

I have no translation file for PyQt3 installed on my
computer, (AFAIK there 
isn't any), looks like this translation of the shortcuts is
pulled in via 
kdelibs.

> Since I am not that familar with 
> translations at all; would you see here a high priority
to get the
> ScriptEditor-package translated? or would it be ok to
try to take care of
> it for KSpread2/KDE4?

It is important to have all messages in the main menu
translatable, 
translation of the ScriptEditor package is a task for
KSpread2.
Before your mail I even did not realize that the dialogs
"Export to HTML File" 
and "Script Editor" are "just" some
python scripts.

Burkhard Lück
_______________________________________________
koffice-devel mailing list
koffice-develkde.org
h
ttps://mail.kde.org/mailman/listinfo/koffice-devel