Skip to main content

A quick fix to set Locale on OOO (Open office org)

One of our web application uses OOO(open office org 3.2) to convert msOffice file to HTML file. There are a open source project named JodConverter which helps you to do most of the low level works such as connecting to server and much more. For quick start you can see my previous post. Few days ago we got a bug about Russian encoding after converting big Ms Word file to Html, as a usual our developers done their all the best to get rid of it, put directives on html and much more, but all in vain. Then i tried to change the OOO settings which recommended on ooo forums.
1) Change HTML compatibility - character set UTF-8 which should fix the problem but it havn't
2) Then change the Language settings -> set Locale for Russian and the bug fixes.
see the screen shot
Preferences
During my annual vacation, colleague could not manage to change the preferences to the production server. He as usual connect to server by ssl client on cli mode and thus could't change to the preferences. We usually use winscp or standard ssl client to connect to remote Solaris server. There are another very well tools xManager which will help you to bring remote linux/unix desktop to your windows desktop. Another very useful command is display LocalIP to tunneling gui from remote computer to local.
DISPLAY=HOST:0.0, export DISPLAY

For that remote port should be open for you to tunneling.
My colleague found another very quick fix to solve the problem with encoding. Through winscp he connects to the remote server and change the default locale to Russian by the following code on Linguistic.xcu file. Here is the fragments of the file to change
<node oor:name="General">

<prop oor:name="DefaultLocale" oor:type="xs:string">

<value>ru-RU</value>

</prop>

</node>

lingusitic.xcu file should be found on Solris file systme ~/.openoffice.org/3/user/registry/data/org/openoffice/Office/Linguistic.xcu

Comments

Popular posts from this blog

Send e-mail with attachment through OSB

Oracle Service Bus (OSB) contains a good collection of adapter to integrate with any legacy application, including ftp, email, MQ, tuxedo. However e-mail still recognize as a stable protocol to integrate with any application asynchronously. Send e-mail with attachment is a common task of any business process. Inbound e-mail adapter which, integrated with OSB support attachment but outbound adapter doesn't. This post is all about sending attachment though JavaCallout action. There are two ways to handle attachment in OSB: 1) Use JavaCallout action to pass the binary data for further manipulation. It means write down a small java library which will get the attachment and send the e-mail. 2) Use integrated outbound e-mail adapter to send attachment, here you have to add a custom variable named attachment and assign the binary data to the body of the attachment variable. First option is very common and easy to implement through javax.mail api, however a much more developer manage t

Tip: SQL client for Apache Ignite cache

A new SQL client configuration described in  The Apache Ignite book . If it got you interested, check out the rest of the book for more helpful information. Apache Ignite provides SQL queries execution on the caches, SQL syntax is an ANSI-99 compliant. Therefore, you can execute SQL queries against any caches from any SQL client which supports JDBC thin client. This section is for those, who feels comfortable with SQL rather than execute a bunch of code to retrieve data from the cache. Apache Ignite out of the box shipped with JDBC driver that allows you to connect to Ignite caches and retrieve distributed data from the cache using standard SQL queries. Rest of the section of this chapter will describe how to connect SQL IDE (Integrated Development Environment) to Ignite cache and executes some SQL queries to play with the data. SQL IDE or SQL editor can simplify the development process and allow you to get productive much quicker. Most database vendors have their own front-en

Load balancing and fail over with scheduler

Every programmer at least develop one Scheduler or Job in their life time of programming. Nowadays writing or developing scheduler to get you job done is very simple, but when you are thinking about high availability or load balancing your scheduler or job it getting some tricky. Even more when you have a few instance of your scheduler but only one can be run at a time also need some tricks to done. A long time ago i used some data base table lock to achieved such a functionality as leader election. Around 2010 when Zookeeper comes into play, i always preferred to use Zookeeper to bring high availability and scalability. For using Zookeeper you have to need Zookeeper cluster with minimum 3 nodes and maintain the cluster. Our new customer denied to use such a open source product in their environment and i was definitely need to find something alternative. Definitely Quartz was the next choose. Quartz makes developing scheduler easy and simple. Quartz clustering feature brings the HA and