9 replies [Last post]
msinansahin
Offline
Joined: 2009-06-27

I have a template included Turkish characters as "ş and İ". My data block is placed rs_LIST and es_LIST tags as repeated sections. In my development machine every thing works fine but in test machine turkish charcters are converted into "?" character.

Settings of Developer and Test machines are same. Updates are disabled.
But windows update are different. these information may be helpful.

Please help!
Thankyou.

admin
Offline
Joined: 2010-09-06
More details please

Hello Msinansahin.

Can you please tell us:
1) What OS you are using (WinXP?)?
2) What version of OpenOffice?
3) What format is the output document?
4) Are you using any Field Renderer for the characters?
5) What Font are you displaying the Turkish characters in?
6) If you put these Turkish characters outside the rs_LIST and es_LIST section, do they also have the same problem?
7) If you point your DEV server to use the converter on TEST does that fix the problem?

msinansahin
Offline
Joined: 2009-06-27
details

Hi Paulj

1) What OS you are using (WinXP?)?
WinXP Professional
2) What version of OpenOffice?
Open Office 3.0.0
3) What format is the output document?
doc (we tried as pdf, but same result)
4) Are you using any Field Renderer for the characters?
No field renderer
5) What Font are you displaying the Turkish characters in?
Times new roman
6) If you put these Turkish characters outside the rs_LIST and es_LIST section, do they also have the same problem?
if i put Turkish chars outside the repeatable section no problem, they are displayed right.
7) If you point your DEV server to use the converter on TEST does that fix the problem?
I can not do this operation due to network constraints.

Note: in rs_LIST and es_LIST section three tables are depicted. If i remove one of them the Turkish chars are displayed write :). Another information is Turkish chars that are displayed as ? char are Templates characters. The chars comes as data from server are displayed true.

If you want my template i can post it.
Thanks

admin
Offline
Joined: 2010-09-06
Details on difference

Hello Msinansahin.

This seems fine. Given that it works in one environment and not in the other, can you please confirm the precise versions of Java and OpenOffice between the two environments? For OpenOffice look in program/version.ini. For java can you get the version information from inside the program you are using to call Docmosis? Do this by: System.out.println(System.getProperty("java.vm.version"));

msinansahin
Offline
Joined: 2009-06-27
DEVELOPMENT

DEVELOPMENT MACHINE

openoffice version.ini
[Version]
AllLanguages=tr
buildid=300m9(Build:9358)
ExtensionUpdateURL=http://updateext.services.openoffice.org/ProductUpdateService/check.Update
MsiProductVersion=
OOOBaseVersion=3.0
ProductBuildid=9358
ProductCode={3A308188-F0DC-47CA-B589-2DDCC1426C3D}
ProductMajor=300
ProductMinor=9
ProductPatch=
ProductSource=OOO300
UpdateID=OpenOffice.org_3_tr
UpdateURL=
UpgradeCode={7C35B9AB-2CE3-4C18-BE7C-5B97EA089EB3}
UpdateUserAgent= (${buildid}; ${_OS}; ${_ARCH}; BundledLanguages=${AllLanguages})

Java Version
java version "1.5.0_14"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03)
Java HotSpot(TM) Client VM (build 1.5.0_14-b03, mixed mode)
------------------------------------------------------------------------------------------------------------------------

TEST MACHINE

openoffice version.ini
[Version]
AllLanguages=tr
buildid=300m9(Build:9358)
ExtensionUpdateURL=http://updateext.services.openoffice.org/ProductUpdateService/check.Update
MsiProductVersion=
OOOBaseVersion=3.0
ProductBuildid=9358
ProductCode={3A308188-F0DC-47CA-B589-2DDCC1426C3D}
ProductMajor=300
ProductMinor=9
ProductPatch=
ProductSource=OOO300
UpdateID=OpenOffice.org_3_tr
UpdateURL=
UpgradeCode={7C35B9AB-2CE3-4C18-BE7C-5B97EA089EB3}
UpdateUserAgent= (${buildid}; ${_OS}; ${_ARCH}; BundledLanguages=${AllLanguages})

Java version
java version "1.5.0_17"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_17-b04)
Java HotSpot(TM) Client VM (build 1.5.0_17-b04, mixed mode)

Note: i've got java version by c:\java -version command. It is acceptable?

admin
Offline
Joined: 2010-09-06
Java issues

It is important to ensure that the Java version you are reporting is the one that is used by the system when rendering documents. Since you can have many Java versions installed on a machine java -version is often different from the java version any particular application might be using. If you are running the application from the command-line, then it is probably correct. To be sure, can you run the System.out.println() mentioned before in the same code that calls SystemManager.initialise()? That is pretty much guaranteed to give the true answer.

Anyway, your Java versions are different. Are you able to change one of them to match the other to check whether that is the issue.

Since you have said that it does not occur outside the repeating section, it is more likely related to Java than to OpenOffice since repeating sections undergo extra processing in Java. We are not sure why this would impact characters this way however. If you would please email your template to support@docmosis.com we will see if we can make any further suggestions.

Sharad
Offline
Joined: 2010-11-17
Hindi Characters are not being displayed properly

Hello Paulj,
I am trying to pass some Hindi characters [just using add method of DataProviderBuilder] but those are not being rendered properly. I have set the Java property for file encoding to UTF8. My Docmosis version is 2.2.1 and Open office is v3.2.

Rgds,
Sharad

Sharad
Offline
Joined: 2010-11-17
Unicode Issue resolved

Hello Paulj,
I am able to resolve this issue by setting "Arial Unicode MS" in the template.

Regards,
Sharad

msinansahin
Offline
Joined: 2009-06-27
tested

I have installed java 1.5.0.17 to Dev machine. But Turkish chars are displayed true.

admin
Offline
Joined: 2010-09-06
Solved

Some options to help with special characters in templates:

1) set the file.encoding Java system property explicitly. eg: java -Dfile.encoding=UTF8 MyApplication
2) use Docmosis 2.0 (builds 2772 onwards) since it manages this so that regional settings don't influence the character encoding being used.