Globalization translation in APEX

Hi All,
I must be doing something wrong.
I tried to follow the Apex user guide to do the translation, I encountered some problems.
1. After I Map, Seed, Translate, Export. I look at my XLF file, I found, NOT everything got translated, especially those TITLEs, REGIONs, ITEMs... that I defined in the application.
I had to do the Manual translation in order to get it all Translate.
2. In Attribute, I set Application Language Derived From to be Browser (use browser language preference), It does not take effect on all items that I manually translated., I had to set Application Primary Language to be the Language that I translated in order to take effect.
How should I make my translation take effect when I change the browser language option ?
Please help...
3. There are a lot of repeating TEXT that I defined thru out the appication, is there anyway to translate it globally ?
4. If I want to edit the XLF file, what is the proper way the edit that in order to have APEX accept.
Best Regards
--John

Hi Joel,
Let me phrase it a little better.
It seems the language my application displaying is base on the set up in "Application Primary Language",
I had a hard time to get it display base on the browser set up.
The browser set up will affect the APEX user interface, but not my application.
I want my application to act like APEX user interface, I don't know how can I do it.
or if it is reasonable thing to expect from APEX.
Regards
--John

Similar Messages

Globalization translation in APEX part II

Hi Joel and everyone.
Since we can build a GLOBAL multilingual with APEX.
What is the best way to handle CURRENCY ?
I have APPs translated into several different language. What I have trouble with is the CURRENCY.
If I use FML999G999G999G999G990D00 format mask.
APEX simply just change the the dollar sign into whatever currency sing for the different language, the value remain unchanged. And that will present the wrong data
Please help me some ideal of handling this currency issue
Best Regards
--John

Hello,
Yes, APEX will not convert currencies for you (and that would be an extremely risky thing to do, since how should Oracle decide what the most appropriate exchange rate was?).
There are a couple of solutions to this -
1) Just display in one currency but make it clear which currency it is (e.g. "$400 USD").
2) Maintain your own exchange rate ratios, perhaps in a table where you store the exchange rate relative to your 'base currency'. Then when the user selects a particular currency you simple factor your original base amount against the exchange rate, to produce your localised amount.
There are lots of webservices (and other methods) out there which will provide frequent exchange rates, so you could schedule a job to call the webservice at predefined intervals (say every 30 mins) to update your local exchange rate table with the latest values (if you wanted latest values).
Note in some cases large companies also have a 'fixed exchange rate' to protect against small hourly/daily/weekly exchange rate fluctuations (so this is even easier if it fits your requirements).
Hope this helps,
John.
http://jes.blogs.shellprompt.net
http://www.apex-evangelists.com

Globalization/translation: Importing application using a new application ID

