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
ResXFileRef resx types removed by sisulizer - 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 Jul 17th, 2017 03:33 pm
PM Private Upload Quote Reply
timbrown
Member
 

Joined: Mon Feb 27th, 2017
Location: United Kingdom
Posts: 14
Status: 
Offline
We have the following resource manually inputed into a localised resx file.

<assembly alias="System.Windows.Forms" name="System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
<data name="GeneratingDocument" type="System.Resources.ResXFileRef, System.Windows.Forms">
<value>..\Resources.fr\generatingDocument.pdf;System.Byte[], mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
</data>

When the project is built it is removed by sisuilizer. Is there any way to stop sisulizer removing it or to insert these types through the sisulizer UI

Many Thanks

Back To Top PM Private Upload Quote Reply

 Posted: Mon Jul 17th, 2017 03:47 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2962
Status: 
Offline
Hi Tim,

Since Sisulizer takes your original as a blue print to create your localized files it will not look into changes you make to localized files outside of the workflow. Sisulizer simply sees it as its job to create all localized files from the information stored in the project file. The workflow is always
  • one original source scanned by Sisulizer
  • all localizations inside the project
  • Sisulizer creates all localized files for you
If you want to change localized files everytime you have to do it after Sisulizer created all files, e.g. in a batch file using SLMake. This way you'll never forget that.

Hope this helps
Markus



 



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

 Posted: Mon Jul 17th, 2017 03:49 pm
PM Private Upload Quote Reply
timbrown
Member
 

Joined: Mon Feb 27th, 2017
Location: United Kingdom
Posts: 14
Status: 
Offline
Many thanks for your reply - Is there any way to to insert these types through the sisulizer UI i.e the ResXFileRef type/

Back To Top PM Private Upload Quote Reply

 Posted: Mon Jul 17th, 2017 04:15 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2962
Status: 
Offline
Hi,

Have you checked Project - Edit Source - <your source> - Resources. Is your resource type shown? If it is shown but not checked, please check it and then do a Project - Scan for Changes to include it into the project.

If not, please create a simple sample and I forward it to R&D to check if it can be supported in future builds.

Markus



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

Current time is 12:49 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > ResXFileRef resx types removed by sisulizer



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