Opened 12 months ago

Last modified 10 months ago

#5340 new change

Automate fix tags

Reported by: juliandoucette Assignee:
Priority: P3 Milestone: Websites editing service
Module: Sitescripts Keywords:
Cc: wspee, kvas, jsonesen, ire, saroyanm, lisabielik Blocked By:
Blocking: Platform: Unknown / Cross platform
Ready: yes Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

Description (last modified by kvas)

Background

Until recently, we have tried to <fix> all names, numbers inside translatable strings consistently across websites. This was intended to help translators identify words that they probably should not translate in crowdin.

Problem is, this creates more work for us (developers) because we have to read all website content and add <fix> tags manually. This also creates more work for our translation manager because [her translators do not currently use crowdin or understand <fix> tags, she does not currently dedicate resources to reviewing translations from our community].

What to change

I would like to change our policy to not inserting <fix> tags manually - and relying on the CMS to insert them automatically around all [numbers, whitelisted expressions] inside translation strings - by passing an option (which is disabled by default - because fix tags are not currently benefiting our translation manager) to our translation procedure.

Implementation note:

  • The relevant code for working with translation strings exists in cms/bin/translate.py.
  • The functionality should be an option to translate.py (or a separate script if it turns out to be useful to run it without the rest of translate.py functionality).

Change History (7)

comment:1 follow-up: Changed 12 months ago by juliandoucette

  • Description modified (diff)
  • By "whitelisted expressions" I mean basic strings and regular expressions
  • I'm also suggesting that we could create a shared whitelist of expressions that works for all of our websites

comment:2 in reply to: ↑ 1 Changed 12 months ago by kvas

Replying to juliandoucette:

  • I'm also suggesting that we could create a shared whitelist of expressions that works for all of our websites

Yeah, I guess we could have a global config (in something like ~/.cms) and a local one in the website repository if something needs to be added or overridden. The global config could be shared and synchronized via codetools repository.

comment:3 Changed 12 months ago by juliandoucette

Yeah, I guess we could have a global config (in something like ~/.cms) and a local one in the website repository if something needs to be added or overridden. The global config could be shared and synchronized via codetools repository.

No objections.


If you could confirm that you think this is possible and a good idea then we could change our policy immediately and save a lot of time.

comment:4 Changed 12 months ago by kvas

I think this is possible and a good idea.

comment:5 Changed 12 months ago by kvas

  • Description modified (diff)
  • Priority changed from Unknown to P3
  • Ready set

comment:6 Changed 11 months ago by ire

  • Cc ire added; iaderinokun removed

comment:7 Changed 10 months ago by juliandoucette

  • Milestone set to Websites editing service
Note: See TracTickets for help on using tickets.