We want to use the globalization feature of APEX and have created a translation from Dutch to English (application ID's 100 and '101'). This works fine. However, when the application 100 is exported and imported under a different application ID, the translated application ('101') is not imported. We need to import the application using a new ID because we have a development and test version of the same application within one database instance and application ID's have to be unique within one database.
Is there a solution for this problem, except having separate database instances for development and test versions of an application?
Thanks,
Patrick

Hello Patrick,
>> I tried what you suggested but that did not work.
Yes, and I’m sorry about that. That’s what happen when you try to answer from memory, without checking first.
>> <trans-unit id="S-2-101724717460540986-100">
>> The 100 at the end of the trans-unit id probably refers to application 100 and not to application 200.
The problem is not with the application id - that can be easily fixed. The real problem is with the internal components id (the large number) which has been changed. When I first answered you, I thought these would not be changed, as you are using the same workspace (which is indeed the case when you are importing the application into a new workspace, with the same ID number, but on a different APEX instance). However, as you are using the same (physical) workspace, and these IDs must be unique within this workspace, they must be changed upon installation. The result is a very different XLIFF file.
I don’t see an easy solution to this situation. It’s all depends on the complexity and size of your XLIFF file. If it’s relatively small and simple, you can just create a new one. If it’s a large file, it’s probably don’t worth the efforts.
Regards,
Arie.

Lost globalization translations on application change

I've made a change to my application, by a process of taking a copy of the application, and making the changes to it (all I did was an export/import, nothing clever). However, when I import the updated application back over the existing application ID, I find that the language translations no longer work.
The original application has translations for French, German and Spanish (I believe) but I have not done anything specific with them. My changes are explicitly defined as being English-only - the new fields and pages do not have to be translated.
I know nothing about language translations - that feature was part of the application before I took over support of it, and the fact that I have no knowledge is one of the reasons the new code is English-only.
Can anyone tell me what I might have done wrong, and how I should deploy my changes to preserve the existing translations? Once I have deployed the changes to this environment, I will need to further deploy them into production, from the (hopefully, now working!) test environment. A pointer to relevant documentation would help, although I have read the globalization chapters of the manual and they don't make much sense to me (I'm not sure how seeding translations figures in the case of a modification, and I've no idea how to deal with XLIFF files).
Thanks,
Paul.
PS This is HTML DB 1.6 :-( I'm hoping there are no major differences in this area...

Hello Paul,
>> I've made a change to my application, by a process of taking a copy of the application, and making the changes to it
By “taking a copy” I’m assuming you exported the original application, and then imported it under different ID. This is your basic mistake. As Scott pointed out, in order to maintain translations, you must import the application using the same ID.
>> when I import the updated application back over the existing application ID, I find that the language translations no longer work.
Your copy didn’t include any translation information in the first place, so importing it back, didn’t make any difference.
>> if the translations are separate applications
They are not exactly separate applications. You’ll not see the translated applications, and their application id, in the Application Builder application list.
>> what does that mean for my new pages?
As Scott mentioned in his post, if you are editing an existing pages, and don’t change any translated items, the changes will be reflected, in the primary language, in all the translated application.
However, if you are adding new pages, they will be available only in the primary language application. If a translated application will try to call them, you’ll receive an error message, similar to the one you encountered - Error ERR-1016 Application "103" Page "1" not found (requested language="fr") .
In order to fix that you’ll have to seed the primary language application and export the XLIFF file. As you are saying you don’t need to translate the new pages, just import back the XLIFF file – untouched – apply it and publish the translated application. The new pages, in the primary language, will be added to the translated application.
Hope this helps,
Arie.

Script for translating internal APEX messages now on the Wiki

Hi, <br>
<br>
APEX is translated to 10 languages. If you use another language you have to manually translate a number of standard texts. I have created a script for doing this on the Wiki.<br>
<br>
Regards Pete

Hello Pete,
Your script can be very useful, as the builder itself doesn't support copy of translatable strings form one application to another, and this script can make this tedious task more easy.
Users should take into consideration that some of the strings, like the WWV_FLOW_UTILITIES (pertaining to the date picker) would only work on version 3 and above.
Regards,
Arie.

3 questions about Translation in APEX

Hi all, i have 3 questions:
1- After export a XLIFF file, I must translate the data by hand?
2- whenever I add an item, I must return to export and to translate?
3- since I make reference to the application in another language that APEX generates?
I am from Argentina, sorry for my english.
Greetings!!

1. You need to translate by hand unless you have some tool that will do it for you.
2. If you add some translatable text, you need to re-seed (that populates the tables that handle translation) and then export again. If you have already imported your translations, when you export again you will see the translations. You can also just export translations for a specific page (if that makes sense for what you need), if you simply added a new item to a page.
3. Not sure what you mean by this one.
-- Sharon

Apex translation vs. export/import

Hello,
we had several problems with the translation in APEX, here is the newest one:
We applied a translation for an app, and then we exported and imported the app.
We tried to map, ..., publish the translation again. It was ok.
But when we change the language, nothing happens.
Every label remains the same.
I think it is because every id in the export file has changed.
Why the ids change??
What should we do now? Should we make the translation again? (cca. 50.000 items).
Any help would be appreciated!
(Apex version 4.0)
Thanks in advance!

Hello (please tell us your first name),
>> We applied a translation for an app, and then we exported and imported the app.
We tried to map, ..., publish the translation again.
Are you talking about deploying the application into a second development instance, or into production?
First, you shouldremember that you must not change the application ID of the translated application.
Secondly, if you are deploying into a production instance, you need to export both the primary language application and the translated one (this is the only case where you are actually treat the translated application as an independent unit). On the production instance, first import the primary language application and then the translated one.
You only need to re-map, re-apply and re-publish the translated application (using the XLIFF file) if you are going to use the Application Builder to make some changes into your application in the new instance. In this case, and to retain the viability of the XLIFF file, you must use the original translated application ID (as I mentioned before).
>> But when we change the language, nothing happens.
Assuming you installed the translated application correctly (i.e. used its original application ID) the APEX engine derived the application language based on the Application Language Derived From field (Shared Components ==> Edit Globalization Attributes).
If you suspect the problem might emanate from this parameter, please give us more details regarding your settings.
Regards,
Arie.
&diams; Please remember to mark appropriate posts as correct/helpful. For the long run, it will benefit us all.
&diams; Author of Oracle Application Express 3.2 – The Essentials and More

Javascript error in orginal application but not in translated one

Hi,
We export / import our application from dev to test server. Our problem is that we got a javascript error saying : $ is not defined - in firebug.
What I don't understand is that our translated application works perfectly!
Any idea what could cause that error?
Thanks

Hello,
>> Our problem is that we got a javascript error saying : $ is not defined
This type of error usually means that the application doesn’t have access to the APEX provided JavaScript library. First, you should check if the alias for the images directory is defined the same on your dev and test instance.
>> What I don't understand is that our translated application works perfectly
A translated application can have its own alias to an images directory. Are you using this option? (go to shared components, Globalization, translate application and choose the first option of mapping your primary language. In the mapping wizard screen you have a field called Image Directory).
Regards,
Arie.
&diams; Please remember to mark appropriate posts as correct/helpful. For the long run, it will benefit us all.
&diams; Forthcoming book about APEX: Oracle Application Express 3.2 – The Essentials and More

Apex 3.0 in spanish

Hello team,
i was working with the Apex 3.0 sandbox and i was looking at the spanish translation of certain on-line help items, in search of inspiration as i am checking out a translation for one of my sites.
I find the spanish translation of Apex very good in general, as far as my mexican spanish goes, and even too "accurate" in the case of the following page item:
p_item_id=22210144053.4001
page 4316 of application 4000, "Expresión de Validación 1".
The translator translated even the PL/SQL code :-)
For instance, example number 3:
v('ITEM_1') no es nulo
should have been left
v('ITEM_1') is not null
and further on with example 4:
(v('ITEM_1') no es nulo y v('ITEM_2') es nulo) o bien
(v('ITEM_1') es nulo y v('ITEM_2') no es nulo)
Esta validación garantiza que sólo un elemento (ITEM_1, ITEM_2) tiene un valor.
from the original:
(v('ITEM_1') is not null and v('ITEM_2') is null) or
(v('ITEM_1') is null and v('ITEM_2') is not null)
I didn't check if this applies to other translations too.
Bye,
Flavio
Byte64's Annals of Oracle Improbable Errors
http://oraclequirks.blogspot.com

Flavio,
If I get your point you are referring to item help text that happens to contain an example in PL/SQL and the translator translated some of the PL/SQL into Spanish when it should have been left alone. Thanks for pointing that out.
Scott

Intaractive report translation

Hi,
Do somebody know how to translate name of options in Action Menu? I know how to translate most of elements in aplication using 'Shered components ->Globalization-->Translate Application'.
But there are some elements which are untranslatable .
Let's say that Action Menu got options like: Highlight column , save report and ..., but I want to atchieve instead 'Highlight column' --->'Coloured column'.
Do somebody know how to do it the most simple way?
Thx

Nobody is here around :) but
Let say ... we've got procedure which create interactive report
Can I use some string from here to substitute to another string?
wwv_flow_api.create_worksheet(
p_id => 2345718981013634+wwv_flow_api.g_id_offset,
p_flow_id=> wwv_flow.g_flow_id,
p_page_id => 4,
p_region_id => 2345603187013634+wwv_flow_api.g_id_offset,
p_name => 'Shopping Cart',
p_folder_id => null,
p_alias => '',
p_report_id_item => '',
p_max_row_count => '10000',
p_max_row_count_message => 'This query returns more than 10,000 rows, please filter your data to ensure complete results.',
p_no_data_found_message => 'No data found.',
p_max_rows_per_page => '',
p_search_button_label => '',
p_page_items_to_submit => '',
p_sort_asc_image => '',
p_sort_asc_image_attr => '',
p_sort_desc_image => '',
p_sort_desc_image_attr => '',
p_sql_query => a1,
p_status =>'AVAILABLE_FOR_OWNER',
p_allow_report_saving =>'Y',
p_allow_report_categories =>'N',
p_show_nulls_as =>'-',
p_pagination_type =>'ROWS_X_TO_Y',
p_pagination_display_pos =>'BOTTOM_RIGHT',
p_show_finder_drop_down =>'Y',
p_show_display_row_count =>'Y',
p_show_search_bar =>'Y',
p_show_search_textbox =>'Y',
p_show_actions_menu =>'Y',
p_report_list_mode =>'TABS',
p_show_detail_link =>'N',
p_show_select_columns =>'Y',
p_show_filter =>'Y',
p_show_sort =>'Y',
p_show_control_break =>'Y',
p_show_highlight =>'Y',
p_show_computation =>'Y',
p_show_aggregate =>'Y',
p_show_chart =>'Y',
p_show_calendar =>'N',
p_show_flashback =>'Y',
p_show_reset =>'Y',
p_show_download =>'Y',
p_show_help =>'Y',
p_download_formats =>'CSV',
p_allow_exclude_null_values =>'N',
p_allow_hide_extra_columns =>'N',
p_owner =>'ADMIN');
end;

