Suggestion for beginner issues

[BHK4321]

Hello @grhoten,
Please answer this according to your convenience,
I searched for tags like good first issue, beginner-friendly, help wanted, and first-timers-only, but I couldn't find any relevant issues to work on.
As a newcomer to open source, I am looking for beginner-friendly issues in unicode to contribute to. Could you suggest any tasks I can work on?

[grhoten]

I see that you already applied to one of the projects in GSoC. That's a good first step. Beginner is a relative term. If you have C or C++ skills, then your interest in issue #87 may be just right for you.

If you're looking for something that requires the least programming expertise, or are interested in participating separately from GSoC, you may want to consider contributing lexeme data to Wikidata. Such a task is better suited towards people that have deep knowledge of another language. When contributing such data to Wikidata, the contributions are contributed as CC0 or public domain. Anyone can use that data freely without restrictions. This kind of task is a prerequisite for adding support for a new language.

When such data is added to Wikidata, it lowers the effort for this project to add support for such a language. So if you want this project to support a language that you care about, adding data for that language helps out a lot.

What is this project about?

You may want to familiarize yourself with the videos located in the Readme. That provides some good background information.

Which language to support?

There is a list of languages that this project is interested in supporting. You can still add data for another language that interests you. That list provides some guidance on what will be the focus in the near term. If it's higher on the list, there is more interest in supporting that language. Ideally, we want to see at least 10,000 words supported for a given language.

What words should be added?

Here is a guidance on what to add:

• Generally avoid adding multiword phrases. They can be supported by inflecting individual words instead.
• Try to add forms under the same lexeme (lemma) where you're just modifying the grammatical properties of that word.
• Do not try to structure the forms under a lemma that relates to word structure in a sentence. The location of a word in a sentence is managed outside the scope of Unicode Inflection. For example, if a noun is definite or indefinite, and that would change the word order, you can note the word form being definite or indefinite. Just don't try to find a way to convey that it it's supposed to go before or after a verb. Word ordering is a separate topic, and it's better handled outside of this project.
• If a word doesn't exist for a state of grammatical features, don't add it to the lexeme. Don't put dummy text in the lexeme either. For example, if a word is never singular, then don't add any form that is singular.
• If the word choice for a person varies depending on the physical gender of a person, you should consider putting it under the same lemma. For example, if I'm referring to an actor or actress, and I know the gender of that person, then I need to inflect the word under a given lemma describing that person to reflect that person's gender.
• It's recommended to start adding higher frequency words. Here are some lists to consider where to start.
  • Unilex word frequency
  • Any words in CLDR.
  • Wiktionary word frequency lists
  • Maybe others...
• You can look at an overview of what words are already in Wikidata for insight on what parts of speech may be underrepresented.

How to contribute to Wikidata?

You will need to sign up for an account. After you have an account, you can start contributing words. While using the web interface is possible, it can get rather tedious when adding a lot of words. If your language is supported, you may want to consider using a template. This will allow you to just fill in the words without searching for the grammatical feature names for each form.

Adding support for a new language

There is a document about how to add support for a new language. It's a work in progress. This kind of task may be less suited for a complete beginner. I'd only recommend looking at this documentation if there is enough available data from Wikidata for the language of interest. I probably need to add more documentation to it about how to use the dictionary-parser.

When supporting a language, there is also a task for completely supporting RBNF (Rule Based Number Format). That's a topic for another time though. It takes time to explain it. The Number Format Tester helps with writing such rules, and the rules are submitted to CLDR for inclusion when the rules are completed.

I can elaborate more if needed. I hope you find this information helpful.

[BHK4321]

Thankyou @grhoten for your detailed response ,

It was a hectic day so i express apology for the delay,

I applied to the #87 Project because it was aligning with my skills and my interests , so as you mentioned #87 is well suited for me as :
i am really good in C and C++ as i have been doing Competitive Programming too , i can mention the profile in the proposal.

The adding support for a new language task is quite interesting and i would try my best to add some support to the languages English and Hindi , as Hindi is my native language and i am quite proficient with English too.
I viewed all the links you included for adding support for languages , so once i confirm what i want to add to the lemmas or addition of words into the CLDR and similar resources , i will get back to you with the pull requests.

Moreover, i read the Readme file you mentioned for the UTW videos ,the Platforms do not include Windows so will it interrupt with the processes in the project #87 as I am a Windows user ?
And if it is a dependency then i would install any OS of Linux as suggested.

Thankyou.

[BHK4321]

Hello , I have a pull request in the CLDR repo FeatureName addition.
It was quite basic would love to contribute more.
Please review the same.
Thankyou

[grhoten]

As far as CLDR contributions, there is already a process involved with vetting and contributing such data. I recommend closing your pull request and going through the official channels. I recommend checking out https://cldr.unicode.org/#how-to-contribute for more details.

[BHK4321]

Okay , I will look into it.

[BHK4321]

Hello Sir,

I have submitted and updated the proposal for #87 based on my best understanding from various references and repositories. I would sincerely appreciate it if you could review my proposal and provide your feedback.

Thank you.