I can confirm this issue.

DL->NF: Would you please check this?

NF->DL: I do not know how to deal with this issue. Isn't this one for
youre group (ER/OS?)

-

DL->ER: Would you please check this?

I would happily integrate them if someone provided me with the
necessary data. As a template for what is needed you may take
i18npool/source/localedata/data/en_US.xml and be sure you follow the
hints stated in i18npool/source/localedata/data/locale.dtd, you may
also want to take a look at
http://l10n.openoffice.org/servlets/ReadMsg?msgId=231673&listName=dev

Has it been taken care of and someone provided the template already?

AFAIK nobody has taken care of it. It would be very nice if you could
do it :)

Lithuanian OOo 1.0.1 version (from 
http://aldona.mii.lt/pms/lok/openoffice/bandom.htm ) already contains
Lithuanian Locale and Lithuanian currency in Tools->Options->Language
Settings->Languages dialog. This version also contains some bugfixes,
related to internationalisation (for example bug 9441 exists in
english 1.0.1, 1.0.2 and 643C versions but is fixed in lithuanian
1.0.1 version).
But developers of Lithuanian version don't distribute sources or
diff's. I and some more people from Lithuania wrote several emails
about sources but developers don't like to distribute - they say "this
is not finished work. We'll show sources only when work will be
finished". I think if developers distribute binaries from modified
sources they must distribute sources or diff's too. What OOo
developers think about this ?
I can write another email and ask to provide differences in source
code between english OOo 1.0.1 without Lithuanian locale and
lithuanian OOo 1.0.1 with Lithuanian locale.

@Mantas:

> [Lithuanian developers say] "this is not finished work.
> We'll show sources only when work will be finished"

I'd call that a rather short-sighted attitude. Nobody will be able to
evaluate their approach, and maybe they'd have to reimplement things
again for OOo1.1. But that's their problem then. For sure it's not an
open source attitude.

And no, they aren't obliged to publish source modifications if they
take and distribute OOo using the SISSL license instead of LGPL.

So feel free anyone to attach a proper
i18npool/source/localedata/data/lt_LT.xml file to this issue to get
Lithuanian locale support into any OOo distribution.

*** Issue 12267 has been marked as a duplicate of this issue. ***

We were informed by Valentina Dagiene (Dagiene@ktl.mii.lt, see
Lithuanian OOo project - http://aldona.mii.lt/pms/lok/openoffice/),
responsible for Lithuanian OOo project, that they have sent locale
file to OOo developers. 

Is anything else missing the lithuanian locale and Lithuanian language
support to be included in next "official" OOo release?

Guess, target milestone has to be changed to OOo 1.1 Beta2 ?

I just sent Valentina a mail asking whom the file was sent to. I never
heard of any.

Since I even don't know what they changed or fixed in their private
release and don't know yet what they sent to whom, I can't say
anything about what's missing.

Target will be set to 1.1Beta2 only if things are clarified.

Sorry for bothering, but having Llithuanian language support in OOo
1.1 is very important for us. Have you got an answer from Valentina?

If something is missing, please write here. 

No, no answer yet.

Accidently, cheking all bugs with word 'Lithuanian' in description, I
found that Lithuanian locale file is attached to bug #12938.

If anything else is missing, write to this bug - we really want
normally working OOo Beta2.  

Hi Mantas,

Thanks for digging that one out! Please see my comments there.

I am working on Latvian locale file, and have a question  what is
the reason behind using a "MSLCID" for a currency format code? 
Language is not necessarily equivalent to a currency, besides,
Microsoft list is far from being complete.

Hi bubuka,

That's great that finally someone is taking care of this!

The reason for the ID is that the format codes are also used in export
to MS Word or Excel, and the ID is needed for those fixed currencies.
Of course the language isn't equivalent to the currency, but a
currency is always assigned to one or more locales, and one locale has
always one or more currencies.

And yes, the Microsoft list is far from being complete, I already
addressed that in issue 11530

Btw: please use the content of the new directory structure
i18npool/source/localedata/data/* for templates, instead of the old
i18npool/source/localedata_*/*

Thanks
  Eike

lv_LV.xml received by Ilya Ketris (bubuka) as mail; adapted to new
structure. Committed to branch cws_srx644_apps61beta2

I now set this issue to fixed as the cws_srx644_apps61beta2 branch
will be closed today and we need issues to be in a definite state for
QA tracking reasons.

If we encounter things to be fixed in lv_LV.xml, we can either reopen
this issue after beta2 and retarget it to 1.1final, or create a new
issue then.

I agree with all the changes by Eike Rathke made to lv_LV.  I couldn't
find official abbreviations for quarter names and am not sure they
exist, to me "C1, C2" etc will do for now.  Full stop after an ordinal
numeral in dates is not an error.

--
Ilya Ketris

reassign to QA

Please test availability of Latvian number formats, collation,
numbering levels, and so on.

Found fixed on cws Apps61Beta2 using Windows and Solaris

verified

found integrated in srx644m13s2 on Solaris, Linux and Windows