Re: [l10n-dev] numbering
Hi Javier, Khmer native numbering is supported, see the data file in, http://l10n.openoffice.org/source/browse/l10n/i18npool/source/nativenumber/data/numberchar.h?rev=1.7&content-type=text/vnd.viewcvs-markup You should be able to show number in Khmer by selecting the language and the number format as '[NatNum1]0' under Format->Cells...->Numbers->Format code in StarCalc, if you have Khmer font to display the glyphs. If you want to setup Khmer number as pre-defined bullet/numbering, You can set it up in locale data km_KH.xml, you can see number type 12 is for native numbering in locale.dtd, take a look of hi_IN.xml and see how it sets for Hindi number bullet. Regards, Karl. Javier SOLA wrote: Karl, What would I need to do to include Khmer numbering style in OOo 2.0? Thanks, Javier P.D. yes, this is response to a very old mail. Karl Hong wrote: For Asian numbering, those for Chinese, Japanese and Korean, you have to enable Asian support under Tools->Options->Language settings, and you can find the numbering under Format->Numbering/Bullet->Options. Same for Complex Text Layout(CTL) languages, like Thai, Arabic and Hebrew. Karl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Punjabi Locale Data Audit has problems???
--- Eike Rathke <[EMAIL PROTECTED]> wrote: > Hi Amanpreet, > > On Fri, Apr 22, 2005 at 01:49:16 -0700, Amanpreet > Singh Alam wrote: > > > 1) OpenOffice has following problems > > Just to be sure: does that mean that the CLDR data > is correct in all > places you listed under this? No, CLDR has some problem as well! as i mention in mail. > > > Common has also need correction as following > > > > how to update these for Punjabi > > A bug against the CLDR would have to be filed, see > http://www.jtcsv.com/cgibin/locale-bugs > In case you file a bug state the locale (pa_IN) in > the subject line, and > you should give some reference, online or books, to > get changes > accepted. Please publish the bug number here on the > list so I can add it > to the audit file. OK, i m filing a bug for this after collecting facts > > Once the CLDR data is corrected we'll align OOo data > to CLDR. > > Eike thanks Eike with regards Amanpreet Singh Alam POSRD Moga > > -- > OOo/SO Calc core developer. Number formatter > bedevilled I18N transpositionizer. > GnuPG key 0x293C05FD: 997A 4C60 CE41 0149 0DB3 > 9E96 2F1A D073 293C 05FD > > - > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] migrate l10nhelp
hmm ... 43039 helpcontent2 m92 , 41018 helpcontent2 mXX ( first checkin of the new help ) is the difference I guess So if I use mXX OOo source (XX < 92) with cat+sort thing it might work. I'll try (and report follows, of course :-) Not right. In m63 there is helpcontent2 41253 lines. Where can I find mXX (first checkin of the new help)? I was looking in documentation CVS but there's a million thingh up there. Thanks -- Robert Ludvik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Punjabi Locale Data Audit has problems???
Hi Amanpreet, On Fri, Apr 22, 2005 at 01:49:16 -0700, Amanpreet Singh Alam wrote: > 1) OpenOffice has following problems Just to be sure: does that mean that the CLDR data is correct in all places you listed under this? > Common has also need correction as following > > how to update these for Punjabi A bug against the CLDR would have to be filed, see http://www.jtcsv.com/cgibin/locale-bugs In case you file a bug state the locale (pa_IN) in the subject line, and you should give some reference, online or books, to get changes accepted. Please publish the bug number here on the list so I can add it to the audit file. Once the CLDR data is corrected we'll align OOo data to CLDR. Eike -- OOo/SO Calc core developer. Number formatter bedevilled I18N transpositionizer. GnuPG key 0x293C05FD: 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] Punjabi Locale Data Audit has problems???
Hi, for LOCALE DATA AUDIT, Punjabi (pa-IN) has following Problems from http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html 1) OpenOffice has following problems http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#905 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#906 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#907 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#908 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#909 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#910 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#911 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#912 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#913 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#914 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#915 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#916 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#917 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#918 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#919 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#920 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#921 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#922 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#923 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#924 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#925 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#926 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#927 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#928 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#929 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#930 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#931 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#932 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#933 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#934 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#935 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#936 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#937 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#938 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#939 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#940 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#941 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#942 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#943 Common has also need correction as following http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#905 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#906 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#907 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#913 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#905 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#919 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#920 http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html#921 how to update these for Punjabi thanks Amanpreet Singh Alam http://punlinux.sf.net __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] numbering
Karl, What would I need to do to include Khmer numbering style in OOo 2.0? Thanks, Javier P.D. yes, this is response to a very old mail. Karl Hong wrote: For Asian numbering, those for Chinese, Japanese and Korean, you have to enable Asian support under Tools->Options->Language settings, and you can find the numbering under Format->Numbering/Bullet->Options. Same for Complex Text Layout(CTL) languages, like Thai, Arabic and Hebrew. Karl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] adding new ancoding does not work
On Friday 22 April 2005 10:06, Stephan Bergmann wrote:
> Hristo Simeonov Hristov wrote:
> > On Wednesday 20 April 2005 15:29, Stephan Bergmann wrote:
> >>Hristo Simenov Hristov wrote:
> >>>On Wednesday 20 April 2005 10:27, Stephan Bergmann wrote:
> Hristo Simeonov Hristov wrote:
> >On Tuesday 19 April 2005 20:19, Eike Rathke wrote:
> >>Hi Hristo,
> >>
> >>On Tue, Apr 19, 2005 at 10:28:52 +0300, Hristo Simenov Hristov wrote:
> >>>I think that when I choose my encoding in the dialog, it does not
> >>>call the method for converting my encoding but calls some default
> >>>method.
> >>
> >>Where (in which module, which dialog) did you try it?
> >
> >In Writer I'm opening Text encoded file.
> >I tried with replacing of aImplIBM866ToUniTab with values of
> >aImplMIKToUniTab And when I opened TE file it appears correctly, so
> > this array is correct. The problem is how to figure it out which
> >aImplToUniTab using when I open such file with selected MIK
> > encoding (I added in the combobox needed string to be chosen this MIK
> > encoding)
>
> Not sure how the status is today, but there used to be trouble with the
> association of text labels and RTF_TEXTENCODING_ values in those src
> files, esp. if you are running a translated (not en-US?) version of
> OOo. One way to debug this might be to check what calls to
> Impl_getTextEncodingData (textenc.cxx) are actually made.
> >>>
> >>>How can I print text in the console?
> >>>With printf?
> >>
> >>Try it out. ;)
> >>Yes, printf should work on Unix, at least.
> >
> > Hm, it doesn't work.
> > error: `printf' undeclared
> > I put this printf("%d",nEncoding); before the return.
> > Am I wrong?
>
> #include
> is your friend :)
Ups, I have forgot this :)
My mistake. I didn't use C++ since my school days :)
!0x
I'll tried this evening.
--
-
Hristo Simeonov Hristov
Leader of OpenOffice.org - Bulgaria
pgpl0iUagmFdz.pgp
Description: PGP signature
Re: [l10n-dev] adding new ancoding does not work
Hristo Simeonov Hristov wrote:
On Wednesday 20 April 2005 15:29, Stephan Bergmann wrote:
Hristo Simenov Hristov wrote:
On Wednesday 20 April 2005 10:27, Stephan Bergmann wrote:
Hristo Simeonov Hristov wrote:
On Tuesday 19 April 2005 20:19, Eike Rathke wrote:
Hi Hristo,
On Tue, Apr 19, 2005 at 10:28:52 +0300, Hristo Simenov Hristov wrote:
I think that when I choose my encoding in the dialog, it does not
call the method for converting my encoding but calls some default
method.
Where (in which module, which dialog) did you try it?
In Writer I'm opening Text encoded file.
I tried with replacing of aImplIBM866ToUniTab with values of
aImplMIKToUniTab And when I opened TE file it appears correctly, so this
array is correct. The problem is how to figure it out which
aImplToUniTab using when I open such file with selected MIK encoding
(I added in the combobox needed string to be chosen this MIK encoding)
Not sure how the status is today, but there used to be trouble with the
association of text labels and RTF_TEXTENCODING_ values in those src
files, esp. if you are running a translated (not en-US?) version of OOo.
One way to debug this might be to check what calls to
Impl_getTextEncodingData (textenc.cxx) are actually made.
How can I print text in the console?
With printf?
Try it out. ;)
Yes, printf should work on Unix, at least.
Hm, it doesn't work.
error: `printf' undeclared
I put this printf("%d",nEncoding); before the return.
Am I wrong?
#include
is your friend :)
Regards
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
