Support forum of the software localization tool Sisulizer


.NET, Delphi, ... - Sisulizer Localization Tool Support Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.
Search     Help Home Sisulizer Website Download
Search by username
Not logged in - Login | Register 
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Delphi Project - submenu's

 Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius
New Topic Reply Printer Friendly
Delphi Project - submenu's - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Mon Jun 21st, 2010 10:56 am
PM Private Upload Quote Reply
GertRijs
Member
 

Joined: Mon May 12th, 2008
Location: Netherlands
Posts: 53
Status: 
Offline
 In a delphi project, sub-sub menus aren't translatable with the menu-editor. You need to click the form itself to be able to translate sub-menu's.

See attached picture.

Gert

Attachment: menu.png (Downloaded 32 times)
Back To Top PM Private Upload Quote Reply

 Posted: Wed Jun 23rd, 2010 04:46 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 2542
Status: 
Offline
 Hello Gert,

I tested this issue with my sample project for Delphi and:
    all items (also items from invisible sub-menus) are available in Translation Sheet.I can see sub-menus by browsing in Visual Editor (like in real application), that is, after clicking on appropriated item (with arrow symbol) in main menu, Sisulizer automatically opens selected sub-menu in Visual Editor
Could you upload to us your project? I'll check with your SLP file.

Best regards,
Janusz



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Wed Jun 23rd, 2010 05:05 pm
PM Private Upload Quote Reply
GertRijs
Member
 

Joined: Mon May 12th, 2008
Location: Netherlands
Posts: 53
Status: 
Offline
 uploaded
Back To Top PM Private Upload Quote Reply

 Posted: Wed Jun 23rd, 2010 05:45 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 2542
Status: 
Offline
 Hello Gert,

You are right, these items are unavailable in Menu editor. I found your menu items in form  belong to "ActionList1" instead to "MainMenu1" and it could be reason of odd Menu Editor's behavior. Could you check code of this form in your source file?

Best regards,
Janusz



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Thu Jun 24th, 2010 11:20 am
PM Private Upload Quote Reply
GertRijs
Member
 

Joined: Mon May 12th, 2008
Location: Netherlands
Posts: 53
Status: 
Offline
 I will ask the dev to see.
Back To Top PM Private Upload Quote Reply

 Posted: Fri Jun 25th, 2010 07:05 am
PM Private Upload Quote Reply
GertRijs
Member
 

Joined: Mon May 12th, 2008
Location: Netherlands
Posts: 53
Status: 
Offline
 This is what he had to say:
I think I got it. MainMenu1 contains *only* items that are not connected
to the action. Actions, on the other hand, which are listed under
TfrmRCCMain node, have other captions. This is not just a "good
practice" for developers, but also it's easier for translators. When you
translate an *action* all linked menu items and toolbuttons are also
translated.

So it's not really a bug in Sisulizer, but it could be a nice feature if
they add a separate node for TActionList components, like they did for
menus.

> Remember a strange bug we had some time ago: pressing the help menu exits the program?
> See the screenshot, the help-menu shows "Exit2" in its context (MainMenu1.Exit2.Caption)

Yeah, control name remained without me noticing... Hm... I don't know
how sisulizer works, but I guess when I fix this it will need to be
translated again? I suppose that control name is used as identifier?
I am not a Delphi developer, so I only understand half of it above. But I think the fact remains: I can select the "check for updates" submenu, so clearly Sisu is not confused there. I should be able to edit the submenu as well.

Thanks.
(btw, Janusz, I sent you a PM)
Back To Top PM Private Upload Quote Reply

 Posted: Sat Jun 26th, 2010 09:35 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 2542
Status: 
Offline
 If your developers change code of in this form, it can cause new items in Sisulizer's project, but these items should be translated automatically (Translate Duplicate feature), unless you  change also original strings.

(btw, Janusz, I sent you a PM)
I replied you via email.

Have a nice weekend,
Janusz



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

Current time is 08:24 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Delphi Project - submenu's



WowUltra modified by Sisulizer Copyright © 2007-09 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Sisulizer software localization tool - Three simple steps to localize