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 

 Moderated by: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius
New Topic Reply Printer Friendly
New context generation feature in XML engine - Wish list for software localization tool - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Wed Jul 16th, 2008 09:33 am
PM Private Upload Quote Reply
renepape
Member
 

Joined: Tue Aug 21st, 2007
Location: Denmark
Posts: 19
Status: 
Offline
Hi.
I'm translating SQL Reporting Services reports, and these .rdl files are XML files with a certain structure. Everything is fine until you rearrange the report (using the designer), since there is no way of adding a context attribute to the nodes where the actual value to translate is stored.

Today, I get a context like:
"Report.Body.ReportItems.Rectangle.ReportItems.Rectangle.ReportItems.Textbox.Value" repeatedly within one report where only "value" within "textbox" are translated.

Most nodes (except value!) has a "name=" attribute, and I tried adding that as a context specifier with no luck - i guess becaurse  these aren't translatable. Then, I would like an option to include all context-specified attributes of a path in the context, such that is instead would look like:
"Report.Body.ReportItems.Rectangle.RctMain.ReportItems.Rectangle.RctAMHeader.ReportItems.Textbox.textbox21.Value"
where RctMain was the name attribute of the Rectangle node and so on.

Now I've suddenly got a unique context for free :-)

Feel free to invent other context-notations of the concept.

- anxiously awaiting  your comments
René

Back To Top PM Private Upload Quote Reply

 Posted: Wed Jul 16th, 2008 09:44 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3128
Status: 
Offline
Hi René,

can you please send a .rdl sample file to support (at) sisulizer.fi. We will take a look.

Best

Markus



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

 Posted: Thu Jul 17th, 2008 08:30 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3128
Status: 
Offline
Hi René,

we got your files. Have you tried to right click the nodes and make the "name"-attributes part of the context?

Markus


Attachment: 0060.jpg (Downloaded 23 times)



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

 Posted: Thu Jul 17th, 2008 10:56 am
PM Private Upload Quote Reply
renepape
Member
 

Joined: Tue Aug 21st, 2007
Location: Denmark
Posts: 19
Status: 
Offline
Thanks a lot for your guidance. I had totally missed out the fact that right-clicking attribute nodes gave me the opportunity to include the value in the context.

This was exactly what I looked for!

I am constantly astonished by the features and support of Sisulizer. I've been internationalizing software since Multilizer 3 was state of the art, but no other product has yet given me the daily efficiency, quality and support like Sisulizer does.

Also, the customers doing translations using the translator version really like the product and doesn't bomb me with support questions.

- Rene

Back To Top PM Private Upload Quote Reply

 Posted: Thu Jul 17th, 2008 11:18 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3128
Status: 
Offline
Thanks René,

the whole Sisulizer team really loves to get such positive feedback.

And we have to return this tribute to you, our loyal customers. Your feedback in this forum pushes the product in the right direction. Together we make Sisulizer the best localization experience.

You might have seen the new bug reporting feature in V2008. We really want to know if you have any problems at work. It is part of our V2008 quality offensive.

Markus



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

 Posted: Mon Jul 21st, 2008 04:16 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3826
Status: 
Offline
You might have seen the new bug reporting feature in V2008. We really want to know if you have any problems at work. It is part of our V2008 quality offensive.
New bug report feature is very good I think. It seems to me that it is powerful and important feature, and should be pointed in Version history document. Markus, what do you think about it?

Best,

Janusz



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

 Posted: Mon Jul 21st, 2008 04:21 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3128
Status: 
Offline
Yes,

you are right. The history.txt could be more complete. Btw: it made it's way to http://www.sisulizer.com/what-is-new.shtml

Markus



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

Current time is 10:53 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > New context generation feature in XML engine



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

Impress - Privacy statement

Sisulizer software localization tool - Three simple steps to localize