Mobile/Notes/11-Jan-2012: Difference between revisions

Mobile/Notes/11-Jan-2012 (view source)

1,304 bytes added , 11 January 2012

Confirmed users, Bureaucrats and Sysops emeriti

2,976

edits

@@ Line 11: / Line 11: @@
 == Major Topics for This Week ==
+* '''String Freeze:''' What's that exactly? (Pike)
+String freeze is a bad name for the day when we start to work towards shipping the localized versions. It's got less to do with not changing the ascii chars in locales/en-US. Basically, starting at the day of string freeze, we'll allow localizers to say "we're good to ship this", independently of what lands in the code. So any new landing after that needs to make all our versions better, localized or not. Remember, almos 50% of our users are on non-en-US builds.
+Common pitfalls and myths:
+; prelanding strings : in particular on mobile, strings are badly space constrained. Practically, if you're using an Italian build and there's half an Italian string in a button, that's about as good a UI as an English string, as in, not good at all. Strings are landed when the nightly builds on ftp that are ready for QA of that string.
+; re-using existing strings : Just had a too-good-to-miss example in {{bug|710433}}: Changing the verbs "bookmark" and "remove" to a noun "bookmark" with a checkbox. Different words, even though they're the same 8 characters.
+; polish : A warning on visual polish, too: If there's less space for the text after a refresh, that may very well crop localized strings. Likely much more of a problem on mobile than desktop.
 == Application ==