{ "content": [ { "type": "text", "text": "# Date::Manip::Lang (perldoc)\n\n## NAME\n\nDate::Manip::Lang - language support for Date::Manip\n\n## DESCRIPTION\n\nDate::Manip supports a number of different languages when parsing dates, and more can be added.\n\n## Sections\n\n- **NAME**\n- **DESCRIPTION**\n- **CURRENT LANGUAGES**\n- **ADDING A LANGUAGE**\n- **SEE ALSO**\n- **LICENSE**\n- **AUTHOR**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "Date::Manip::Lang", "section": "", "mode": "perldoc", "summary": "Date::Manip::Lang - language support for Date::Manip", "synopsis": null, "tldr_summary": null, "tldr_examples": [], "tldr_source": null, "flags": [], "examples": [], "see_also": [], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "DESCRIPTION", "lines": 2, "subsections": [] }, { "name": "CURRENT LANGUAGES", "lines": 29, "subsections": [] }, { "name": "ADDING A LANGUAGE", "lines": 68, "subsections": [] }, { "name": "SEE ALSO", "lines": 2, "subsections": [] }, { "name": "LICENSE", "lines": 3, "subsections": [] }, { "name": "AUTHOR", "lines": 2, "subsections": [] } ], "sections": { "NAME": { "content": "Date::Manip::Lang - language support for Date::Manip\n", "subsections": [] }, "DESCRIPTION": { "content": "Date::Manip supports a number of different languages when parsing dates, and more can be added.\n", "subsections": [] }, "CURRENT LANGUAGES": { "content": "Currently, the following languages are supported by Date::Manip. The version of Date::Manip\nwhere they were added is included (so you can see the minimum version of Date::Manip needed to\nparse each).\n\nThe language can be chosen by setting the Language config variable to the name of the language\nor any of the aliases included in the table.\n\nAll names and aliases are case insensitive.\n\nLanguage Version Aliases\n\nEnglish default en, enus\n\nCatalan 5.43 ca\nDanish 5.41 da\nDutch 5.32 Nederlands, nl\nFinnish 6.31 fi, fifi\nFrench 5.02 fr, frfr\nGerman 5.31 de, dede\nItalian 5.35 it, itit\nNorwegian 6.21 nb, nbno\nPolish 5.32 pl, plpl\nPortuguese 5.34 pt, ptpt\nRomanian 5.35 ro, roro\nRussian 5.41 ru, ruru\nSpanish 5.33 es, eses\nSwedish 5.05 sv\nTurkish 5.41 tr, trtr\n", "subsections": [] }, "ADDING A LANGUAGE": { "content": "Adding a language is easily done (if you're fluent in both English and the other language). If\nyou want to add a new language, do the following:\n\nLanguage name\nWhen you submit the new language, I'll need the name of the language (of course) and any\ncommon locale names that might be useful for people to select the language.\n\nFor example, if you were creating a Spanish translation (which is not necessary since it\nalready exists), I would need the following list:\n\nspanish es eses\n\nCopy the english module\nCopy the english.pm file (which is in lib/Date/Manip/Lang in the Date::Manip distribution)\nto the new language (i.e. spanish.pm in this example).\n\nSet some variables in the new module\nThe new module (spanish.pm) will need a few simple modifications. Change the package name\nfrom 'english' to 'spanish'.\n\nFix the @Encodings lines. Most languages can be written in more than one encoding. The first\nencoding in the list should be utf-8 and the last should be perl. Include any other\nencodings that should be supported as well.\n\nSet the $YearAdded and $LangName appropriately.\n\nTranslate the language terms\nThe data section of the module is fairly straightforward to translate.\n\nEvery term is defined in the Date::Manip::Lang::english document (or in any of the other\nlanguage module documents), so please refer to it to find out what each element means. Then\nreplace the English version with the new translation.\n\nThere are some requirements:\n\n1) Every element should be defined (except for the sephm and sepms elements which are\noptional).\n\n2) The module must be written using UTF-8 characters if the language includes any non-ASCII\ncharacters.\n\n3) Each element includes a list of values (different variations of the element). In most\ncases, the order of the values for each element is not important since they are just used to\ncreate a regular expression for parsing dates, but a few of them are also used to determine\nprintable values using the \"Date::Manip::Date::printf\" method (or the \"UnixDate\" function).\nThese elements are:\n\nElement printf directive\n\nampm %p\ndayabb %a\ndaychar %v\ndayname %A\nmonthabb %b\nmonthname %B\nnth %E\n\nFor each of these, the value that should be printed out must be the first value in the list.\n\n4) When possible, if a language includes characters that are essentially ASCII characters\nwith a punctuation mark, please include a variation of the value which is just ASCII with\nthe punctuation removed. For example, the spanish name for Saturday in ASCII would be\nwritten sabado, but in reality, the first 'a' has an accent over it. This word should appear\ntwice... first in full UTF-8 encoding, and second as all ASCII. If the language (Russian for\nexample) has no ASCII equivalent, just include the UTF-8 representation.\n\nFeel free to contact me if you have any questions.\n", "subsections": [] }, "SEE ALSO": { "content": "Date::Manip - main module documentation\n", "subsections": [] }, "LICENSE": { "content": "This script is free software; you can redistribute it and/or modify it under the same terms as\nPerl itself.\n", "subsections": [] }, "AUTHOR": { "content": "Sullivan Beck (sbeck@cpan.org)\n", "subsections": [] } } } }