view release on metacpan or  search on metacpan

README  view on Meta::CPAN

            'CF.Service Tag' => 'serviceTag',
            'CF.Serial #'    => 'serialNo',
        );

    This requires that, after the import, RT becomes the generator of all
    asset ids. Otherwise, asset id conflicts may occur.

  Configuring Text::CSV_XS
    This extension is built upon Text::CSV_XS, which takes a number of
    options for controlling its behavior. You may have a different field
    delimiter, or byte-order-marking (BOM), for example, and need to enable
    configuration to support it. Options set in %AssetsImportParserOptions
    will be passed directly to new() in Text::CSV_XS:

        Set( $AssetsImportParserOptions, {
            binary     => 1,
            detect_bom => 1,
            sep_char   => '|',
        });

    The only default option is binary => 1. More information is available in

inc/YAML/Tiny.pm  view on Meta::CPAN

        if ( utf8::is_utf8($string) && ! utf8::valid($string) ) {
            die \<<'...';
Read an invalid UTF-8 string (maybe mixed UTF-8 and 8-bit character set).
Did you decode with lax ":utf8" instead of strict ":encoding(UTF-8)"?
...
        }

        # Ensure Unicode character semantics, even for 0x80-0xff
        utf8::upgrade($string);

        # Check for and strip any leading UTF-8 BOM
        $string =~ s/^\x{FEFF}//;

        # Check for some special cases
        return $self unless length $string;

        # Split the file into lines
        my @lines = grep { ! /^\s*(?:\#.*)?\z/ }
                split /(?:\015{1,2}\012|\015|\012)/, $string;

        # Strip the initial YAML header

lib/RT/Extension/Assets/Import/CSV.pm  view on Meta::CPAN

        'CF.Serial #'    => 'serialNo',
    );

This requires that, after the import, RT becomes the generator of all
asset ids.  Otherwise, asset id conflicts may occur.

=head2 Configuring Text::CSV_XS

This extension is built upon L<Text::CSV_XS>, which takes a number of
options for controlling its behavior. You may have a different
field delimiter, or byte-order-marking (BOM), for example, and need to
enable configuration to support it. Options set in
C<%AssetsImportParserOptions> will be passed directly to C<new()> in
L<Text::CSV_XS>:

    Set( $AssetsImportParserOptions, {
        binary     => 1,
        detect_bom => 1,
        sep_char   => '|',
    });