List manager translation

Hello all,
I have a small but annoying problem.
I have to review an application that has been developed in german and should be rendered in both german and english.
So the previous developper has defined the application texts in german and has defined a translated application in english.
The problem is : there is a List Manager in a page that contains two buttons (Add / Remove). They are still defined with english text in the main application (german) and I cannot find any properties to change this.
The list manager also opens a popup with two other buttons. And the problem is the same.
Do you any other solution than renaming every elements from the main application in english and then translate it in german?
I guess I can use a dynamic action to redefine the two visible buttons text. But it will not solve the problem for the popup buttons
Any Idea?
Thank you very much.
Max

Arie Geller is an expert on this, and if I recall there is a pertinent chapter in this book regarding globalization & translation.
http://www.packtpub.com/oracle-application-express-3-2/book
But no doubt there are a few blog posts on this topic - look for keywords found under Shared Components -> Translate Application
Scott
blog: [url grassroots-oracle.com]grassroots-oracle.com
twitter: [url twitter.com/swesley_perth]@swesley_perth
-- please mark any useful posts as helpful or correct, in the end it helps us all

Translate Application for arab users

hey all,
I have an application i want to make the arabic version from the application for the users,i created a copy of the application now i want to rename the items (pages,regions,buttons,etc) to arabic in proper way and to change the direction of the items from right to left for arabic users...
Regards ,
Ahmed

