DateTime-Format-Japanese 0.03
- Released by
- DMAKI
- Version
- Release Date
- 2006-07-06
- Kwalitee
- 137.5
- Core Kwalitee
- 90.62
- LINKS
DateTime-Format-Japanese 0.03
Kwalitee Issues
- has_human_readable_license
-
Add a section called "LICENSE" to the documentation, or add a file named LICENSE to the distribution.
- has_license_in_source_file
-
Add =head1 LICENSE and the text of the license to the main module in your code.
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: DateTime-Format-Japanese-0.03/lib/DateTime/Format/Japanese/Traditional.pm -- Around line 401: Non-ASCII character seen before =encoding in '$fmt->parse_datetime("Ãç²½»°Ã¯Ãïø»°Ãü±¯»°¤Ã¹ï");'. Assuming CP1252 DateTime-Format-Japanese-0.03/lib/DateTime/Format/Japanese.pm -- Around line 507: Non-ASCII character seen before =encoding in '$fmt->parse_datetime("ÿ£¶Ã¯£±·î£²£·Ãü¸á𣵻þ£³£°Ã¬");'. Assuming CP1252
- meta_yml_declares_perl_version
-
If you are using Build.PL define the {requires}{perl} = VERSION field. If you are using MakeMaker (Makefile.PL) you should upgrade ExtUtils::MakeMaker to 6.48 and use MIN_PERL_VERSION parameter. Perl::MinimumVersion can help you determine which version of Perl your module needs.
- has_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- has_known_license_in_source_file
-
Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.
- use_warnings
-
Add 'use warnings' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.
Error: DateTime::Format::Japanese, DateTime::Format::Japanese::Common, DateTime::Format::Japanese::Traditional
- meta_yml_has_repository_resource
-
Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).
- has_separate_license_file
-
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.
- has_security_doc
-
Add SECURITY(.pod|md). See Software::Security::Policy.
- security_doc_contains_contact
-
Add SECURITY(.pod|md) and add a contact address. See Software::Security::Policy.
- has_contributing_doc
-
Add CONTRIBUTING(.pod|md). See https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.