Daniel Muey > Locale-Maketext-Utils > Locale::Maketext::Utils



Annotate this POD


New  2
Open  4
View/Report Bugs
Module Version: 0.41   Source  


Locale::Maketext::Utils - Adds some utility functionality and failure handling to Local::Maketext handles


In MyApp/Localize.pm:

    package MyApp::Localize;
    use Locale::Maketext::Utils; 
    use base 'Locale::Maketext::Utils'; 
    our $Encoding = 'utf-8'; # see below
    # no _AUTO
    our %Lexicon = (...

Make all the language Lexicons you want. (no _AUTO)

Then in your script:

   my $lang = MyApp::Localize->get_handle('fr');

Now $lang behaves like a normal Locale::Maketext handle object but there are some new features, methods, and failure handling which are described below.

our $Encoding ^

If you set your class's $Encoding variable the object's encoding will be set to that.

   my $enc = $lh->encoding(); 

$enc is $MyApp::Localize::fr::Encoding || $MyApp::Localize::Encoding || encoding()'s default

Argument based singleton ^

The get_handle() method returns an argument based singleton. That means the overhead of initializing an object and compiling parts of the lexicon being used only happen once even if get_handle() is called several times with the same arguments.

Lexicon hashes that are "read only" ^

Sometimes you want your lexicon to be a tied hash that is read only which would be fatal when storing a compiled key's value (e.g. GDBM_File).

To faciltate that (without needing other special tie()s as per "Tie::Hash::ReadonlyStack compat Lexicon") you can simply init() your handle with:

  $lh->{'use_external_lex_cache'} = 1;

That will cause all compiled strings to be stored in the object instead of back in the lexicon.

Aliasing ^

In your package you can create an alias with this:

   __PACKAGE__->make_alias($langs, 1);
   MyApp::Localize->make_alias([qw(en en_us i_default)], 1);

Where $langs is a string or a reference to an array of strings that are the aliased language tags.

You must set the second argument to true if __PACKAGE__ is the base class.

The reason is there is no way to tell if the pakage name is the base class or not.

This needs done before you call get_handle() or it will have no effect on your object really.

Ideally you'd put all calls to this in the main lexicon to ensure it will apply to any get_handle() calls.

Alternatively, and at times more ideally, you can keep each module's aliases in them and then when setting your obj require the module first.


Deprecated for clarity:

These are deprecated because they are ambiguous names (i.e. used in other places by other things) and thus problematic when harvesting phrases.

$lh->print($key, @args);

Shortcut for

    print $lh->maketext($key, @args);

$lh->fetch($key, @args);

Alias for

    $lh->maketext($key, @args);

$lh->say($key, @args);

Like $lh->print($key, @args); except appends $/ || \n

$lh->get($key, @args);

Like $lh->fetch($key, @args); except appends $/ || \n


Returns the base class of the object. So if $lh is a MyApp::Localize::fr object then it returns MyApp::Localize


Returns the language class of the object. So if $lh is a MyApp::Localize::fr object then it returns MyApp::Localize::fr


Returns the real language name space being used, not language_tag()'s "cleaned up" one


Returns 0 if the argument is not a language that can be used to get a handle.

Returns the language handle if it is a language that can be used to get a handle.


This returns a hashref whose keys are the language tags and the values are the name of language tag in $lh's native langauge.

It can be called several ways:

The module it uses for lookup (Locales::Language) is only required when this method is called. Make sure you have the latest verison of Locales as 0.04 (i.e. Locales::Base 0.03) is buggy!

The module it uses for lookup (Locales::Language) is currently limited to two character codes but we try to handle it gracefully here.

In array context it will build and return an additional hashref with the same keys whose values are the language name in the langueage itself.

Does not ensure that the tags are loadable, to do that see below.


Exactly the same as $lh->lang_names_hashref() (because it calls that method...) except it only contains tags that are loadable.

Has additional overhead of calling $lh->langtag_is_loadable() on each key. So most likely you'd use this on a single specific place (a page to choose their language setting for instance) instead of calling it on every instance your script is run.

$lh->append_to_lexicons( $lexicons_hashref );

This method allows modules or script to append to the object's Lexicons. Consider using "Tie::Hash::ReadonlyStack compat Lexicon" instead.

Each key is the language tag whose Lexicon you will prepend its value, a hashref, to.

So assuming the key is 'fr', then this is the lexicon that gets appended to:


The only exception is if the key is '_'. In that case the main package's Lexicon is appended to:


        '_' => {
            'Hello World' => 'Hello World',
        'fr' => {
            'Hello World' => 'Bonjour Monde',


Removes $key from every lexicon. Consider using "Tie::Hash::ReadonlyStack compat Lexicon" instead.

What is removed is stored in $lh->{'_removed_from_lexicons'}

If defined, $lh->{'_removed_from_lexicons'} is a hashref whose keys are the index number of the $lh->_lex_refs() arrayref.

The value is the key and the value that that lexicon had.

This is used internally to remove _AUTO keys so that the failure handler below will get used


Return a Locales object suitable for the object (or the optional locale tag argument).

If the locale tag can not be loaded it tries the super (if any) then $lh->{'fallback_locale} (if set) and its super (if any) before defaulting to 'en'.

Locales is where all the CLDR data and logic comes from.


Takes 2 optional arguments:

1. A locale tag whose name you want (defaults to the object's locale).
2. A locale tag whose language you want the name to be in (defaults to the object's locale).

These names are defined by the CLDR.


With no argument, returns the object locale’s character orientation as a string suitable for HTML’s dir attribute.

Given a CLDR character orientation string it will return a string suitable for HTML’s dir attribute.

Given a locale tag and second argument of true (specifying that the first argument is a tag not a CLDR character orientation string ) it returns that locale’s character orientation as a string suitable for HTML’s dir attribute.

The character orientation comes from CLDR.


Returns the locale display pattern for the object or the tag given as the ofrst optional argument.

The pattern comes from the CLDR.


Returns the character orientation string for the object or the tag given as the first optional argument.

The string comes from the CLDR.

$lh->lextext('Your key here.')

Get the lexicon’s text of 'Your key here.' without compiling it (in other words all bracket notation is still in tact).

The results are suitable for the first arg to makethis().

$lh->text('Your key here.')–deprecated for clarity

Deprecated name of $lh->lextext().

It is deprecated because it is an ambiguous name (i.e. used in other places by other things) and thus problematic when harvesting phrases.


Like maketext() but does not lookup the phrase in the lexicon and compiles the phrase exactly as given.


Like makethis() but uses the base class as the phrase compiler instead of the object.

This is usful in testing when you want consistent semantics on arbitrary objects.


This is an alias to maketext(). Its sole purpose is to be used to semantically indicate that the source code does not contain a translatable string in the call to maketext().

For example:

    $lh->maketext('Hello World') 

It is easy to tell that we need to provide translations for 'Hello World'. But given:


It is not easy to determine what $api_rv->{'string'} is in order to pass it on to the translation team.

However if we do that like this:

     my $string = translatable('Hello World'); # See Locale::Maketext::Utils::MarkPhrase

Then the parser can simply ignore the call to makevar() and find the value it is interested in via translatable()

Additionally, since makevar() is meant to work with variables it also has the distinction of taking an array ref, as its only arg, that contains the arguments you’d normally pass to make*().

This makes it easier/possible to do something like this:


in, say, Template Toolkit syntax.

For example, if 'api_mt_result' is [ 'You have [quant,_1,user,users].', 42 ] you could do:

    [% locale.makevar(api_mt_result) %]

instead of something hacky and convoluted like:

    [%- SET item_list = [] -%]
    [%- FOREACH i IN api_mt_result; item_list.push(i.json); END -%]
    [% '\[% locale.makevar(' _ item_list.join(", ") _ ') %\]' | evaltt %]


Helps you find an asset for a locale based on the locale's fallback.

Takes a code ref and an optional locale tag (default to the object's locale).

The code ref is passed a locale tag (from the list of the locale's fallbacks).

The first tag that returns a defined value halts the loop and that value is returned.

    my $foo = $lh->get_asset(sub {
        my ($tag) = @_;
        return "foo+$tag" if Foo->has_locale($tag);


Takes a path to look for with %s where the locale tag should be. The first locale (in the object's locale's fallback list) whose path passes -f gets the path returned. Does a return; if none are found.

    my $template = $lh->get_asset_file('…/.locale/%s.tt'); # …/.locale/fr.tt

The optional second argument is a string to return when the path passes -f.

    my $js = $lh->get_asset_file('…/.locale/%s.css','http://example.com/locale_css/%s.css'); # http://example.com/locale_css/fr.css


Same as get_asset_file() but the path must pass -d.


Delete the internal cache. Returns the hashref that was removed.

You can pass it a key and only that is removed (i.e. instead of the entire cache).

    my $get_asset_file_cache = $lh->delete_cache('get_asset_file');  # only delete the cached data for get_asset_file()
    my $entire_cache = $lh->delete_cache();# delete the entire cache

Currently this applies to 'get_asset_file', 'get_asset_dir', 'makethis', and 'makethis_base'.

Automatically _AUTO'd Failure Handling with hooks ^

This module sets fail_with() so that failure is handled for every Lexicon you define as if _AUTO was set and in addition you can use the hooks below.

This functionality is turned off if:

The result is that a key is looked for in the handle's Lexicon, then the default Lexicon, then the handlers below, and finally the key itself (Again, as if _AUTO had been set on the Lexicon). I find this extremely useful and hope you do as well :)


If lookup fails this code reference will be called with the arguments ($lh, $key, @args)

It can do whatever you want to try and find the $key and return the desired string.

   return $string_from_db;

If it fails it should simply:


That way it will continue on to the part below:


If $lh->{'_get_key_from_lookup'} is not a code ref, or $lh->{'_get_key_from_lookup'} returned undef then this method is called with the arguments ($lh, $key, @args) right before the failure handler does its _AUTO wonderfulness.

Improved Bracket Notation ^


This uses the decimal format defined in CLDR to format the number. That means there is no need to subclass or define special data per class.

It takes an additional argument to specify the maximum number of decimal places you want.


CLDR plural rule aware version of the Locale::Maketext numerate(). That means there is no need to subclass.

See Locales::DB::Docs::PluralForms for locale specific arguments.


CLDR plural rule aware version of the Locale::Maketext quant().

That means there is no need to subclass, you need to specify all arguments (except the always optional “Special Zero” argument that some locales have)

See Locales::DB::Docs::PluralForms for locale specific arguments.

e.g. Key is 'en', value is 'ru':

    '… [quant,_1,one category text,other category text,special_zero text] …' => '… [quant,_1,one category text,few category text,many category text,other category text] …'

You can use '%s' to specify the position of the number. Other wise it is prepended with a space (except “Special Zero” which won't contain the number.)

The number is formatted via numf() with a max decimal place of 3.

You can pass in an array ref instead of the number in order to pass in a max decimal places value. The first item is the number, the second item is the max decimal places.

    maketext('The average monthly rainfall is [quant,_1,inch,inches].', $n); # … is 42.869 inches.
    maketext('The average monthly rainfall is [quant,_1,inch,inches].', [$n,2]); # … is 42.87 inches.

Additional bracket notation methods ^


Joins the given arguments with the first argument:

   [join,-,_*], @numbers becomes 1-2-3-4-5
   [join,,_*], @numbers becomes 12345
   [join,~,,_*], @numbers becomes 1,2,3,4,5
   [join,~, ,_*], @numbers becomes 1, 2, 3, 4, 5

Array ref arguments are expanded:

   $lh->maketext('… [join,-,_1,2] …', [1,2,3],4); # … 1-2-3-4 …


Take a list of arguments (like join–array ref arguments are expanded) and format it per the locale's CLDR list pattern for and.

   You chose [list_and,_1]., \@pals
   You chose Rhiannon.
   You chose Rhiannon and Parker.
   You chose Rhiannon, Parker, and Char.
   You chose Rhiannon, Parker, Char, and Bean.

See "get_list_and()" in Locales for more information.


Same as list_and but with or-lists. See "get_list_or()" in Locales for more information and an important caveat.


Like list_and() but all values are quoted via the CLDR to disambiguate them.


Like list_or() but all values are quoted via the CLDR to disambiguate them.


Creates a phrased list "and/or" style:

  You chose [list,and,_*]., @pals
  You chose Rhiannon.
  You chose Rhiannon and Parker.
  You chose Rhiannon, Parker, and Char.
  You chose Rhiannon, Parker, Char, and Bean.

The 'and' above is by default an '&':

  You chose [list,,_*]

  You chose Rhiannon, Parker, & Char

A locale can set that but I recommend being explicit in your lexicons so the translators will know what you're trying to say:


A locale can also control the seperator and "oxford" comma character (IE empty string for no oxford comma)

The locale can do this by setting some variables in the same manner you'd set 'numf_comma' to change how numf() behaves for a class without having to write an almost identical method.

The variables are (w/ defaults shown):

  $lh->{'list_seperator'}   = ', ';
  $lh->{'oxford_seperator'} = ',';
  $lh->{'list_default_and'} = '&';

Array ref arguments are expanded.


Allows you to get datetime output formatted for the current locale.

    'Right now it is [datetime]'

It can take 2 arguments which default to DateTime->now and 'date_format_long' respectively.

The first argument tells the function what point in time you want. The values can be:

The second tells it what format you'd like that point in time stringified. The values can be:


CLDR version of current year. i.e. Shortcut to [datetime,,YYYY].


Convert byte count to human readable format. Does not require external modules.

   'You have used [format_bytes,_1] of your alloted space.', $bytes

Accepts an optional argument for max number of decimal places, default is 2.


Shortcut to Math::Units convert()

  'The fish was [convert,_1,_2,_3]" long', $feet,'ft','in'


This method allows you to choose a word or phrase to use based on a boolean.

The first argument is the boolean value which should be true, false, or undefined. The next arguments are the string to use for a true value, the string to use for a false value and an optional value for an undefined value (if none is given undefined uses the false value).

  'You [boolean,_1,have won,didn't win] a new car.'

  'You [boolean,_1,have won,didn't win,have not entered our contest to win] a new car.'

   $lh->maketext(q{Congratulations! It's a [boolean,_1,girl,boy]!}, $is_a_girl);

It can have “embedded args”:

    'You must specify a value[boolean,_1, for the “_1” field].


This method allows you to choose a word or phrase to use based on definedness.

The first argument is the value which should be defined or undefined.

The next arguments are: the string to use for a defined value, the string to use for a undefined value and an optional string for a defined value that is false (if none is given undefined uses the undefined value).

It can have “embedded args”.

    'Sorry, [is_defined,_2,“_2” is an invalid,you must specify a valid] value for “[_1]”.' 'domain', $domain
    # Sorry, “localhost” is an invalid value for “domain”.
    # Sorry, you must specify a valid value for “domain”.


The first argument is the same as the first argument to datetime(). Then comes the string for future and the string for false.

    Your session [is_future,_1,will expire,expired] on [datetime,_1,date_format_medium].


Embed comments in your phrases.

    'The transmogrifier has been constipulated to level “[_1]”[comment,The argument is the variable name containing the superposition of the golden ratio’s decimal place in relation to π as mildegredaded by the authoritative falloosifier.].'
    # The transmogrifier has been constipulated to level “☺”.


Include non-translatable text in your phrase, e.g. a proper name.

   'Thanks you for contacting [asis,Feel Good Inc.].'

This is a short-name alias to 'output,asis' so it can have embedded methods like any output() method.

   'Thanks you for contacting [asis,Foo chr(38) Barsup(®)].'

Does not support embedded args.


When you output a phrase you might mark it up by wrapping the string in, say, <p> tags. You wouldn't inlcude HTML *in* the key itself for a number of obvious reasons (HTML is not human, HTML is not the only possible output you may ever want, etc):

    print $lh->maketext('<p class="ok">Good news everyone!</p>'); # WRONG DO NOT DO THIS  !!
    print q{<p class="ok">} . $lh->maketext('Good news everyone!') . "</p>"; # good

What about when you want to format something inside the string? For example, you want to be sure certain words stand out. Or the argument is a URL that you want to be a link?

Again, you don't want to add formatting inside the string so what do you do? You use the output() method.

This method allows you to specify various output types. Those types allows a key to specify how a word or phrase should be output without having to understand or anticipate every possible context it might be used in.

   'What ever you do, do [output,strong,NOT] cut the blue wire!'
   'Your addon domain [output,underline,_1] has been setup.' 

Default output methods.

Each output method name is the second argument to output. e.g. if the output method is 'xyz' you'd use it like this [output,xyz,…] and define a new one like this 'sub output_xyz { … }'.

All output() methods support embedded methods: sub(), sup(), chr(), amp(), and numf(). Note: sub(), sup(), and numf() are simplified in that they only work with one argument.

These default bare bones methods support 3 contexts: HTML, ANSI, and plain text. See "output() context" below.

Feel free to over ride them if they do not suit your needs.

The terminal control codes were ripped from Term::ANSIColor but the module itself is not used.

Adding your own output methods

Output methods can be created (and overridden) simply by defining a method prefixed by output_ followed by the output type. For example in your lexicon class you would:

   sub output_de_profanitize {
       my ($lh, $word_or_phrase, $level, $substitute) = @_;
       return get_clean_text({
          'lang' => $lh->get_language_tag(),
          'text' => $word_or_phrase,
          'level' => $level,
          'character' => $substitute,

Then you can use this in your lexicon key:

   'Quote of the day "[output,de_profanitize,_1,9,*]"'

Your class can do whatever you like to determine the context and is by no means limited to 'plain' and 'html' types. Keys that are not context names (i.e. _type) should be preceded by an underscore.

Arbitrary name/value attribute list

Methods that support this feature are able to accept additional arguments treated as name/value pair attributes.

The idea is to embed ones that will likely not change and hopefully add to the meaning of the string.

    Your hair [output,inline,is on fire,class,urgent]!

After that list (or instead of it) a single hashref can be passed in. The intent here is to be able to do any arbitrary name/value that the caller might want to use but is likely to change and/or adds little meaning if any to the string.

output() context

Context as used here means what type of output we want based on where it will be happening at.

'html' will do output suitable for use in HTML code.

'ansi' will do output suitable for a terminal.

'plain' will do output without any sort of formatting.

Project example ^

Main Class:

    package MyApp::Localize;
    use Locale::Maketext::Utils; 
    use base 'Locale::Maketext::Utils'; 

    our $Encoding = 'utf-8'; 
    __PACKAGE__->make_alias([qw(en en_us i_default)], 1);

    our %Lexicon = (
        'Hello World' => 'Hello World', # $Onesided used to allow for 'Hello World' => '',

French class:

    package MyApp::Localize::fr;
    use base 'MyApp::Localize';
    our %Lexicon = (
        'Hello World' => 'Bonjour Monde',
    # not only is this too late to be of any use
    # but it's pointless as it already in essence happens since a failed NS 
    # lookup tries the superordinate (in this case 'fr') before moving on 
    # __PACKAGE__->make_alias('fr_ca');
    sub init {
        my ($lh) = @_;
        $lh->{'numf_comma'} = 1; # Locale::Maketext numf()
        return $lh;

Standard" .pm layout

In the name of consistency I recommend the following "Standard" namespace/file layout.

You put all of your locales in MainNS::language_code

You put any utility functions/methods in MainNS::Utils and/or MainNS::Utils::*

So assuming a main class of MyApp::Localize the files && name spaces would be:

   MyApp/Localize.pm                MyApp::Localize
   MyApp/Localize/Utils.pm          MyApp::Localize::Utils
   MyApp/Localize/Utils/Etc.pm      MyApp::Localize::Utils::Etc
   MyApp/Localize/Utils/AndSoOn.pm  MyApp::Localize::Utils::AndSoOn
   MyApp/Localize/fr.pm             MyApp::Localize::fr
   MyApp/Localize/it.pm             MyApp::Localize::it
   MyApp/Localize/es.pm             MyApp::Localize::es

If you choose to use this paradigm you'll have two additional methods available:


Returns the directory that correspnds to the base class's name space.

Again, assuming a main class of MyApp::Localize it'd be '/usr/lib/whatever/MyApp/Localize'


Returns a list of locales available. These are based on the .pm files in $lh->get_base_class_dir() that are not 'Utils.pm'.

They are returned in the order glob() returns them. (i.e. no particular order)

Assuming the file layout above you'd get something like (fr, it, es, ...)

This would be useful for creating a menu of available languages to choose from:

   my ($current_lookup, $native_lookup) = $lh->lang_names_hashref('en', $lh->list_available_locales());
   # since our main lexicon only has aliases (i.e. no .pm file): 
   #    we want the main language on top and we only want one of the aliases: the superordinate
   for my $langtag ('en', sort $lh->list_available_locales()) {
       if ($current_lookup->{$langtag} eq $native_lookup->{$langtag}) {
           # do menu entry like "Current $current_lookup->{$langtag} ($langtag)" # Currently English (en)
       else {
          # do menu entry like "$current_lookup->{$langtag} :: $native_lookup->{$langtag} :: ($langtag)" # Italian :: Italiano (it)

Tie::Hash::ReadonlyStack compat Lexicon

Often you'll want to add things to the lexicon. Perhaps a server's local version of a few strings or a context specific lexicon and using append_to_lexicons() and remove_key_from_lexicons() is too cumbersome.

Buy making your lexicon a Tie::Hash::ReadonlyStack hash we can do just that.

First we make our main lexicon:

    use Tie::Hash::ReadonlyStack;
    tie %MyApp::Localize::Lexicon, 'Tie::Hash::ReadonlyStack', \%actual_lexicon;

'%actual_lexicon' can be a normal hash or a specially tied hash (e.g. a GDBM_READER GDBM_File hash)

Next we add the server admin's overrides:

  $lh->add_lexicon_override_hash($tag, 'server', \%server);

When we init a user we add their override:

  $lh->add_lexicon_override_hash($tag, 'user', \%user);

Then we start a request and add request specific keys (perhaps a small lexicon package included with the module that implements the functionality for the current request) to fallback on if they do not exist:

  $lh->add_lexicon_fallback_hash($tag, 'request', \%request);

After the request we don't need that last one any more so we remove it:

  $lh->del_lexicon_hash($tag, 'request');

When the user context goes out of scope out we clean up theirs as well:

  $lh->del_lexicon_hash($tag, 'user');

If you choose to use this paradigm (via Tie::Hash::ReadonlyStack or a class implementing the methods in use below) you'll have three additional methods availble:

These methods all returns false if the lexicon is not tied to an object that implements the method necessary to do this. Otherwise they return whatever the tied class's method returns


This adds a hash to be checked before any others currently in the stack.

Takes 2 or 3 arguments. The language tag whose lexicon we are adding to, a short identifier string, and a reference to a hash. If the language tag is not specified or not in use in the current object the main lexicon is the one it gets asssigned to.

   # $lh is 'fr' and the main language is english, both are tied to Tie::Hash::ReadonlyStack
   $lh->add_lexicon_override_hash('fr', 'user', \%user_fr); # updated the 'fr' lexicon
   $lh->add_lexicon_override_hash('user', \%user_en); # updates main lexicon since no language was specified
   $lh->add_lexicon_override_hash('it', 'user', \%user_it); # updates main lexicon since 'it' is not in use in the handle 

Uses "add_lookup_override_hash()" in Tie::Hash::ReadonlyStack under the hood.


Like "add_lexicon_override_hash()" except that it adds the hash after any others currently in the stack.

Uses "add_lookup_fallback_hash()" in Tie::Hash::ReadonlyStack under the hood.


That attribute when true (e.g. set in init()) will cause the add_lexicon* methods to return true if the given name has been added before it tries to add them (which will return false since they exist already)

Care must be taken that you're not using the same identifier with different hashes or you some lexicons will simply not be added.

A better approach is to design your stack modifying logic so it doesn't try to add uplicate entries. This option is really only inteneded for debugging and testing.


This deletes a hash added via add_lexicon_override_hash() or add_lexicon_fallback_hash() from the stack.

Its arguments are the langtag and the short identifier string.

If langtag is not specified or is an '*' then it is removed from all lexicons in use.

If the specified langtag is not in use in the current object it gets removed from the main lexicon.

   $lh->del_lexicon_hash('fr', 'user'); # remove 'user' from the 'fr' lexicon
   $lh->del_lexicon_hash('*', 'user'); # remove 'user' from all the handle's lexicons
   $lh->del_lexicon_hash('user'); # remove 'user' from all the handle's lexicons
   $lh->del_lexicon_hash('it', 'user'); # remove 'user' from the main lexicon since 'it' is not in use

Uses "del_lookup_hash()" in Tie::Hash::ReadonlyStack under the hood.

Phrase Utils ^

See Locale::Maketext::Utils::Phrase::Norm for pragmatic examination and normalization of maketext phrase.

See Locale::Maketext::Utils::Phrase::cPanel for the same but via a cPanel recipe.

See Locale::Maketext::Utils::Mock for a mock object you can use for testing phrases.

See Locale::Maketext::Utils::MarkPhrase for a lightweight way to mark phrases in source code as translatable.


$ENV{'maketext_obj'} gets set to the language object on initialization ( for functions to use, see "FUNCTIONS" below ) unless $ENV{'maketext_obj_skip_env'} is true


Locale::Maketext::Pseudo has some exportable functions that make use of $ENV{'maketext_obj'} to do things like:

    use Locale::Maketext::Pseudo qw(env_maketext);
    env_maketext("Hello, my name is [_1]", $name); # use real object if we have one otherwise use pseudo object


Locale::Maketext, Locales::Language, Locale::Maketext::Pseudo, Text::Extract::MaketextCallPhrases

If you use "$lh-"lang_names_hashref()> or "$lh-"loadable_lang_names_hashref()> make sure you have the latest verison of Locales as 0.04 (i.e. Locales::Base 0.03) is buggy!


Audit that “Arbitrary name/value attribute list” is being used everywhere it makes sense to and that each use of it is documented.

Add in currently beta datetime_duration() ("LOCALIZATION of DateTime::Format modules" in DateTime::Format::Span and company)

Add in currently beta currency(), currency_convert()

Add more tests for v0.20: The changes have been in production outside of CPAN for a while, this was just a release to bring the CPAN verison up to date.


If you have an idea for a method that would fit into this module just let me know and we'll see what can be done


Daniel Muey, http://drmuey.com/cpan_contact.pl


Copyright (c) 2011 cPanel, Inc. <copyright@cpanel.net>. All rights reserved.

This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself, either Perl version 5.8.6 or, at your option, any later version of Perl 5 you may have available.

syntax highlighting: