Bug 138418

Summary: Typo? Scripts or Script Manager in KSpread doc
Product: [Applications] calligrasheets Reporter: Natalie <nat>
Component: generalAssignee: Calligra Sheets (KSpread) Bugs <calligra-sheets-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: mail, mkruisselbrink
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Natalie 2006-12-05 23:27:40 UTC 
Version:            (using KDE KDE 3.5.2)
OS:                Linux

KSpread

  - commands.docbook:1016
  <guimenuitem>Script Manager...</guimenuitem>

  and
  - commands.docbook:1020
  <guilabel>Scripts Manager</guilabel> dialog

  One with and one without "s"?
Comment 1 Burkhard Lück 2006-12-05 23:52:45 UTC 
Natalie wrote:
>One with and one without "s"? 
 
Yes.

"Script Manager..." ist the string in the menu

"Scripts Manager" is the label of the dialog

So close this bug or assign it to the kspread developers.

By the way, did you realize, that the guimenuitem "Script Manager..." and the items "Export to HTML File..." and "Script Editor" in the submenu "Scripts" are not translatable?
And even worse, the menu items in the dialog "Script Editor" are also not translatable, but have translated shortcuts. A menuitem like "Undo CTRL+Z" looks really strange!
Comment 2 Rich Johnson 2007-07-28 21:13:58 UTC 
Reassigning to KSpread developers.

KSpread developers,

If you find this a bug/issue and fix this, could you please either update the documentation correctly, or mark that you have fixed it on your end and then reassign it back to kde-doc-english@kde.org and one of us and can fix the documentation for you. Thank you.
Comment 3 Sebastian Sauer 2007-09-02 21:46:25 UTC 
imho it's not a "big issue" and fixed in trunk already (there it's called "Script Manager" like at amarok too). So, question is, if it makes sense to fix it in 3.5.x aka if it's worth the probably additional translation-work?!
Comment 4 Marijn Kruisselbrink 2009-01-14 22:08:58 UTC 
closing, since this bug is old, and apparently fixed.