Re: Please check these In-product help articles
David Tenser
> Chris Ilias wrote:
>> There's a lot of code clean up, syntax switching, and of course
>> Firefox 2 and 3 content. It's a morass of code, so I could have easily
>> missed some stuff.
>> http://support.mozilla.com/kb/accessibility-en-US
>> http://support.mozilla.com/kb/cookies-en-US
>> http://support.mozilla.com/kb/customization-en-US
>> http://support.mozilla.com/kb/download_manager-en-US
>> http://support.mozilla.com/kb/forieusers-en-US
>> http://support.mozilla.com/kb/glossary-en-US
>> http://support.mozilla.com/kb/mouse_shortcuts-en-US
>> http://support.mozilla.com/kb/popup-en-US
>> http://support.mozilla.com/kb/shortcuts-en-US
>> http://support.mozilla.com/kb/tabbed_browsing-en-US
>> http://support.mozilla.com/kb/using_firebird-en-US
>>
>>
>> The prefs article and menu reference article are still not ready.
>
> I might derail the question a bit, but as this is likely the first
> changeset for localizers to look at, here are my thoughts on it from a
> l10n editing view.
>
> I took a look to see what got changed from the import to the current
> stage, and I had a hard time doing so. Like, I tried to look at the
> history, and none of the plethora of different diffs actually showed
> something that highlighted the changes.
>
> If I was a localizer who got his or her content imported and wanted to
> follow up on these changes, I had no idea what to do.
>
Actually, the diff for en-US is more complicated that it would have to
be. This is because we did the en-US import first, when we first had
some problems with the script. The imports for the other locales are
much more straighforward:
* Links are automatically converted
* No weird spacing between divs
Therefore, the only job for localizers should be to verify that there
are no "garbage" characters left.
In order to make the diff between "raw import" to "updated for firefox
3" clearer, I think we should backup the en-US files, re-import them
en-US files with the updated script, and then re-apply the changes. That
will allow localizers to see a more exact diff, showing exactly what
they should do with their files.
(Chris, I'll get back to you with instructions on how to do this without
breaking the article translation links.)
> Can we get improvements on this still? Like, just some color
> highlighting of added-removed would help. And maybe less options, just
> the hope that one of the other 5 different diff versions might actually
> enlighten me just took time.
>
See Chris bug report. We are missing some CSS that makes the diff
uncolored. Hopefully we can push a fix for this to the live server this
week.
Hope this helps.
Axel Hecht
That'd be cool and helpful for the translation work here, I guess.
>> Can we get improvements on this still? Like, just some color
>> highlighting of added-removed would help. And maybe less options, just
>> the hope that one of the other 5 different diff versions might
>> actually enlighten me just took time.
>>
>
> See Chris bug report. We are missing some CSS that makes the diff
> uncolored. Hopefully we can push a fix for this to the live server this
> week.
The styles in the bug make sense to me. Commented in the bug.
Axel