Axel Hecht wrote:
> Chris Ilias wrote:
>> On 1/4/08 3:08 PM, _David Tenser_ spoke thusly:
>>> To me, it still feels like it would make sense to do an in-product ->
>>> SUMO article import for each locale, save for the "Using Firefox"
>>> article. We should then create a list of features that we want to
>>> cover -- with an emphasis on /basic/ features, e.g.:

>>> * Places
>>> * Location Bar
>>> * ...

>>> Basically, the new "in-product" help will be a subset of the articles
>>> available in SUMO. We need to decide on a sensible subset, and,
>>> preferably, use as much of the current in-product content as possible
>>> to minimize work for localizers. We could, for example, decide that
>>> we want a separate article about Add-ons
>>> (http://support.mozilla.com/kb/Customizing+your+Firefox+with+add-ons),
>>> but that means all localizers need to translate it from scratch. Or,
>>> we could just settle on what's already covered in customization.xhtml
>>> above.

>> I often prefer the wording of the in-product stuff; so I think it
>> would be better to import all the in-product help, then if there are
>> aspects of the current KB articles that we feel are better, we can
>> then import those aspects into the stuff imported from in-product and
>> do away with the KB versions that were created from scratch. (Did that
>> make sense?)

>> After that, we can choose which articles to use for Fx3
>> virtual-in-product help.

> One of the tasks that remain is to fix up the links to in-product help
> within firefox. So we need to fix those links reasonably soon, in
> particular when we want to split existing pages.