Talk about add-ons and extension development.
jooliaan

Posts: 462Joined: August 24th, 2003, 6:09 amLocation: Italy
Posted July 19th, 2005, 3:46 am
AnonEmoose wrote:I was just saying that having TEM onboard would greatly enhance the project's reach.
Peoples coming from TEM (and other projects of course  ) will be very welcome  Seewak wrote:I sum up : -We must warn authors that they do not have to update an extension if local are missing. -We could create a glossary which list the "difficult" words and their translations. I know Frenchmozilla (team translating mozilla products into French) use a glossary written with the team translating OpenOffice.org into French.
Great sum, I agree on each of the points!  Sewaak wrote:-the site's name
The first one coming in my mind is: Lion's extensions (ROARRRRRRRRRRRR  )
Seewak

Posts: 34Joined: June 10th, 2004, 11:47 amLocation: France
Posted July 19th, 2005, 4:00 am
Why not BabelZilla ? :o
Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8b4) Gecko/20050716 Firefox/1.0+
Site Admin of Extensions.geckozone.org.
jooliaan

Posts: 462Joined: August 24th, 2003, 6:09 amLocation: Italy
Posted July 19th, 2005, 4:06 am
Seewak wrote:Why not BabelZilla ? :o
WOW! I like it! 
The RedBurn
Posts: 13Joined: October 19th, 2004, 4:48 pmLocation: Belgium
Posted July 19th, 2005, 4:43 am
I was thinking about something like extensionsl10n, but it's probably too much serious and not as imaginative as BabelZilla.
The only con for BabelZilla is that it doesn't make think about extensions.
goofyFr

Posts: 70Joined: June 26th, 2005, 2:03 pmLocation: France
Posted July 19th, 2005, 5:12 am
MMMh
(semi-seriously) ExtensionsAreAllOver ?
TEL The Extension Link ?
TheOneKEA

Posts: 4864Joined: October 16th, 2003, 5:47 amLocation: Somewhere in London, riding the Underground
Posted July 19th, 2005, 6:15 am
BabelZilla or e10n would be good names.
Proud user of teh Fox of Fire Registered Linux User #289618
goofyFr

Posts: 70Joined: June 26th, 2005, 2:03 pmLocation: France
Posted July 19th, 2005, 6:51 am
seewak wrote:What about : ... -the categories -...
<ul>
<li>Updating extensions</li>
( with one thread per extension ?)
<li>New extensions</li>
<li>Projects and requests</li>
<li>Help</li>
- Howto (knowledge base)/ Tips and tricks
- Q & A
</ul>
BenBasson
Moderator

Posts: 13671Joined: February 13th, 2004, 5:49 amLocation: London, UK
Posted July 19th, 2005, 8:53 am
Name suggestion: extenl10n.
I think the forum used must be one that has the "description" field for individual topics. This could be used to keep track of the languages the extension has been translated to, so an example might look like this:

Luana

Posts: 54Joined: December 10th, 2004, 7:13 amLocation: Everywhere...
Posted July 19th, 2005, 9:18 am
goofyFr wrote:MMMh (semi-seriously) ExtensionsAreAllOver ? * * * Seriously, i really like the last Cusser proposal: extenl10nTechnical name, but not too much  goofyFr wrote:<ul> <li>Updating extensions</li> ( with one thread per extension ?)
Good idea, more the Cusser idea! ADDED Cusser wrote:I think the forum used must be one that has the "description" field for individual topics. 
goofyFr wrote:<li>New extensions</li>
Maybe could be great to create also this section with one thread per extension more the Cusser idea! ADDED Cusser wrote:I think the forum used must be one that has the "description" field for individual topics. 
What do you think about this? goofyFr wrote:<li>Projects and requests</li> <li>Help</li> - Howto (knowledge base)/ Tips and tricks - Q & A </ul>
I agree
AnonEmoose
Posts: 2031Joined: February 6th, 2004, 11:59 am
Posted July 19th, 2005, 9:33 am
I'm just musing out loud.
With the new chrome.manifest structure, I'm wondering if locales can be installed separately from the extension. (essentially just adding an additional locale line pointing to the proper locale path or alternately deleting/renaming the original chrome.manifest so a new one is regenerated on startup which includes the newly added locale)
If so, extension authors need not include each locale prior to release, since it can be created/added later.. (Obviously this is assuming that he/she properly localized for at least one locale). As long as there was a collection/depository for corresponding locales all one would have to do is download & install it or just place it in the extension folder without the need to replace the jar (if the author originally packaged the extension in a jar).
BenBasson
Moderator

Posts: 13671Joined: February 13th, 2004, 5:49 amLocation: London, UK
Posted July 19th, 2005, 9:57 am
AnonEmoose wrote:I'm wondering if locales can be installed separately from the extension.
Probably, but then we could run into situations where the extension is updated and the locale is not => instant parsing errors. I don't know if the extension system can cope with this sort of thing well (probably not), but in any case, updating the extension should not cause the language to revert.
Ideally, the more locales that can be included for an initial release, the better. Silently adding extra locales without bumping the version number is possible and should be encouraged until the auto-update system can deal with this stuff better (i.e. an en-US Firefox install should ignore an extension update that gives a de-DE locale as the only addition, since it's not relevent to that install).
AnonEmoose
Posts: 2031Joined: February 6th, 2004, 11:59 am
Posted July 19th, 2005, 10:10 am
Cusser wrote:AnonEmoose wrote:I'm wondering if locales can be installed separately from the extension.
Probably, but then we could run into situations where the extension is updated and the locale is not => instant parsing errors. I don't know if the extension system can cope with this sort of thing well (probably not), but in any case, updating the extension should not cause the language to revert.
Correctly you point out that only upon UPDATING an extension (which contains new labels/strings) would parsing errors occur. However it could easiely be remedied by installing an updated locale (if available) or by removing the chrome.manifest & the offending (older) locale which should correct the errors as a new chrome.manifest would be regenerated (provided there was contents.rdf included) upon FireFox restart Cusser wrote:Ideally, the more locales that can be included for an initial release, the better. Silently adding extra locales without bumping the version number is possible and should be encouraged until the auto-update system can deal with this stuff better (i.e. an en-US Firefox install should ignore an extension update that gives a de-DE locale as the only addition, since it's not relevent to that install).
Agreed ...
asqueella
Posts: 4019Joined: November 16th, 2003, 3:05 amLocation: Russia, Moscow
Posted July 19th, 2005, 10:20 am
while we're talking about l10n and locales installed separately, see bug 285848. It's an area that could definitely be improved.
xavivars
Posts: 25Joined: May 15th, 2004, 6:07 am
Posted July 19th, 2005, 11:44 am
I like more BabelZilla, but if you think el10n it's a good name, let's go!
And I'm with you that a forum with descriptions for each topic would be great.
goofyFr

Posts: 70Joined: June 26th, 2005, 2:03 pmLocation: France
Posted July 19th, 2005, 12:51 pm
cusser and xavivars wrote:a forum with descriptions for each topic would be great.
+1
Sure it would (whichever name it will have  )
Return to Extension Development
Who is online
Users browsing this forum: No registered users and 1 guest
|