Add Wikipedia processing and report

[oree-xx]

Fixes

• Fixes Add Wikipedia processing and reporting #232

Description

Added python scripts for processing and reporting wikipedia data.
Covered analysis around top 10 highest language usage, classification of represented and underrepresented languages, average count of article per language and percentage of all Wikipedia articles that belong to the top 10 languages.

Checklist

• I have read and understood the Developer Certificate of Origin (DCO), below, which covers the contents of this pull request (PR).
• My pull request doesn't include code or content generated with AI.
• My pull request has a descriptive title (not a vague title like Update index.md).
• My pull request targets the default branch of the repository (main or master).
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no
  visible errors.

Developer Certificate of Origin

For the purposes of this DCO, "license" is equivalent to "license or public domain dedication," and "open source license" is equivalent to "open content license or public domain dedication."

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[oree-xx]

@TimidRobot I am considering classifying the languages by regions. Would that be quite meaningful?

[TimidRobot]

@TimidRobot I am considering classifying the languages by regions. Would that be quite meaningful?

Please provide more information on what the API provides regarding regions

Rather, the data file doesn't have any region information. The processing phase shouldn't fetch any additional information. If there is region data, the fetch script needs to be updated. Though, given the various diasporas, I'm skeptical that region information is helpful.

[oree-xx]

@TimidRobot I am considering classifying the languages by regions. Would that be quite meaningful?

Please provide more information on what the API provides regarding regions

Rather, the data file doesn't have any region information. The processing phase shouldn't fetch any additional information. If there is region data, the fetch script needs to be updated. Though, given the various diasporas, I'm skeptical that region information is helpful.

Ohh okay.

[TimidRobot]

I also think think you should update and reorder plots:

1. "Language representation" (renamed to use Sentence case)
2. "Most represented languages" (rename from "Top 10 Highest Language Usage")
3. "Least represented languages" (new, be sure to note that it only includes languages with at least 1 article)

[TimidRobot]

We use sentence case for titles and headings because we generally follow the Google developer documentation style guide.

Capitalization in titles and headings  |  Capitalization  |  Google developer documentation style guide  |  Google for Developers:

In document titles and headings, use sentence case. That is, capitalize only the first word in the title, the first word in a subheading after a colon, and any proper nouns or other terms that are always capitalized a certain way.

Even though you're using sentence case, don't put a period at the end of a title or heading.

Sentence case improves readability and allows consistent capitalization (otherwise knowing which words to capitalize can become quite hard to remember).

See also: Documentation Guidelines — Creative Commons Open Source

[TimidRobot]

Good work, thank you!