Well, my original example was defining the array
@days at compile time, because that's going to be more efficient than:
sub day_of_week {
my $self = shift;
my @days = _('Mon'),_('Tues'),_('Wed'),_('Thurs'),_('Fri')
+,_('Sat'),_('Sun');
return $days[ $self->{day_num} ];
}
To give another example, I have about 3,000 lines of YAML config data, which gets loaded into a hash during initialisation. Some of that data will contain strings-to-be-translated, eg:
status:
a: _('Active')
i: _('Inactive')
During init, I check all the scalar values in the config hash and, if they match the _('...') form, then I bless them into i18n::String. Doing this with tie wouldn't be feasible.
Clint
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.