XTra4o – Release 0.9.2 and Help

Last week we made our XLIFF-Translator for Oracle available to the public.

Based on the feedback we already received, we made some changes to the utility. See the About-tab in the application.

We also use this tool to try out some typical-issues-you-need in-every-application.

In XTra4o we implemented two different ways to provide Help to the user.

For every step we provide a visual-aid explaining where you are in the translation process.

For ‘experienced’ users it is possible to disable this help via the User Preferences.

A second way to provide Help is an on-demand approach with context-sensitive help. Clicking on the Help menu will open a dragable window, showing information of the current page.

This help text is fetched from a table which makes it possible to build a simple Apex screen on this table. Now a non-technical person can write the help text instead of a developer, which is always better …

Don’t hesitate to give it a try and provide us some feedback !


2 thoughts on “

  1. I have a development and production environment. I keep the database models in sync. When I make a change to the app, I first do it in dev then migrate through export/import to production. Now here’s my issue. In dev, I have created a second language (fr-ca) and had translations done. However, when I do an export/import to the production environment (which is a different app_id), it does not recognize the second language nor the fact that the application has even been translated. Does this mean I have to create another translation file and go through the entire process again each and every time I migrate changes to production from my development environment? This is a serious amount of work given the size of the application and the number of translations which would need to be done. Is there any way to automate the translation of the production environment (ie through the backdoor tables) using the translations which have already been done in the development environment or can I somehow export the french application from dev? Not everyone wants their production environment to also be their development environment.

  2. This is indeed a problem when you have different app_id’s in dev and production. See our blog Deploy Your Multilingual application in a production environment. and second comment on that.I don’t know if there exists within apex already a workaround for this !I am afraid that you have to redo your translation work for the production environment.This is one of the reasons we started to build our Xtra4o utility; and especially the dictionary concept. I once had the same problem. I decided to put all translations of the imported xliff-from developemnt into the Xtra4O-dictionary. Afterwards I loaded the XLIFF from production with the other app-id and applied the dictionary to that file. So we could rather quick recuperate the previous translation work.For future multi-lingual applications we will always verify the application-ids in dev and production to try to hold them in sync … I know this is not always possible; for cases where this is not possible we know that the dictionary concept of Xtra4o can help to work around the problem!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

About Jan Huyzentruyt