5.10 and I18N::Langinfo

All,

I just installed AS 5.10 (1003) on my server here, and for some
reason, I18N::Langinfo was not installed. At least, I get "Can't
locate I18N::Langinfo.pm in @INC (@INC contains [the stuff you'd
expect it to contain]" when I try to use certain modules.

I can't find I18N::Langinfo on CPAN or in any of several PPM
repositories. I assume that since it's a core module, it doesn't have
a separate distro. My questions: how can I reinstall this module?
How can I find out why it failed? Did any others fail, and are
lurking problems waiting to bite me?

This is a frequent annoyance to me core modules are very difficult
to install or upgrade independently.

Thanks,
Eric
_______________________________________________
ActivePerl mailing list
ActivePerl@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

RE: 5.10 and I18N::Langinfo

Roode, Eric <> wrote:
> All,
> =

> I just installed AS 5.10 (1003) on my server here, and for some
> reason, I18N::Langinfo was not installed. At least, I get "Can't
> locate I18N::Langinfo.pm in @INC (@INC contains [the stuff you'd
> expect it to contain]" when I try to use certain modules. =

> =

> I can't find I18N::Langinfo on CPAN or in any of several PPM
> repositories. I assume that since it's a core module, it doesn't
> have a separate distro. My questions: how can I reinstall this
> module? =

> How can I find out why it failed? Did any others fail, and are
> lurking problems waiting to bite me? =


This is reminiscent of another question I saw recently. According to the
doco, it is "just a wrapper for the C nl_langinfo() interface", so
unless the build platform has appropriate support, I18N::Langinfo may
not get installed. But I agree it would be useful to know that. A "Not
supported on this platform" exception perhaps, rather than just being
silently dropped.

Yes it is a core module, so the source code is in the Perl distribution.
Perhaps you could extract and build it on your platform.

> =

> This is a frequent annoyance to me core modules are very
> difficult to install or upgrade independently. =


I can't recall ever needing to upgrade a core module, but I can imagine
it being difficult if the source is only in the Perl distribution.

HTH

-- =

Brian Raven =



==================== =====3D=
================
Atos Euronext Market Solutions Disclaimer
==================== =====3D=
================

The information contained in this e-mail is confidential and solely for the=
intended addressee(s). Unauthorised reproduction, disclosure, modification=
, and/or distribution of this email may be unlawful.
If you have received this email in error, please notify the sender immediat=
ely and delete it from your system. The views expressed in this message do =
not necessarily reflect those of Atos Euronext Market Solutions.

Atos Euronext Market Solutions Limited - Registered in England & Wales with=
registration no. 3962327. Registered office address at 25 Bank Street Lon=
don E14 5NQ United Kingdom. =

Atos Euronext Market Solutions SAS - Registered in France with registration=
no. 425 100 294. Registered office address at 6/8 Boulevard Haussmann 750=
09 Paris France.

L'information contenue dans cet e-mail est confidentielle et uniquement des=
tinee a la (aux) personnes a laquelle (auxquelle(s)) elle est adressee. Tou=
te copie, publication ou diffusion de cet email est interdite. Si cet e-mai=
l vous parvient par erreur, nous vous prions de bien vouloir prevenir l'exp=
editeur immediatement et d'effacer le e-mail et annexes jointes de votre sy=
steme. Le contenu de ce message electronique ne represente pas necessaireme=
nt la position ou le point de vue d'Atos Euronext Market Solutions.
Atos Euronext Market Solutions Limited Soci=E9t=E9 de droit anglais, enregi=
str=E9e au Royaume Uni sous le num=E9ro 3962327, dont le si=E8ge social se =
situe 25 Bank Street E14 5NQ Londres Royaume Uni.

Atos Euronext Market Solutions SAS, soci=E9t=E9 par actions simplifi=E9e, e=
nregistr=E9 au registre dui commerce et des soci=E9t=E9s sous le num=E9ro 4=
25 100 294 RCS Paris et dont le si=E8ge social se situe 6/8 Boulevard Hauss=
mann 75009 Paris France.
==================== =====3D=
================

_______________________________________________
ActivePerl mailing list
ActivePerl@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

I18N::Langinfo supplement/override (was RE: 5.10 and I18N::Langinfo)

Brian Raven wrote, on Thursday, May 22, 2008 11:49 AM:
> Roode, Eric <> wrote:
[...]

> > I can't find I18N::Langinfo on CPAN or in any of several PPM
> > repositories.
>
> This is reminiscent of another question I saw recently. According to
> the doco, it is "just a wrapper for the C nl_langinfo() interface",
> so unless the build platform has appropriate support, I18N::Langinfo
> may not get installed. But I agree it would be useful to know that.

I have some modules (Time::Format, Regexp::Common::time,
Time::Normalize) that need to know the month and weekday names, and
their abbreviations, in the user's current locale. Those modules
currently get this information from I18N::Langinfo (and fall back on
English names/abbreviations).

Since I18N::Langinfo is not reliably available, I would like to
provide a way for the user to explicitly specify the month/weekday
names/abbreviations that they would like to use. My first thought was
to provide a set of functions in each module: set_month_names(),
set_weekday_names(), etc. But... why should the user have to set the
names once for each module? They should be able to do it once and be
done.

So I am considering having a new central module whose only purpose in
life is to wrap I18N::Langinfo and allow the user to specify month and
weekday names and abbreviations (or override them if the module exists
and works but the caller wants a different set of names for some
reason). And it should probably allow the user to specify the other
strings that I18N::Langinfo provides.

I'm posting this here to stimulate discussion about the merits of this
idea. Is it good? Is it awful? Does this sort of thing exist
already?

Should it be incorporated into I18N::Langinfo? I suspect that is a
bad idea. If it should be a new module, should it be under I18N?
Maybe I18N::Langinfo::Fake? I18N::Langinfo::Override? Should it be
under Locale:: or even Lingua::?

Thanks in advance,
Eric Roode

PS: I am also posting this to use.perl.org, and the modules@perl.org
mailing list.
_______________________________________________
ActivePerl mailing list
ActivePerl@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs