apertium / apertium-html-tools

Web application providing a fully localised interface for text/website/document translation, analysis and generation powered by Apertium.
http://wiki.apertium.org/wiki/Apertium-html-tools
GNU General Public License v3.0
41 stars 89 forks source link

Added Hindi and Santali language Translations #425

Closed Prasanta-Hembram closed 2 years ago

coveralls commented 2 years ago

Pull Request Test Coverage Report for Build 1666167624


Totals Coverage Status
Change from base Build 1652805859: 0.0%
Covered Lines: 1355
Relevant Lines: 1370

💛 - Coveralls
Prasanta-Hembram commented 2 years ago

I too was busy for this new year eve no issue :-) . Thanks @sushain97 for suggesting me to make change, i hope that i have done everything good :-). Also, i want to know how to test those translations. Followed this guide https://wiki.apertium.org/wiki/Apertium-html-tools but unable to test my translations. Index file present is the src folder is not working.

sushain97 commented 2 years ago

Also, i want to know how to test those translations. Followed this guide https://wiki.apertium.org/wiki/Apertium-html-tools but unable to test my translations. Index file present is the src folder is not working.

The instructions are here: https://github.com/apertium/apertium-html-tools#contributing

Prasanta-Hembram commented 2 years ago

Thanks for the help @sushain97 but i encountered some error here,

Problem No.1) I have successfully installed Node.js and Yarn but after giving yarn install --dev command i get error which I'm not able to fix. Error is as follows below, for which built is not successful for me. Just want to view the site in html for newly added language, any shortcut ?? or in order to fix what further steps are needed (detailed beginner guide is recommended :-))

yarn install --dev yarn install v1.22.17 warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json. [1/4] Resolving packages... [2/4] Fetching packages... [-----------------------------------------------------------------------] 1/757Segmentation fault

Problem 2) Also, i was testing for the newly created https://github.com/Prasanta-Hembram/apertium-eng-sat and tested with https://wiki.apertium.org/wiki/Apertium-apy but seems to fail (not able to detect the language pair). Any idea how to make it work.

sushain97 commented 2 years ago

Problem No.1) I have successfully installed Node.js and Yarn but after giving yarn install --dev command i get error which I'm not able to fix. Error is as follows below, for which built is not successful for me. Just want to view the site in html for newly added language, any shortcut ?? or in order to fix what further steps are needed (detailed beginner guide is recommended :-))

Hm, I have a suspicion that you're using Yarn v2 instead of Yarn v1.

You could try these instructions instead: https://github.com/apertium/apertium-html-tools#building.

Combine the docker build with yarn serve or just directly accessing the built index.eng.html.

Prasanta-Hembram commented 2 years ago

Thanks @sushain97 for the help i have set Yarn v1 and the build is successfull. I have also updated my translations, and everything is ready now. I hope i have commited well !! We can close this long pull :-)...

Prasanta-Hembram commented 2 years ago

Also, how to translate these languages Screenshot 2022-01-06 204452 I found https://github.com/apertium/apertium-apy/tree/master/language_names but still confused where to add these language translations. May be most probably in "manual-additions.tsv"?? For Santali language should i create a new tsv file or add it to there too.

sushain97 commented 2 years ago

Also, how to translate these languages Screenshot 2022-01-06 204452 I found https://github.com/apertium/apertium-apy/tree/master/language_names but still confused where to add these language translations. May be most probably in "manual-additions.tsv"?? For Santali language should i create a new tsv file or add it to there too.

Here are the directions: https://github.com/apertium/apertium-apy/tree/master/language_names#manual---edit

Prasanta-Hembram commented 2 years ago

Again, Thanks @sushain97 i will also update those language in apy repo. I will try to correct my error anyhow. I hope i have deleted correct files.

Prasanta-Hembram commented 2 years ago

Also, how to translate these languages Screenshot 2022-01-06 204452 I found https://github.com/apertium/apertium-apy/tree/master/language_names but still confused where to add these language translations. May be most probably in "manual-additions.tsv"?? For Santali language should i create a new tsv file or add it to there too.

Here are the directions: https://github.com/apertium/apertium-apy/tree/master/language_names#manual---edit

Manual - EDIT

**manual-fixes.tsv** contains fixes to the scraped data.
**manual-additions.tsv** contains additions to the scraped data.
variants.tsv contains fixes/additions to the scraped data for language variants.
turkic.tsv contains Turkic language names.

N.B. Due to historical reasons, there are currently some additions in manual-fixes.tsv.

So, HIndi language locale translation should go to manual-fixes.tsv and Santali language locale translations (new language in apy) should be in manual-additions.tsv or both should be in which files if I'm wrong??

sushain97 commented 2 years ago

So, HIndi language locale translation should go to manual-fixes.tsv and Santali language locale translations (new language in apy) should be in manual-additions.tsv or both should be in which files if I'm wrong??

Updates to existing language names should go in fixes and new one should go in additions.

Prasanta-Hembram commented 2 years ago

HI, @sushain97 can you check again i have made some changes.

sushain97 commented 2 years ago

Could you revert the changes to package.json and yarn.lock?

Prasanta-Hembram commented 2 years ago

package.json and yarn.lock?

can you again check?