Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Hyland Connect
- Enterprise Platforms
- Alfresco
- Alfresco Archive
- OpenWorkdesk in YOUR custom language
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
OpenWorkdesk in YOUR custom language
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2010 08:17 AM
At the moment, OpenWorkdesk (OWD) Community Edition comes in three languages:
- English
- German
- Romanian
[img]http://openworkdesk.org/img/languages.JPG[/img]
The language can be changed by clicking the desired language in the upper right corner of the OWD login screen. For translating OWD, OWD development team introduced keys for every OWD String output, which are listed together with their respective "language" value in a properties file (e.g. oecmlocalize_en.properties for the english language). Those properties files can be found in the oecmlocalize_3000.jar file in the WEB-INFlib folder of your OWD Community Edition deployment.
The selectable languages on the login screen are configurable by editing following lines in the WEB-INFconfcmisowbootstrap.xml file of your deployment:
There are two ways to translate OWD Community Edition to YOUR language
Method 1:
Open an existing properties file from the oecmlocalize_3000.jar file, translate every key value to your language, rename the properties file (e.g. to oecmlocalize_ex.properties) and save it to the jar file. Add the new language to the code shown above in owbootstrap.xml like in following example:
You can even add a flag symbol for your language to the designdefault20imageslang folder of your deployment. In the code example the image was specified to be named ex.gif. After a server restart, you should now be able to choose your language from the OWD login screen.
Method 2:
Create a new properties file (e.g. oecmlocalize_ex.properties) and enter OWD´s keys with your respective language value. The keys for the output strings are shwon in so called debug mode. To enable debug mode, uncomment the debug mode part like in the following lines of owbootstrap.xml:
Change language to Debug Mode from OWD´s login screen and you will see the original keys instead of OWD´s output strings. Add a key to the properties file with his respective "language" value like the following example:
key=value
Seperate the different key-value pairs by entering each pair in a new line. Save the new properties file into the oecmlocalize_3000.jar file. If your properties file would be named oecmlocalize_ex.properties, you´d have to add the language to owbootstrap.xml like in the following example:
You can even add a flag symbol for your language to the designdefault20imageslang folder of your deployment. In the code example the image was specified to be named ex.gif. After a server restart, you should now be able to choose your language from the OWD login screen.
- English
- German
- Romanian
[img]http://openworkdesk.org/img/languages.JPG[/img]
The language can be changed by clicking the desired language in the upper right corner of the OWD login screen. For translating OWD, OWD development team introduced keys for every OWD String output, which are listed together with their respective "language" value in a properties file (e.g. oecmlocalize_en.properties for the english language). Those properties files can be found in the oecmlocalize_3000.jar file in the WEB-INFlib folder of your OWD Community Edition deployment.
The selectable languages on the login screen are configurable by editing following lines in the WEB-INFconfcmisowbootstrap.xml file of your deployment:
<availablelocals display='true'>
<!– for German also de_au.gif (Austria) or de_ch.gif (Swiss) flag available –>
<lang icon="/images/lang/de.gif" displayname="Deutsch">de</lang>
<!– for English also en_gb.gif (British) flag available –>
<lang icon="/images/lang/en.gif" displayname="English">en</lang>
<!– <lang icon="/images/lang/debugmode.gif" displayname="Debug Mode (for developers only)">debugmode</lang> –>
</availablelocals>
There are two ways to translate OWD Community Edition to YOUR language
Method 1:
Open an existing properties file from the oecmlocalize_3000.jar file, translate every key value to your language, rename the properties file (e.g. to oecmlocalize_ex.properties) and save it to the jar file. Add the new language to the code shown above in owbootstrap.xml like in following example:
<availablelocals display='true'>
<!– for German also de_au.gif (Austria) or de_ch.gif (Swiss) flag available –>
<lang icon="/images/lang/de.gif" displayname="Deutsch">de</lang>
<!– for English also en_gb.gif (British) flag available –>
<lang icon="/images/lang/en.gif" displayname="English">en</lang>
<!– for YOUR language –>
<lang icon="/images/lang/ex.gif" displayname="Example">ex</lang>
<!– <lang icon="/images/lang/debugmode.gif" displayname="Debug Mode (for developers only)">debugmode</lang> –>
</availablelocals>
You can even add a flag symbol for your language to the designdefault20imageslang folder of your deployment. In the code example the image was specified to be named ex.gif. After a server restart, you should now be able to choose your language from the OWD login screen.
Method 2:
Create a new properties file (e.g. oecmlocalize_ex.properties) and enter OWD´s keys with your respective language value. The keys for the output strings are shwon in so called debug mode. To enable debug mode, uncomment the debug mode part like in the following lines of owbootstrap.xml:
<availablelocals display='true'>
<!– for German also de_au.gif (Austria) or de_ch.gif (Swiss) flag available –>
<lang icon="/images/lang/de.gif" displayname="Deutsch">de</lang>
<!– for English also en_gb.gif (British) flag available –>
<lang icon="/images/lang/en.gif" displayname="English">en</lang>
<lang icon="/images/lang/debugmode.gif" displayname="Debug Mode (for developers only)">debugmode</lang>
</availablelocals>
Change language to Debug Mode from OWD´s login screen and you will see the original keys instead of OWD´s output strings. Add a key to the properties file with his respective "language" value like the following example:
key=value
Seperate the different key-value pairs by entering each pair in a new line. Save the new properties file into the oecmlocalize_3000.jar file. If your properties file would be named oecmlocalize_ex.properties, you´d have to add the language to owbootstrap.xml like in the following example:
<availablelocals display='true'>
<!– for German also de_au.gif (Austria) or de_ch.gif (Swiss) flag available –>
<lang icon="/images/lang/de.gif" displayname="Deutsch">de</lang>
<!– for English also en_gb.gif (British) flag available –>
<lang icon="/images/lang/en.gif" displayname="English">en</lang>
<!– for YOUR language –>
<lang icon="/images/lang/ex.gif" displayname="Example">ex</lang>
<!– <lang icon="/images/lang/debugmode.gif" displayname="Example (for developers only)">debugmode</lang> –>
</availablelocals>
You can even add a flag symbol for your language to the designdefault20imageslang folder of your deployment. In the code example the image was specified to be named ex.gif. After a server restart, you should now be able to choose your language from the OWD login screen.
Labels:
- Labels:
-
Archive
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2010 08:19 AM
Of course feel free to attach your properties files and let them, by this way, be part of the OpenWorddesk Community Edition.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-09-2011 06:14 AM
Hi,
What about support for RTL?
Kindest regards,
Hadi
What about support for RTL?
Kindest regards,
Hadi
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-10-2011 03:38 AM
Hi Hadi,
we were able to proof support of RTL in an exemplary PoC for an OpenWorkdesk project in Dubai already.
RTL support is achieved not only through the OpenWorkdesk application itself, but also through a RTL supported web browser and operating system on the client side. If the client side web browser and operating system are supporting RTL, you just would have to change the encoding of the localize properties file to a RTL supported language, like Arabic, Hebrew, Pashto, Persian, Sindhi, Syriac, Thaana, Urdu, Yiddish, etc.
Is there a chance, that you could translate the strings on the OpenWorkdesk welcome page to your desired language, so I could demonstrate RTL support with a screenshot or by attaching the adapted RTL encoded localize properties file?
The default strings on the welcome page are the following:
- Welcome to WeWebU OpenWorkdesk (used as welcome text)
- Name (used for the username field)
- Password (used for the password field)
- Login (for the login button)
- Reset (for the reset button)
we were able to proof support of RTL in an exemplary PoC for an OpenWorkdesk project in Dubai already.
RTL support is achieved not only through the OpenWorkdesk application itself, but also through a RTL supported web browser and operating system on the client side. If the client side web browser and operating system are supporting RTL, you just would have to change the encoding of the localize properties file to a RTL supported language, like Arabic, Hebrew, Pashto, Persian, Sindhi, Syriac, Thaana, Urdu, Yiddish, etc.
Is there a chance, that you could translate the strings on the OpenWorkdesk welcome page to your desired language, so I could demonstrate RTL support with a screenshot or by attaching the adapted RTL encoded localize properties file?
The default strings on the welcome page are the following:
- Welcome to WeWebU OpenWorkdesk (used as welcome text)
- Name (used for the username field)
- Password (used for the password field)
- Login (for the login button)
- Reset (for the reset button)
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2011 04:38 AM
Hi depf,
This is Great news
this will close a sizable gab with Alfresco
Gladly … the javascript escapes equivalent in Arabic for the strings you posted:
I'll do some testing with Alfresco (may be in a month time-hopefully); if successful I'll translate it to Arabic
Best regards
Hadi
… RTL support is achieved not only through the OpenWorkdesk application itself, but also through a RTL supported web browser and operating system on the client side…
This is Great news
this will close a sizable gab with Alfresco
Is there a chance, that you could translate the strings on the OpenWorkdesk welcome page …
Gladly … the javascript escapes equivalent in Arabic for the strings you posted:
welcome=\u0645\u0631\u062d\u0628\u0627 \u0628\u0643 \u0641\u064a \u0646\u0638\u0627\u0645 WeWebU OpenWorkdesk
name=\u0625\u0633\u0645 \u0627\u0644\u0645\u0633\u062a\u062e\u062f\u0645
password=\u0643\u0644\u0645\u0629 \u0627\u0644\u0645\u0631\u0648\u0631
login=\u062a\u0633\u062c\u064a\u0644 \u0627\u0644\u062f\u062e\u0648\u0644
reset=\u0645\u0633\u062d \u0627\u0644\u062d\u0642\u0648\u0644
I'll do some testing with Alfresco (may be in a month time-hopefully); if successful I'll translate it to Arabic
Best regards
Hadi
Related Content
- Alfresco Community Edition 23.4 Release Notes in Alfresco Blog
- Alfresco Share User Dashboard dashlets missing in Alfresco Forum
- Configuration of Advanced Search in share in Alfresco Forum
- java.net.SocketTimeoutException: timeout while calling a REST API in Alfresco Forum
- org.alfresco.error.AlfrescoRuntimeException Unable to create key manager in Alfresco Forum
Getting started
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.
