Closed Bug 581102 Opened 14 years ago Closed 10 years ago

make it possible for localizers to localize the SDK documentation

Categories

(Add-on SDK Graveyard :: Documentation, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: myk, Unassigned)

Details

(Whiteboard: c=Add-ons u=addons p=0)

It should be possible for localizers to localize the SDK documentation.

Perhaps packages' docs/ directories could be divided into locale-specific subdirectories that contain locale-specific versions of documentation (docs/en, docs/es, etc.)?  |cfx docs| would then need to choose the right version to display based on the locale of the user's OS.  And Add-on Builder would need to choose the right version to display based on the locale of the user's browser.
@MyK I'll be happy to help on this in the ES locale version.
Let me know if I can give a hand on this!
(In reply to comment #1)
> @MyK I'll be happy to help on this in the ES locale version.
> Let me know if I can give a hand on this!

We are going to coordinate that locale through Mozilla-Hispano ;). 

If someone want to reach us, do it through #mozilla-hispano on irc.mozilla.org.
(In reply to comment #2)
> (In reply to comment #1)
> > @MyK I'll be happy to help on this in the ES locale version.
> > Let me know if I can give a hand on this!
> 
> We are going to coordinate that locale through Mozilla-Hispano ;). 
> 
> If someone want to reach us, do it through #mozilla-hispano on irc.mozilla.org.

Cool Hernan!! I have an idea: let's send an email to the rest of the ambassadors to see if we can have another locales also and let's spread the word about this to the rest of the community! We talked about this already in #mozilla-hispano IRC channel an it's awesome!
The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product.

To filter bugmail related to this change, filter on the word "looptid".
Component: Jetpack SDK → General
Product: Mozilla Labs → Add-on SDK
QA Contact: jetpack-sdk → general
Component: General → Documentation
QA Contact: general → documentation
Priority: -- → P1
Target Milestone: --- → Future
Is this still planned/wanted? I know that a localization API is being created for the SDK itself to use, but would that apply to the SDK documentation as well? ( https://wiki.mozilla.org/Features/Jetpack/Add-on_SDK_Localization_API_and_Service )
(In reply to comment #5)
> Is this still planned/wanted? I know that a localization API is being
> created for the SDK itself to use, but would that apply to the SDK
> documentation as well? (
> https://wiki.mozilla.org/Features/Jetpack/Add-
> on_SDK_Localization_API_and_Service )

Yes, it's wanted, and I think it looks at the moment like a separate problem to localizing add-ons. So this ought to stay, even though I won't be able to look at it for a little while yet.
It was determined that this will be better as a feature page.
Assignee: nobody → dcm
(Pushing all open bugs to the --- milestone for the new triage system)
Target Milestone: Future → ---
Assignee: dcm → jgriffiths
Whiteboard: c=Add-ons u=addons p=0
Assignee: jgriffiths → nobody
Priority: P1 → --
Can we close this one?
Flags: needinfo?(wbamberg)
No, not until we have finished migrating stuff to MDN.
Flags: needinfo?(wbamberg)
(In reply to Will Bamberg [:wbamberg] from comment #10)
> No, not until we have finished migrating stuff to MDN.

If a contributor made a patch we would still accept it then?
Flags: needinfo?(wbamberg)
I guess, as usual, it would depend on what the patch was. If the patch was to add it to the existing SDK doc system, no. If it was to finish migrating the docs to MDN, and "make it posssible" in that way, then sure! Why do you ask, is such a thing likely to happen in the next week or so?

But I don't very much mind: if you want really want to close this bug, close it.
Flags: needinfo?(wbamberg)
Now the docs are MDN, they can!
https://developer.mozilla.org/en-US/Add-ons/SDK
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.