language

[stevew]

thank you for the comments.

i think i sitll need to know how i might set the charset and text from script for MessageBox. For example,

MessageBox: $TITLE$ Setup Error, This product requires at least Administrator Priviledges.$NEWLINE$$NEWLINE$Setup cannot continue.


For importing the language information remotely, i do not see how to do this. I see these automation commands:

miaAddDialogFile
miaAddSupportFile
miaAddMergeFile
miaAddPatchFile
miaAddIncludeFile

but i do not see how to invoke the import wizard.

[sinan]

A MessageBox is a system window and I am not sure how you can change the charset for that (or if that is even applicable). The standard MessageBox Win32 API is called.

You can send your remote translation office the following items:

1) The Dialog Batch Updater tool to automatically change charsets on all dialogs with a single click.
2) The miabuild.exe tool to remotely build the setup from the command line.
3) The runtime files required by the automation interface so miabuild works remotely - see the help for a full list of these files (they are typically located at <IA Folder>\\automation\\libraries, subfolders are required)
4) Your setup project
5) Your setup files

[stevew]

thank you for your help. i'm sorry to ask so many questions which may be all mixed up.

Can you clarify that i may not import the translated text with any remote tools? This needs to be done by me before rebuilding the project?

[sinan]

I am not sure what you are asking here...if you want to locally import remote translations you can do that easily.

[stevew]

okay, for a bit of details. I would like to create a setup project in english. Then send the project to a Russian or Greek customer. I would like them to enter the translation text, import the text, and rebuild the project without contacting me; or sending me the import text and asking me to verify, import, and rebuild.

[stevew]

boing! the lights have finally come on for me.

I see your help file explanation for Passing Variables To and From Dialogs and Scripts. This is what i was missing.

Also, upon further reflection I will use your language translator mechanism as it was intended and I will import the translated text to my project.

Now i will just see if I can replace the MessageBox with actual Dialogs. The reason is that I have found that most people of other languages still install English Windows then complain if the MessageBox captions don't match the application language.

[sinan]

Ah, great there is some progress!

About redoing MessageBox'es. Easy - just create a custom dialog. Add three icons to it, set to show if a hidden label on the dialog is set to true. Add a text field and some buttons, the text field can directly reference a variable (say $MESSAGETEXT$) and the buttons can again be conditionalized to display only when their associated hidden labels are set to true (to allow OK/Cancel/Abort/Retry/Ignore/Yes/No functionality, but this may already be overkill).

Then create a new include script which calls this dialog and returns a result. In your main script you can just initialize variables and then call the include script to show the custom message box with exactly your own charset, etc

Hope the above is clear...let me know if you need more help.

[stevew]

thanks. your tip was helpful for me. i opted for 4 individually tailored dialogs for now. the only way i could find to rename my dialogs was from the dialog editor "save as" option. but that is fine, and i have now created my custom dialogs and am generating my project script via the automation API. Very slick and powerful tool you have built!
... and i don't mind the slightly slower install since the built exe is sooo tiny ... awesome! i am so proud of myself for finding your software.

[sinan]

Thanks for your enthusiasm Spread the word and help others find InstallAware!