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: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius
New Topic Reply Printer Friendly
Can't compile... - 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: Fri Aug 27th, 2010 08:13 am
PM Private Upload Quote Reply
bikedude
Member
 

Joined: Thu Aug 20th, 2009
Location:  
Posts: 79
Status: 
Offline
Building "L:\Flamingo\Main\bin\nb-NO\Mikromarc.Windows.Components.resources.dll", the Norwegian, Bokmål (Norway) version of "L:\Flamingo\Main\src\Windows\Components\Components.csproj"
Could not compile the resource file: L:\Flamingo\Main\src\Windows\Components\mmCatalogueSearchSpec.nb-NO.resx


The error output that follows is ""L:\Flamingo\Main\src\Windows\Components\mmCatalogueSearchSpec.nb-NO.resources" resource file does not exist. Can't create the satellite assembly".

How should I diagnose this?

(we're using build 307)

Back To Top PM Private Upload Quote Reply

 Posted: Fri Aug 27th, 2010 09:06 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


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

307 needs ...nb-NO.resources" as a sort of a template.
Please make sure that the file can be found in the given path before your start the build process in Sisulizer. The result is better matching satellite in terms of the .NET framework needed by the file.
This was changed in 307. In 308 the "template" will be used if it exists to get the best result. If not it will be created with default parameters.

At least this is how I understood R&D.

Hope this helps

Markus



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

 Posted: Fri Aug 27th, 2010 09:10 am
PM Private Upload Quote Reply
bikedude
Member
 

Joined: Thu Aug 20th, 2009
Location:  
Posts: 79
Status: 
Offline
Ah, I noticed the other thread, but didn't think the error messages were that similar.

As the poster in the other thread indicated, surely the localized resource file is Sisulizer's domain? We use Sisulizer to output such files... The current approach feels a bit cannibalistic. :P

I guess I'll just have to wait for 308 (or 309 as previously indicated).

Back To Top PM Private Upload Quote Reply

 Posted: Fri Aug 27th, 2010 09:27 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2115
Status: 
Offline
You are right it is 309 and we hope we have it middle of next week.

The devil is in the details. What is good in one situation might be bad in some other. There is not one place in a .NET project where all needed info are together. Sisulizer has to collect them to make a proper output.

Markus



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

Current time is 08:39 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Can't compile...



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