Hi Ahmed,
Did you already have a look in the Shared Components section - Globalization - Translate Application?
The steps to follow;
1. Map your primary language application to a translated application
2. Seed and export the translation text of your application into a translation file.
3. ranslate text identified in translation file.
4. Apply your translation file and publish
5. Optionally translate messages which are used by PL/SQL procedures and functions.
6. Optionally identify any data that needs to be dynamically translated to support SQL based lists of values.
Or have a look in the doc: http://download.oracle.com/docs/cd/B28359_01/appdev.111/b32258/global.htm
I never tried to translate into a language with a reading direction of right to left... interesting!
Dimitri
-- http://dgielis.blogspot.com

Change language of the IR "toolbar"

How/where do we change the language for the options in the toolbar of Interactive Reports (the search tool's Go button, plus the drop down list of options such as Select Columns and etc). These items don't show up in the translatable list of items in the Translation area. Is there somewhere else I have to look? (APEX 3.1).

This documentation contains all the IR messages to be translated: http://apex.oracle.com/i/doc/global_mess_reports.htm#BABEADAJ
For example, you mentioned the 'Select Colums' text... it is associated to the APEXIR_SELECT_COLUMNS message. Just go to your app's Shared Components > Text Messages (Under Globalization) and create a new Message. In 'Name', enter APEXIR_SELECT_COLUMNS, the choose the appropriate language you want to translate it to, and then enter the translated message in the 'Text' field.
Best regards,
Mathieu

Problem with accentuated characters in XLIFF file (no problem anymore)

Sorry, the following turned out to be a non-problem. XLIFF editor understands accentuated characters in the translation file very well :o)
I am trying to translate an APEX v 2.2 application from french to german.
Generated xlf file header reads:
<file original="f101_102_fr-ch_de.xlf" source-language="fr-ch" target-language="de" datatype="html">
All french diacritical characters in the file are replaced by something like Ã©. Something similar happens when one exports CSV file to Excel with Automatic CSV Encoding set to "No".
Application main language can be swiss french (fr-ch) or french french (fr), with the same result.
Application Language Derived From is "Use application primary language"
Automatic CSV Encoding is set to "Yes".
Is there a possibility to export non-english characters correctly?
Thank you.
Message was edited by: kortchnoi
kortchnoi

