GSoC 2021 Proposal: Translation System Refinements
Name: Yogesh Sharma
Personal Email: firstname.lastname@example.org
Affiliation: Bharati Vidyapeeth's College of Engineering, New Delhi
Location: New Delhi, India
Timezone: Indian Standard Time (UTC +05:30)
Abstract/summary (<20 words):
In plots2 internationalization (i18n) system exists but lacks a consistent workflow for importing new translations, as well as some issues such as HTML parsing and UI shortcomings.
What problem(s) does your project solve?
Currently, the internationalization system exists but there are a few problems such as issues with CSS alignment, missing translations, improper HTML parsing so it's difficult to see proper localization support in publiclab.org which might trouble the users across the globe due to lack of multi-language support. All these problems will be solved by this project.
Note: All the mockups/prototypes and code samples are just for reference. They can be revised/updated according to the requirements of the project, moderator preferences, or suggestions given by mentors.
1. Refine the custom translation helper
We need to refine this translation helper. The existing helper looks something like this
Ways to refine the translation assistant above...
As for now, the translation link is not working yet it is directed to 404 pages.
2. Resolving HTML parsing issues
- Here all we need to make sure we are within the HTML attribute and not include too much HTML in these attributes.
3. Improving CSS of missing translation prompt
Well Initially, CSS translation information needs to be adjusted to the items below
In the header Currently, translation information is provided in a separate tag, moving it to the title tag on the topic will fix the problem. This problem, therefore, arises as a result of Prompt's rendering of the translation.
Share your work dropdown
In this share your work dropdown has a bug while we inspect the web page this dropdown moves upwards under the navbar.
Currently, in the footer where we select the language to be translated from the Language dropdown, it should appear within the footer section in an upward direction but it comes up and crosses the footer section downwards.
4. Page to recruit translators and document
Below are some of the changes that will be made as part of the project -
[Preview under process]
The same topic to follow.
This section will list all the details - in relation to translation projects and the nature of the work done and all previous details to be considered.
This section will contain a form for those interested in joining as a translator, who need to provide basic information on the form for details to be reviewed and verified. And the process will be done.
The same topic as follows just needs to fix that language section bug.
5. Write and provide a workflow guide for code-related tasks for translation import
- Write in Readme itself how internal performance works on the platform.
- Along with that, use GitBook to record individual job details.
6. Improve workflow with first-time problems only based on the translation
- Easy self-testing translation
- Prepare drag-and-drop request for update: New translation template, add translation mark to the problem. And the guidelines on the PR template if it is for translation. It will help to separate translation and PR issues. Translators can submit comments to the PR itself for review by the translation community and maybe compiled over time.
Places where the translation is needed to be added.
https://publiclab.org/post: As this page is very important and helps members of the public to create posts, edit their writing so there is a need to submit translations to this page.
Footer: The website footer needs to be translated as a header.
I will need guidance from my counselors. suggestions or feedback from all members of the PublicLab will be positive and will help me build, complete my project and contribute to the community.
I personally started my contribution by working on the first issue only on Image-sequencer and community-toolbox, and since then the Public Lab community has been supporting me. I have been an active member of Public Lab for the past year.
Also, I have done a good number of contributions in the Public lab in the community toolbox. And helping new fellows in contribution fix issues along with them participating in discussions, welcoming new contributors, and much more.
PRs in community-toolbox
1. New Navbar added with the logo of PublicLab (#420)[merged]
2. Public lab dependency chart (#424)[merged]
3. Dependency chart is added to the navbar (#434)[merged]
4. Language section added to home page (#422)[merged]
5. Formate of web page is fixed (#441)[merged]
6. Language section is added into the navbar (#447)[merged]
PR in Image-sequencer
1. Link Updated(publiclab/chatroom link is add in index.html page)(#1627)[merged]
Well Regarding Public Lab, I have gained a lot of experience and guidance from every member of the PublicLab especially @jywarren and Working in Public Lab has been a great journey for me till now and I hope the same for the future as well.
I started working with Public Lab as I really liked the concept of the public lab, the work they do for the environment, and the young people who open the source. Having a speaker where people can share their ideas and environmental research work on other projects like community toolbox, photo sequence. This reflects the diversity of nature and cares for the environment. All of this encourages me to work with the community.
_Plots project helps every user as it provides users to share their ideas in terms of posts and comments and also gives the ability to translate the website contents to their native languages. _
Do you understand this is a serious commitment, equivalent to a full-time summer job? Tell us how you'll structure your schedule from day today!
_Yes, I fully understand that this is a huge commitment and I am able to devote 6-7 hours every day to complete this project. According to the college education calendar, I have no dispute with the timeline and if anything arises I will be sure to inform my counselors about it.
Hi @Yogesh! Thanks so much for your proposal!
I added a note also to https://github.com/publiclab/plots2/issues/9257 with thanks for your research on the 404 error, with a recommendation there.
And I wanted to point out my comment at https://github.com/publiclab/plots2/issues/9257#issuecomment-816836984 which is relevant to your proposal as well!
I like the examination of the first 2 more technical issues. I'm curious for your thoughts on the part about coordinating translators, onboarding them, the social and cooperative parts! What do you think about building out the guidance at https://publiclab.org/wiki/translation and developing a group/topic on PublicLab.org to coordinate different language translations? What are some ways we can make this process inviting and supportive, and to have good communication all along the workflow, from noticing an untranslated text or missing language all the way to publishing new translations to the site?
Thanks a lot Yogesh!!!!
Is this a question? Click here to post it to the Questions page.
It's a great idea about building out the guidance at https://publiclab.org/wiki/translation from noticing an untranslated text to all the way to publishing new translations to the site. Thanks a lot, @warren sir 😊.
Reply to this comment...
Log in to comment
And be sure to check out my thoughts on a test suite for different translation helpers in my comment here! https://publiclab.org/notes/ajitmujumdar25999/04-05-2021/gsoc-proposal-2021-translation-system-refinement#c28483 -- thanks!
Reply to this comment...
Log in to comment
Login to comment.