Astro-App-Satpass2
view release on metacpan or search on metacpan
lib/Astro/App/Satpass2/Locale/C.pm view on Meta::CPAN
},
perigee => {
title => 'Perigee',
},
period => {
title => 'Period',
},
phase => {
table => [
[ 6.1 => 'new' ],
[ 83.9 => 'waxing crescent' ],
[ 96.1 => 'first quarter' ],
[ 173.9 => 'waxing gibbous' ],
[ 186.1 => 'full' ],
[ 263.9 => 'waning gibbous' ],
[ 276.1 => 'last quarter' ],
[ 353.9 => 'waning crescent' ],
],
title => 'Phase',
},
range => {
title => 'Range',
},
revolutions_at_epoch => {
title => 'Revolutions At Epoch',
},
right_ascension => {
title => 'Right Ascension',
},
second_derivative => {
title => 'Second Derivative',
},
semimajor => {
title => 'Semimajor Axis',
},
semiminor => {
title => 'Semiminor Axis',
},
status => {
title => 'Status',
},
time => {
title => 'Time',
},
tle => {
title => 'TLE',
},
type => {
title => 'Type',
},
};
__END__
=head1 NAME
Astro::App::Satpass2::Locale::C - Define the C locale for Astro::App::Satpass2
=head1 SYNOPSIS
my $c_locale = require Astro::App::Satpass2::Locale::C;
=head1 DESCRIPTION
This Perl module defines the C locale (which is the default locale )for
L<Astro::App::Satpass2|Astro::App::Satpass2>.
All you do with this is load it. On a successful load it returns the
locale hash.
=head1 SUBROUTINES
None.
=head1 THE LOCALE DATA
The locale data are stored in a hash. The top-level key is always locale
code. This is either a two-character language code, lower-case (e.g.
C<'en'>, a language code and upper-case country code delimited by an
underscore (e.g. C<'en_US'>, or C<'C'> for the default locale.
The data for each locale key are a reference to a hash. The keys of this
hash are the names of
L<Astro::App::Satpass2::FormatValue|Astro::App::Satpass2::FormatValue>
formats (e.g. C<{azimuth}>), the names of top-level reporting templates
preceded by a dash (e.g. C<{'-flare'}>, or the special keys
C<'{+message}'> (error messages) or C<'{+template}'> (templates).
The content of these second level hashes varies with its type, as
follows:
=head2 Format Effectors (e.g. C<{azimuth}>)
These are hashes containing data relevant to that format effector. The
C<{title}> key contains the title for that format effector. Other keys
relevant to the specific formatter may also appear, such as the
C<{table}> key in C<{phase}>, which defines the names of phases in terms
of phase angle. These extra keys are pretty much ad-hoc as required by
the individual format effector. In general they are cascades of C<HASH>
and/or C<ARRAY> references, though the last can be a C<CODE> reference.
The C<HASH> and C<ARRAY> references are resolved one at a time using
successive C<__localize()> arguments. A C<CODE> reference is resolved by
calling it passing the current C<__locale()> argument, and the original
C<__locale()> call's invocant argument (or C<undef> if none). See the
C<almanac> definition above for an example.
=head2 Top-level reporting (e.g. C<{'-flare'}>
The only key defined at the moment is C<{string}>, whose content is a
hash reference. This hash is keyed by text appearing as the values in
L<Astro::App::Satpass2::FormatValue|Astro::App::Satpass2::FormatValue>
C<literal>, C<missing>, and C<title> arguments, and the corresponding
values are the translations of that text into the relevant locale.
For example, a Spanish localization for C<{'-flare'}> might be something
like
{
es => {
string => {
night => 'noche',
( run in 0.454 second using v1.01-cache-2.11-cpan-75ffa21a3d4 )