Well... In a way, it was my fault. I have created xliff file and looked at its contents using CodeWright text editor. Using CW's regular expressions and macros, one could process translation fairly easily.
However, in this file foreign characters are scrambled (=> my post).
Then, I decided to install and try XLIFF editor. The one recomended by SUN handled all diacritical characters nicely.
So, as long as I don't try to proceed to direct translation of the xlf file, but through XLIFFF editor, I don't have to worry about french and german accents. At least, I hope so (I still have to import the german translation to be sure).
Igor
Message was edited by: I. Kortchnoi
kortchnoi

Problem with Umlauts

Hi All,
For our customer we managed a german application inside APEX, unfortunately we have some problems with showing the umlauts in the application.
By showing a interactive report the umlauts in the data and in the column names are shown correct. But when I pressed the green wheel I saw ZurÃ¼cksetzen instead of zurucksetzen.
This problem also occured by logging into the application with a wrong password (UngÃ¼ltige ID-Daten fÃ¼r die Anmeldung) instead of Ungeltige ID Daten fur die anmeldung.
By the installation of APEX we run also the LOAD_DE.SQL script to translate the apex version. Before we run this script we set the language to german_Germany.AL32UTF8.
When I look into the HTTP server in the dads.conf file I saw the follow row: PlsqlNLSLanguage German_Germany.AL32UTF8
It seems that the problem is inside APEX instead of the application inside the APEX version (because the application shows the data correct). Is there a way to see which names are stored in the databse (to make sure that the data is stored correctly)?
Has anybody an idea how to fix this problem?
We have an Oracle 11G Database with apex version 3.2 and an HTTP Server.

I find a solution for this problem.
Below the steps we did to fix this issue
I first checked the dads.conf, if you’re weblogic is correctly configured.
Yes it was!
Then I checked, if the database is able to save Umlaute
Yes it was!
Then I checked, if the database stores the Umlaute for Apex
No it doesn't
That means, that the import (load_de) was unsuccessfull.
Then I checked the import files, which were saved on the server
Everything seems to be correct.
Then I checked other NLS related settings and found that ORA_NLS10 was set.
Although we need this setting for some reasons, it “destroyed” our load_de.sql.
Finally I unset this setting, and load the data again and now it worked.

Globalization translation in APEX

Similar Messages

Maybe you are looking for