Describe the bug
#6036 (comment) has the specific issues, and there are child issues to this one to track. Because of Translatewiki now pulling in Hindi and ES-419 strings there's a bunch of pipeline work we need to do support these.
Besides the child issues, there are 72 lint failures in the strings themselves issues that need to be fixed (as of the latest TranslateWiki CI run relative to this issue being created) are seen here: https://gist.github.com/BenHenning/7213c53fd84d52b06e5cab08af9f42d2.
All lint issues fall into these categories to address:
All of these will require changes directly on Translatewiki.
Steps To Reproduce
#6158 isn't passing CI checks.
Expected Behavior
#6158 should pass CI checks and the app should be able to use the new strings.
Screenshots/Videos
No response
What device/emulator are you using?
No response
Which Android version is your device/emulator running?
No response
Which version of the Oppia Android app are you using?
No response
Additional Context
No response
Describe the bug
#6036 (comment) has the specific issues, and there are child issues to this one to track. Because of Translatewiki now pulling in Hindi and ES-419 strings there's a bunch of pipeline work we need to do support these.
Besides the child issues, there are 72 lint failures in the strings themselves issues that need to be fixed (as of the latest TranslateWiki CI run relative to this issue being created) are seen here: https://gist.github.com/BenHenning/7213c53fd84d52b06e5cab08af9f42d2.
All lint issues fall into these categories to address:
IMPLIED_QUANTITY(8/72): All problems in the Hindi translations where the translator didn't actually use a%dqualifier for specifically the "one" plural case despite that matching both 0 and 1 in Hindi. This applies to messages:chapter_countstory_countlesson_countcompleted_story_countongoing_topic_countminutes_agohours_agodays_agoSTRING_FORMAT_COUNT(4/72): these are Hindi messages that are incorrectly using the type specifiers (e.g.%1$s) and seem to have extra incorrect%s actually. This applies to messages (note that despite there being 4 reported errors they are duplicated so there are only two):chapter_completedmath_expression_error_number_after_var_termSTRING_FORMAT_INVALID(2/72): this is related to the previous point. The extra%in the following message is causing an issue (and it's being reported as 2 errors for this one message):chapter_completedTYPOGRAPHY_DASHES(3/72): these are cases where a hyphen-is being used but an en dash should be used instead in this case since these are all ranges:–. This applies to messages:number_error_larger_than_fifteen_charactersnumber_error_larger_than_fifteen_charactersnps_score_questionTYPOGRAPHY_ELLIPSIS(1/72): this is a case of using...(three periods) instead of the ellipsis character:…. This affects message:noTYPOGRAPHY_FRACTIONS(1/72): this is a case of using1/2instead of the one half character:½. This affects message:ratio_error_invalid_formatTYPOGRAPHY_QUOTES(50/72): these are cases where standard quotes"need to be replaced with directional quotes:“”(Unicode: “ and ”). Note that these are tricky to copy or use so care should be taken since smart quotes can sometimes behave a bit unexpectedly in text editors. This affects messages:progress_database_full_dialog_descriptionmath_expression_error_single_redundant_parenthesesmath_expression_error_multiple_redundant_parenthesesmath_expression_error_redundant_parentheses_individual_termmath_expression_error_unnecessary_symbolsmath_expression_error_missing_lhs_for_addition_operatormath_expression_error_missing_lhs_for_multiplication_operatormath_expression_error_missing_lhs_for_division_operatormath_expression_error_missing_lhs_for_exponentiation_operatormath_expression_error_missing_rhs_for_addition_operatormath_expression_error_missing_rhs_for_subtraction_operatormath_expression_error_missing_rhs_for_multiplication_operatormath_expression_error_missing_rhs_for_division_operatormath_expression_error_missing_rhs_for_exponentiation_operatormath_expression_error_missing_equalsmath_expression_error_more_than_one_equalsmath_expression_error_hanging_equalsmath_expression_error_unsupported_functionnumber_error_starting_with_floating_pointwelcomeprivacy_policy_web_linkagree_to_termsterms_of_service_web_linkfaq_answer_whats_oppiaprogress_database_full_dialog_descriptionfractions_default_hint_textmath_expression_error_single_redundant_parenthesesmath_expression_error_multiple_redundant_parenthesesmath_expression_error_redundant_parentheses_individual_termmath_expression_error_unnecessary_symbolsmath_expression_error_missing_lhs_for_addition_operatormath_expression_error_missing_lhs_for_multiplication_operatormath_expression_error_missing_lhs_for_division_operatormath_expression_error_missing_lhs_for_exponentiation_operatormath_expression_error_missing_rhs_for_addition_operatormath_expression_error_missing_rhs_for_subtraction_operatormath_expression_error_missing_rhs_for_multiplication_operatormath_expression_error_missing_rhs_for_division_operatormath_expression_error_missing_rhs_for_exponentiation_operatormath_expression_error_missing_equalsmath_expression_error_more_than_one_equalsmath_expression_error_hanging_equalsmath_expression_error_unsupported_functionnumber_error_starting_with_floating_pointwelcomeprivacy_policy_web_linkagree_to_termsterms_of_service_web_linkfaq_answer_whats_oppiafaq_answer_whos_an_adminTYPOS(3/72): these are specific potential typos discovered by the lint tool:math_expression_error_single_redundant_parentheses. Error message: "al rededor" is a common misspelling; did you mean "alrededor"?math_expression_error_multiple_redundant_parentheses. Error message: "al rededor" is a common misspelling; did you mean "alrededor"?math_expression_error_redundant_parentheses_individual_term. Error message: "al rededor" is a common misspelling; did you mean "alrededor"?All of these will require changes directly on Translatewiki.
Steps To Reproduce
#6158 isn't passing CI checks.
Expected Behavior
#6158 should pass CI checks and the app should be able to use the new strings.
Screenshots/Videos
No response
What device/emulator are you using?
No response
Which Android version is your device/emulator running?
No response
Which version of the Oppia Android app are you using?
No response
Additional Context
No response