[DUG] Internationalisation

[Paul Hectors]

Hi Tony,

I can only speak of what we have done at PowerShield which is in Delphi 2007.
We use ModelMaker plugin which has a feature that allows for scanning of string literals, you can then set whether they are a resource string or not.
Once the source code has the resource strings defined we use SisUlizer to manage and build the localised executables. Because we are using Delphi 2007 there was not much choice in our method.
SisUlizer has it quirks so you would have to evaluate and see whether it works in your scenario or not.

I would imagine life should be a lot easier in a Unicode version of Delphi.

Best regards,

Paul

-----Original Message-----
From: delphi-bounces at listserver.123.net.nz [mailto:delphi-bounces at listserver.123.net.nz] On Behalf Of Tony Blomfield
Sent: Tuesday, 31 March 2015 6:32 a.m.
To: 'NZ Borland Developers Group - Delphi List'
Subject: [DUG] Internationalisation

HI.

I'd appreciate any comment about Internationalisation for Delphi Windows applications please.

We have a number of applications in XE2 and coming up XE7 that I need to internationalise for Greater China, and a number of  .

I have tried using the Resource Wizard, and ETM, but found it difficult to learn, and has many show stopper bugs. Basically this stuff was written for Delphi 5 - 20 years ago and has never been maintained (Like so much of Delphi).

I am also looking at using dxGetText and PO Edit. Unfortunately dxGetText also looks to have very little in the way of support. We are not averse to purchasing a tool as long as it works well and is supported.

I would appreciate some guidance from someone with success in this area.

Thanks very much in advance.

Tony


_______________________________________________
NZ Borland Developers Group - Delphi mailing list
Post: delphi at listserver.123.net.nz
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to delphi-request at listserver.123.net.nz with Subject: unsubscribe