[Planning] Translation System Refinement

[imajit]

I have not completely planned this out yet but these are some parts I'll work on :

• UI Issues with Translation icon
  • Fix position of icon
  • Improve pop-up
  • Fix UI
• Translation function improvement
  • Handle inline function calls
  • Positioning and visibility of icon
  • Reduce Icon Count
  • Handle empty strings in translation files
  • Dialect Support [Discussion Dialects in Transifex #9809 ]
• Tests for translation function
  • Tests for new changes in Translation function
  • Tests for UI changes
  • Tests for FTO related changes
• Setting up workflow to import translations
  • Create a dummy project to safely test integration
  • Export Strings from Github Repo to Transifex
  • Importing Reviewed strings from Transifex
• Translation Dashboard and Community box section
  • Add FAQ section to existing wiki page
• Test for FTOs issue
  • Verify UI changes in Gitpod
  • FTO issue template
  • Launch Browser in Gitpod
• Add Documentation
  • New Translation Function
  • UI verification in Gitpod
  • Transifex integration
    I'll add subtasks and other tasks. Feel free to add new ideas/tasks 😄

[jywarren]

These are looking good! Many may break out into subtasks, agreed! As you go, you might convert some into headings instead of tasks. Cool!

[jywarren]

I also linked you to https://github.com/publiclab/plots2/milestone/22, and if you want we can make this issue the new "lead" issue there by reordering and mentioning it in the description!

[Tlazypanda]

Hey @imajit Nice breakdown 💯 Here is a comment that I made on @Manasa2850 planning issue that might be helpful - #9694 (comment)

Also It might be helpful for both of you to go through each other's planning issue and help brainstorm. Brownie points for finding overlap if any and handling that or expanding your proposals a bit to get some new ideas onboard. Thank you! Have fun 🎊

[imajit]

On the site there a lot of buttons where the translation function is called as we cannot nest one button inside another, the globe icon occurs besides the button. I can change it such that both text and globe icon is inside a single button but I read on the internet that nesting two anchor tags is not considered a good practice and I would have to restyle every button where this happens which would be a lot of changes site-wide. In some cases the buttons are also too small and having a nested globe icon would make things even more compact. If I remove the nested globe then there will be a considerable reduction in the number of globe icons from the site. So wanted to know your views. Should I change each button or just have make it a simple button with no nesting?
@jywarren @Tlazypanda @RuthNjeri @cesswairimu @grvsachdeva @keshavsethi

[ebarry]

Thank you Ajit, nice to chat through forum ideas today. Interested to hear if you developed any more perspectives?

[imajit]

Thank you Ajit, nice to chat through forum ideas today. Interested to hear if you developed any more perspectives?

Hey! I think the existing Translation process works well for recruiting new translators, can we get an opinion from the existing translators about what they feel can be added or what they feel is missing, I can work on that. Also, I think we can get more contributors for translation if we advertise about it #9659 (comment) , would love to hear your views on that too

[imajit]

Also, there are some simple string replacement changes that can be very good candidates for ftos, I'll make some ftos for this, this can be helpful in understanding what tests I need to add to make translation based ftos easy to review and merge. Thanks @grvsachdeva for this suggestion 💯

[RuthNjeri]

On the site there a lot of buttons where the translation function is called as we cannot nest one button inside another, the globe icon occurs besides the button. I can change it such that both text and globe icon is inside a single button but I read on the internet that nesting two anchor tags is not considered a good practice and I would have to restyle every button where this happens which would be a lot of changes site-wide. In some cases the buttons are also too small and having a nested globe icon would make things even more compact. If I remove the nested globe then there will be a considerable reduction in the number of globe icons from the site. So wanted to know your views. Should I change each button or just have make it a simple button with no nesting?
@jywarren @Tlazypanda @RuthNjeri @cesswairimu @grvsachdeva @keshavsethi

Hi @imajit
From what you are saying, is that currently, the global icon and the button, is not nested? And that from your research it is not a good practise to nest them?

At the end of the comment, you do mention

If I remove the nested globe then there will be a considerable reduction in the number of globe icons from the site. So wanted to know your views. Should I change each button or just have make it a simple button with no nesting?

I am confused, is there nesting on the site currently? What do you mean by removing the nested globe and it leading to a reduction in the number of globe icons? Does removing the nesting mean that you are completely removing the globe icon?