Issue 71483 - ta-IN windows installer not showing tamil characters
Summary: ta-IN windows installer not showing tamil characters
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Internationalization
Classification: Code
Component: ui (show other issues)
Version: OOo 2.1
Hardware: All Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: mugunth
QA Contact: issues@l10n
URL:
Keywords: needmoreinfo, oooqa
Depends on:
Blocks:
 
Reported: 2006-11-13 10:41 UTC by mugunth
Modified: 2013-08-07 14:59 UTC (History)
6 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description mugunth 2006-11-13 10:41:32 UTC
I downloaded & tested the ta-IN installer for the upcoming OOo2.1 from the
following location:
http://oootranslation.services.openoffice.org/pub/OpenOffice.org/ooomisc/sdf/OOo_l10n/wnt/en-US_ta-IN_download/Oo_2.1.0_061101_Win32Intel_install_ta-IN.exe


Once installed the user interface shows only boxes instead of tamil characters.
This could be due to OpenOffice windows installer not setting the default
font correctly.

In most windows systems, the default tamil font will be Latha.ttf (or Ariel
font which includes tamil unicode characters also)
Is it possible to set the default font for UI in windows to Latha.ttf font
As of now since we could not read whats shown in the strings the ta-IN windows
installer cannot be used by tamil users.
Comment 1 rafaella.braconi 2006-11-13 11:20:20 UTC
cc:ing ihi and coni
Comment 2 ivo.hinkelmann 2006-11-13 11:47:26 UTC
Ingo, Tamil is set to UTF8 in the msi-encoding.lst . Is there a way to set the
default font or do you know how to solve this thus the correct characters are
shown? Do we have to build en-US_ta-IN combination?
Comment 3 ivo.hinkelmann 2006-11-13 11:47:52 UTC
target 2.1
Comment 4 ivo.hinkelmann 2006-11-13 11:59:49 UTC
in VCL xcu the default fonts for ta-IN are :

  <node oor:name="ta-IN" oor:op="replace">
      <prop oor:name="UI_SANS" oor:op="replace" oor:type="xs:string">
        <value>Lohit Tamil;Tahoma;Lucidasans;Lucida Sans;Supplement;Andale Sans
UI;Arial Unicode MS;Lucida Sans Unicode;clearlyU;Interface User;Wa
      </prop>
      <prop oor:name="CTL_DISPLAY" oor:op="replace" oor:type="xs:string">
        <value>Lohit Tamil;Tahoma;Lucidasans;Lucida Sans;Arial Unicode MS</value>
      </prop>
      <prop oor:name="CTL_HEADING" oor:op="replace" oor:type="xs:string">
        <value>Lohit Tamil;Tahoma;Lucidasans;Lucida Sans;Arial Unicode MS</value>
      </prop>
      <prop oor:name="CTL_PRESENTATION" oor:op="replace" oor:type="xs:string">
        <value>Lohit Tamil;Tahoma;Lucidasans;Lucida Sans;Arial Unicode MS</value>
      </prop>
      <prop oor:name="CTL_SPREADSHEET" oor:op="replace" oor:type="xs:string">
        <value>Lohit Tamil;Tahoma;Lucidasans;Lucida Sans;Arial Unicode MS</value>
      </prop>
      <prop oor:name="CTL_TEXT" oor:op="replace" oor:type="xs:string">
        <value>Lohit Tamil;Tahoma;Lucidasans;Lucida Sans;Arial Unicode MS</value>
      </prop>
    </node>

is this entry somehow wrong?
Comment 5 ingo.schmidt-rosbiegal 2006-11-13 15:36:06 UTC
is -> ihi: vcl xcu has nothing to do with the Windows Installer problems. xcu
files are only used by the Office application, not by the installers.
I am wondering about this problem. At least since m185 (found no older version)
ta-IN is listed in solenv/bin/modules/installer/globals.pm in the list of
languages not supported by Windows Installer. Therefore the complete
installation process should be in English, that is automatically added to the
installation set.
You have a cws to create ta-IN installation sets? Please test this.
Comment 6 mugunth 2006-11-13 15:53:06 UTC
The problem is observered not only in windows installer, its observed in the
openoffice product after installation also. So VCL xcu files might also needs to
be checked. 
( i am just thinking aloud - experts need to confirm this)

Is it possible to have different VCL xcu files for windows and Linux. 
Because Lohit tamil gets bundled in most Linux distros. In windows Lohit tamil
font is not available. Latha font is bundled with most of the latest windows OS
(XP onwards with indic language support enabled).

If the entries in the file VCL xcu for windows contain Latha font instead of
Lohit Tamil font, this problem might get solved.
Comment 7 ivo.hinkelmann 2006-11-15 13:34:53 UTC
I rebuilded ta-IN and installed the windows build:

-installer is in en-US
-gui is in tamil correct shown 

I'm not sure if this issue is still valid. I will upload the new build asap
Comment 8 mugunth 2006-11-30 14:51:43 UTC
Hi Ihi,
I still find this problem. 
I downloaded and installed the latest Openoffice ta-IN build from this URL:
http://oootranslation.services.openoffice.org/pub/OpenOffice.org/ooomisc/sdf/OOo_l10n/wnt/en-US_ta-IN_download/

and tried using in WindowsXP machine. I find the installer is showing english
characters and after installing when I try using openoffice, i find boxes in all
the menus.

I tried replacing Andale San UI font to Latha font(tamil unicode font provided
by Microsoft) in font replacement table, still I see boxes in openoffice menus.

Please check this. 
Comment 9 mugunth 2006-11-30 14:52:58 UTC
It dont work for us. Still the problem is there.
Comment 10 ivo.hinkelmann 2006-11-30 15:56:51 UTC
set target to OOo 2.2
Comment 11 ivo.hinkelmann 2006-11-30 16:01:38 UTC
Did you also checked the latest rc1 ?
http://oootranslation.services.openoffice.org/pub/OpenOffice.org/2.1.0rc1/
Comment 12 ivo.hinkelmann 2007-01-08 17:14:22 UTC
what is the status of this issue?
Comment 13 vg 2007-01-24 17:53:06 UTC
reassign
Comment 14 Martin Hollmichel 2008-01-28 02:38:11 UTC
set target 3.x
Comment 15 stefan.baltzer 2008-10-29 14:17:01 UTC
SBA: This issue has a target set but is still in state of "Unconfirmed".
Please re-check with OOo 3.0 or younger if it is (still) valid.
Then confirm it or set an appropriate resolution.
Thank you.
Comment 16 stefan.baltzer 2008-10-29 14:24:13 UTC
SBA: This issue has a target set but is still in state of "Unconfirmed".
Please re-check with OOo 3.0 or younger if it is (still) valid.
Then confirm it or set an appropriate resolution.
Thank you.
Comment 17 Rainer Bielefeld 2010-03-13 08:01:26 UTC
@mugunth 
Still a problem for you?
If yes, please contribute a step by step instruction how to reproduce the problem
I will close the issue within 10 days if we don't get required further information.
Comment 18 Rainer Bielefeld 2010-03-24 06:26:03 UTC
Closing issue due to reporter's inactivity as WFM.
Comment 19 Rainer Bielefeld 2010-03-24 06:26:18 UTC
@reporter:
Please feel free to reopen this issue if you find out that the problem still
exists in the latest release of OOo and if you can provide requested additional
information.