I hope you are not really going to insist on using data file names that include spaces and parentheses ("1 (1).txt" and so on) as either input files or output files. That makes lots of things a lot more difficult for command-line usage involving file names (everything would need to be quoted and/or escaped). Please stick to alphanumerics, underscore, hyphen and period for file names.

I understand the difficulty of trying to write documentation in a foreign language. I hope you will have a chance to go over it with someone who knows both your native language and English well enough so that you can discuss the module comfortably with them, and they can clarify the English description. As it is, I would have to read the program code to understand how to use the module. (You might want to consider posting (a pointer to) the code for preliminary review by other monks.)

It may be worthwhile to create a CPAN layer called "Text::Corpus::", which at first would contain just a "Stats" module (Text::Corpus::Stats), and later could contain other support modules for building, maintaining and using text corpora.

In reply to Re: help for naming a module that aims latin utf8 coded corpus statistical analysis by graff
in thread help for naming a module that aims latin utf8 coded corpus statistical analysis by fernandes

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.