Closed Bug 1104821 Opened 10 years ago Closed 10 years ago

Input: translations for feedback form

Categories

(Mozilla Localizations :: zh-CN / Chinese (Simplified), defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: willkg, Assigned: shaohua.wen)

References

Details

We fixed a few strings yesterday on the product picker part of the new Input feedback form which need to be translated. The strings are as follows: 708:#: fjord/feedback/templates/feedback/picker.html:23 709:msgid "Select a product" 710:msgstr "" 741:#: fjord/feedback/templates/feedback/thanks.html:43 742:msgid "Having problems? Get help." 743:msgstr "" 745:#: fjord/feedback/templates/feedback/thanks.html:45 746:msgid "Go to our support forum where you can <a href=\"%(url)s\">get help and find answers</a>." 747:msgstr "" Input strings can be fixed in the Input project in Verbatim <https://localize.mozilla.org/zh_CN/input/>. Once those are translated, I can deploy the updated translations and we'll be all set to release the new feedback form. Thank you so much for your work on Input strings! I really appreciate your efforts on these new feedback form strings. If you have any questions, please let us know.
done
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
The strings are still untranslated in svn. Is there something you have to do in Verbatim to push the strings to svn that isn't done, yet?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I don't know Verbatim very well, so I asked Kadir. He said there's a "Commit all to VCS" button/link in Verbatim. We need to press that to commit it to svn. Then I can pull the changes into the site.
I did it in r135530 for them to speed things up (the crappy part is that SVN consider me as author).
I verified it's fully translated now. I'll push it to -stage later today. Thank you!
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
I verified it on stage. Marking as VERIFIED.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.