Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

localize(1p) [opensolaris man page]

LOCALIZE(1p)						User Contributed Perl Documentation					      LOCALIZE(1p)

localize -- produce Interchange localization file from set of pages VERSION
# $Id: localize.PL,v 2.11 2007-08-09 13:40:57 pajamian Exp $ SYNOPSIS
"localize -l lg_CC [-d lg_CC] [-m file|-t] file [file2 file3 ...]" DESCRIPTION
Helps manage Interchange pages by finding, adding, and merging localization strings. OPTIONS
"-c" Rewrite [L] sections with [LC]text[do_DO]text[/do_dO], adjust file and data -- mutually exclusive with "-o". "-d lg_CC" Create default domain file with Locale lg_CC as prefix "-l lg_CC" Create file with Locale lg_CC as prefix. This is mandatory unless in -c mode with "-m" option. "-m file" Read existing information to merge from <file>. Can contain multiple locales. "-M" When in "-c" mode, prefix MM_ to make minimate_compatible; when in regular mode, strip MM_ from [LC] defs "-n" Don't write comments in the output. "-o" Rewrite [L] sections with [L msgNNNN], adjust file and data. Mutually exclusive with "-c". "-t" Two page mode, mutually exclusive with "-m." "-u dir" Directory with (UI) menu database files, e.g. "/usr/lib/interchange/lib/UI/pages/includes/menus". This can be used to include the menu titles in the output. lg_CC refers to the POSIX norm of specifying two-letter language and country codes to refer to a locale. Two-page mode requires two files (one for each language) to compare and merge into one locale definition. The merge file for the "-m" option should use the Perl reference form -- see the Interchange documentation for more information. If [L msg_key]default text[/L] keys are found, will produce a comment with the default text for reference. A backup file (filename.html.bak) is saved if "-o" is used, but only one level. Subsequent .bak files will be overwritten. SEE ALSO AUTHOR
Mike Heins and Stefan Hornburg perl v5.14.2 2012-01-23 LOCALIZE(1p)

Check Out this Related Man Page

Vend::Payment::iTransact(3pm)				User Contributed Perl Documentation			     Vend::Payment::iTransact(3pm)

Vend::Payment::iTransact - Interchange iTransact Support SYNOPSIS
&charge=itransact or [charge mode=itransact param1=value1 param2=value2] PREREQUISITES
Net::SSLeay or LWP::UserAgent and Crypt::SSLeay Only one of these need be present and working. DESCRIPTION
The Vend::Payment::iTransact module implements the itransact() routine for use with Interchange. It is compatible on a call level with the other Interchange payment modules. To enable this module, place this directive in "interchange.cfg": Require module Vend::Payment::iTransact This must be in interchange.cfg or a file included from it. Make sure CreditCardAuto is off (default in Interchange demos). The mode can be named anything, but the "gateway" parameter must be set to "itransact". To make it the default payment gateway for all credit card transactions in a specific catalog, you can set in "catalog.cfg": Variable MV_PAYMENT_MODE itransact It uses several of the standard settings from Interchange payment. Any time we speak of a setting, it is obtained either first from the tag/call options, then from an Interchange order Route named for the mode, then finally a default global payment variable, For example, the "id" parameter would be specified by: [charge mode=itransact id=YouriTransact] or Route itransact id YouriTransactID or Variable MV_PAYMENT_ID YouriTransactID The active settings are: id Your iTransact account ID, supplied by iTransact when you sign up. Global parameter is MV_PAYMENT_ID. home_page The internet address of your site. Defaults to "http://__SERVER_NAME__" if not set. Global parameter is MV_PAYMENT_HOME_PAGE. remap This remaps the form variable names to the ones needed by iTransact. See the "Payment Settings" heading in the Interchange documentation for use. Troubleshooting Try the instructions above, then enable test mode. A test order should complete. Then move to live mode and try a sale with the card number "4111 1111 1111 1111" and a valid expiration date. The sale should be denied, and the reason should be in [data session payment_error]. If nothing works: o Make sure you "Require"d the module in interchange.cfg: Require module Vend::Payment::iTransact o Make sure either Net::SSLeay or Crypt::SSLeay and LWP::UserAgent are installed and working. You can test to see whether your Perl thinks they are: perl -MNet::SSLeay -e 'print "It works "' or perl -MLWP::UserAgent -MCrypt::SSLeay -e 'print "It works "' If either one prints "It works." and returns to the prompt you should be OK (presuming they are in working order otherwise). o Check the error logs, both catalog and global. o Make sure you set your account ID properly. o Try an order, then put this code in a page: <XMP> [calc] my $string = $Tag->uneval( { ref => $Session->{payment_result} }); $string =~ s/{/{ /; $string =~ s/,/, /g; return $string; [/calc] </XMP> That should show what happened. o If all else fails, consultants are available to help with integration for a fee. See BUGS
There is actually nothing *in* Vend::Payment::iTransact. It changes packages to Vend::Payment and places things there. AUTHORS
Mark Johnson and Cameron Prince, based on original code by Mike Heins. perl v5.14.2 2011-03-09 Vend::Payment::iTransact(3pm)
Man Page

Featured Tech Videos