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

Apache Ignite deep dive, SQL engine

Apache Ignite is an open source memory-centric distributed database, caching and comput- ing platform. From the beginning, it was designed as an in-memory data grid for developing a high-performance software system. So, it’s core architecture design is slightly different from the traditional NoSQL databases, which can simplify building modern applications with a flexible data model and simpler high availability, high scalability. Moreover, to understand how to design application with any databases or framework properly, you must understand the architecture of the database or framework itself. By getting a better idea of the system, you can solve different problems in your enterprise architecture landscape, can select a comprehensive database or framework that is appropriate for your application and get the maximum benefits from the system. In this article we are going to explore the Apache Ignite SQL engine. Under the hood...

Book review: High Performance in-memory computing with Apache Ignite by Sadruddin Md

A new title The Apache Ignite book has been released including Ignite 2.6 and above. Read the full book review by Sadruddin Md .

Quick start with In memory Data Grid, Apache Ignite

UP1: For complete quick start guide, see also the sample chapter of the book "High performance in-memory computing with Apache Ignite" here . Even you can find the sample examples from the GitHub repository . IMDG or In memory data grid is not an in-memory relational database, an NoSQL database or a relational database. It is a different breed of software datastore. The data model is distributed across many servers in a single location or across multiple locations. This distribution is known as a data fabric. This distributed model is known as a ‘shared nothing’ architecture. IMDG has following characteristics: All servers can be active in each site. All data is stored in the RAM of the servers. Servers can be added or removed non-disruptively, to increase the amount of RAM available. The data model is non-relational and is object-based. Distributed applications written on the platform independent language. The data fabric is resilient, allowing non-disruptive au...

My workspace

Search This Blog