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
Delphi developers: Please vote for Sisulizer - Offers, Announcements and FAQs - Public information from the Sisulizer team - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Wed Feb 22nd, 2012 07:06 pm
PM Private Upload Quote Reply
Renate.Reinartz
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 56
Status: 
Offline
Please follow the link, and vote for your favorite string localization tool for Delphi:

http://delphitools.info/2012/02/15/what-do-you-use-for-string-localization-in-delphi/

So far GNU gettext is leading, and Sisulizer is second. Besides the fact, that I know that some of you use both, it would be nice to vote for Sisulizer.

If you need more infos about how to localize GNU gettext PO/POT file, you may also want to check our localization blog at http://www.the-localization-tool.com.

Thanx,
Renate



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

 Posted: Wed Mar 28th, 2012 10:00 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3844
Status: 
Offline
Renate.Reinartz wrote: So far GNU gettext is leading, and Sisulizer is second. Besides the fact, that I know that some of you use both, it would be nice to vote for Sisulizer.

If you need more infos about how to localize GNU gettext PO/POT file, you may also want to check our localization blog at http://www.the-localization-tool.com.

In build 330 improved Gettext support:
  • Added support for partially translated PO/POT files. So now you can add as source (to Sisulizer project) also fully or partially translated PO/POT files. It helps switching to Sisulizer, or translating PO/POT files generated by other Gettext tools used by your developers.
  • Since build 330 you can decide what Sisulizer should to do with not translated items during build output PO file. Before, Sisulizer always saved originals to output Po file for not translated items. Now you can select following options "All" (Sisulizer works like before build 330), "Translated" (not translated items have empty translation items in output file), "Different" (in this case Sisulizer saves to output file only translations different from originals). This feature is useful when your developer/employer use third party Gettext tools, in SVN solution, etc.
Both those feature significantly improve compatibility with third party tools e.g. POEdit and now Gettext support in Sisulizer is "tool independent".

Best regards,
Janusz



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

Current time is 12:02 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Public information from the Sisulizer team > Offers, Announcements and FAQs > Delphi developers: Please vote for Sisulizer



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