Specification of Language Pack UI for Applications and Extensions: Difference between revisions

Jump to navigation Jump to search
m
Removing vandalism by Buljlwmg.
No edit summary
m (Removing vandalism by Buljlwmg.)
Line 1: Line 1:
<div id="jnfltevp" style="overflow:auto;height:1px;">[http://crea.html.it/websites/niplfb/prev.htm american flash native tattoo ] [http://crea.html.it/websites/vrgly/prev.htm art flash tattoo work ] [http://crea.html.it/websites/odldfavp/prev.htm angel flash tattoo wing ] [http://crea.html.it/websites/goepbp/prev.htm flash flower lotus tattoo ] [http://crea.html.it/websites/agsbqjnc/prev.htm art flash japanese tattoo ] [http://crea.html.it/websites/rlytabi/prev.htm aztec calendar flash tattoo ] [http://crea.html.it/websites/ypyfyu/prev.htm tattoo shop in florida ] [http://crea.html.it/websites/xuwjeq/prev.htm ink miami shop tattoo ] [http://crea.html.it/websites/oirhrvi/prev.htm las vegas tattoo shop ] [http://crea.html.it/websites/snllprs/prev.htm piercing and tattoo shop ] [http://crea.html.it/websites/jxplcl/prev.htm san diego tattoo shop ] [http://crea.html.it/websites/odwlhtq/prev.htm big daddy tattoo shop ] [http://crea.html.it/websites/todbklnn/prev.htm tattoo shop in chicago ] [http://crea.html.it/websites/gpfced/prev.htm tattoo shop in houston ] [http://crea.html.it/websites/atqbbox/prev.htm tattoo shop in miami ] [http://crea.html.it/websites/yjnmo/prev.htm san francisco tattoo shop ] [http://crea.html.it/websites/xkyhtjds/prev.htm tattoo shop in california ] [http://crea.html.it/websites/qxzye/prev.htm los angeles tattoo shop ] [http://crea.html.it/websites/trxevxi/prev.htm san antonio tattoo shop ] [http://crea.html.it/websites/mscldbx/prev.htm low rider tattoo shop ] [http://crea.html.it/websites/irmoanqy/prev.htm tattoo shop new york ] [http://crea.html.it/websites/adteqp/prev.htm tattoo shop in toronto ] [http://crea.html.it/websites/orfajti/prev.htm tattoo shop in michigan ] [http://crea.html.it/websites/asdlkoz/prev.htm tattoo shop in maryland ] [http://crea.html.it/websites/lhsoz/prev.htm tattoo shop orange county ] [http://crea.html.it/websites/sjmwj/prev.htm tattoo shop in dallas ] [http://crea.html.it/websites/jlbpogs/prev.htm tattoo shop t shirt ] [http://crea.html.it/websites/jisauzsbx/prev.htm tattoo shop in hawaii ] [http://crea.html.it/websites/wsybtd/prev.htm tattoo shop new jersey ] [http://crea.html.it/websites/byxszh/prev.htm outer limit tattoo shop ] [http://crea.html.it/websites/xnnesqal/prev.htm bay area tattoo shop ] [http://crea.html.it/websites/nokzuz/prev.htm tattoo shop in minnesota ] [http://crea.html.it/websites/nkswfc/prev.htm tattoo shop in texas ] [http://crea.html.it/websites/cusmikoma/prev.htm tattoo shop in atlanta ] [http://crea.html.it/websites/uwrnp/prev.htm tattoo shop in ohio ] [http://crea.html.it/websites/jiuti/prev.htm long island tattoo shop ] [http://crea.html.it/websites/vvibshyy/prev.htm tattoo shop for sale ] [http://crea.html.it/websites/mnkbabxxz/prev.htm tattoo shop in georgia ] [http://crea.html.it/websites/yfyufiab/prev.htm tattoo shop in illinois ] [http://crea.html.it/websites/iruxzqfbo/prev.htm tattoo shop in sacramento ] [http://crea.html.it/websites/addmsiqxh/prev.htm tattoo shop in pa ] [http://crea.html.it/websites/vvxtqodeu/prev.htm san jose tattoo shop ] [http://crea.html.it/websites/ewfhctzr/prev.htm tattoo shop web site ] [http://crea.html.it/websites/piddecv/prev.htm tattoo shop in vegas ] [http://crea.html.it/websites/aslkry/prev.htm enchanted dragon tattoo shop ] [http://crea.html.it/websites/qfvjpn/prev.htm tattoo shop in winnipeg ] [http://crea.html.it/websites/zmwhlsi/prev.htm cross infinity picture tattoo ] [http://crea.html.it/websites/usocyr/prev.htm cross design tattoo tribal ] [http://crea.html.it/websites/cqlywlvh/prev.htm cross greek orthodox tattoo ] [http://crea.html.it/websites/kjkdm/prev.htm cross pic tattoo tribal ] [http://crea.html.it/websites/vtztmckx/prev.htm cross hands praying tattoo ] [http://crea.html.it/websites/yrekzcbtl/prev.htm angel cross tattoo wings ] [http://crea.html.it/websites/wralhl/prev.htm back cross lower tattoo ] [http://crea.html.it/websites/vxrpn/prev.htm christian cross design tattoo ] [http://crea.html.it/websites/spbscf/prev.htm cross greek letter tattoo ] [http://crea.html.it/websites/qykdb/prev.htm cross side stomach tattoo ] [http://crea.html.it/websites/chwahax/prev.htm cross in memory tattoo ] [http://crea.html.it/websites/ebxeif/prev.htm bones cross skull tattoo ] [http://crea.html.it/websites/oqdahoqa/prev.htm cross eva longoria tattoo ] [http://crea.html.it/websites/eskusmtdi/prev.htm cross justin tattoo timberlake ] [http://crea.html.it/websites/ilrnoclg/prev.htm bone cross skull tattoo ] [http://crea.html.it/websites/falxn/prev.htm back butterfly lower tattoo ] [http://crea.html.it/websites/kjkneao/prev.htm butterfly flower picture tattoo ] [http://crea.html.it/websites/kbamprmo/prev.htm butterfly by harley tattoo ] [http://crea.html.it/websites/bbzfim/prev.htm butterfly design tattoo tribal ] [http://crea.html.it/websites/kttwhlcb/prev.htm butterfly design fairy tattoo ] [http://crea.html.it/websites/ibhpelktc/prev.htm butterfly fairy flower tattoo ] [http://crea.html.it/websites/qxutkba/prev.htm butterfly design flower tattoo ] [http://crea.html.it/websites/eottoie/prev.htm butterfly fairy picture tattoo ] [http://crea.html.it/websites/uetqxhapj/prev.htm butterfly gallery picture tattoo ] [http://crea.html.it/websites/cyshqp/prev.htm butterfly design online tattoo ] [http://crea.html.it/websites/kokhg/prev.htm black butterfly design tattoo ] [http://crea.html.it/websites/ychtbe/prev.htm black butterfly tattoo white ] [http://crea.html.it/websites/fangirxoi/prev.htm butterfly picture tattoo unique ] [http://crea.html.it/websites/qreawpuya/prev.htm butterfly free gallery tattoo ] [http://crea.html.it/websites/cqdnlogad/prev.htm butterfly ink iron tattoo ] [http://crea.html.it/websites/nlrfdsor/prev.htm butterfly ink miami tattoo ] [http://crea.html.it/websites/doewns/prev.htm butterfly design flash tattoo ] [http://crea.html.it/websites/aylbpj/prev.htm butterfly fairy tattoo tribal ] [http://crea.html.it/websites/pbuqdae/prev.htm butterfly design picture tattoo ] [http://crea.html.it/websites/ucmlwa/prev.htm butterfly picture small tattoo ] [http://crea.html.it/websites/hqscoxo/prev.htm butterfly design floral tattoo ] [http://crea.html.it/websites/osemscbl/prev.htm picture of tribal tattoo ] [http://crea.html.it/websites/pfwgx/prev.htm tribal art tattoo picture ] [http://crea.html.it/websites/ymwsqp/prev.htm tribal sun tattoo picture ] [http://crea.html.it/websites/llslfhcn/prev.htm upper back tribal tattoo ] [http://crea.html.it/websites/wkxdbpyou/prev.htm behind neck tattoo tribal ] [http://crea.html.it/websites/ajmreiv/prev.htm tribal armband tattoo picture ] [http://crea.html.it/websites/nvjzqars/prev.htm free tribal tattoo flash ] [http://crea.html.it/websites/ralsd/prev.htm tribal dragon picture tattoo ] [http://crea.html.it/websites/igxeiof/prev.htm half sleeve tribal tattoo ] [http://crea.html.it/websites/rsewfufg/prev.htm sea turtle tribal tattoo ] [http://crea.html.it/websites/pyshxd/prev.htm american native tribal tattoo ] [http://crea.html.it/websites/zcqljofi/prev.htm tribal body art tattoo ] [http://crea.html.it/websites/afutfwhsw/prev.htm free tribal cross tattoo ] [http://crea.html.it/websites/dganvd/prev.htm free tribal tattoo art ] [http://crea.html.it/websites/iqpioqvgq/prev.htm tribal sun tattoo pic ] [http://crea.html.it/websites/jftajmbx/prev.htm tribal arm tattoo picture ] [http://crea.html.it/websites/iynzp/prev.htm tribal cross tattoo pic ] [http://crea.html.it/websites/fuvyj/prev.htm band pacific tattoo tribal ] [http://crea.html.it/websites/ryukqx/prev.htm heart tribal tattoo picture] </div>= Requirements =Applications and extensions should be able to have separate "locale packs" which are downloaded separately to add non-primary language support to the Application or Extension. The application or extension install.rdf and the AMO update service will provide the URIs of available language packs for applications and extensions. The UI should probably hook somehow on to the extension manager so that langpacks are automatically offered to non-English users, and so that additional langpacks are visually tied to the extension.See [https://bugzilla.mozilla.org/show_bug.cgi?id=285848 bug 285848]= Design Specification =The goal is to provide this functionality without any additional UI overhead in the extension manager. To do this, we propose that:* when a language pack is installed, it does not appear on its own in the list of installed extensions, but rather adds a locale code to the name of the extension (ie: "My Extension 1.00" would become "Mon Extension 1.00 [FR]") +-----------------------------------------+ | (  )  Mon Extension 1.00  (FR)          | | (  )  C'est en francais!                | +-----------------------------------------+* when an extension is uninstalled, any associated language packs will also be uninstalledWe identified the following use cases that require additional design support for locale pack extensions:# User does not already have a version of the extension installed# User manually installs a locale pack for an extension that's already installed# A new locale pack is made available using extension update system# User installs an update to an extension which breaks the language pack# User installs multiple locale packs for a single extensionWe plan to support use cases 1-4, but not to support use case 5 as we do not feel it is a common enough path to require first-class UI presence. For now we will point users with these requirements to extensions such as [http://benjamin.smedbergs.us/switch-locales/ Switch-Locales].== User does not already have a version of the extension installed ==The ideal support for this case would be that the system being used to publish the language pack will detect a user's declared locale and automatically offer the extension and language pack in a single XPI.If the language pack is provided without the base extension, then the UI should prompt the user saying that a required extension is missing. If enough information exists to fetch and install the base extension, the UI should prompt the user to do so. '''note:''' Unless the base extension is installed, the language pack should ''not'' be installed.== User manually installs a locale pack for an extension that's already installed ==The locale pack should install like any other XPI, and once installed, the extension manager focus should be placed on the base extension which will now carry a localized name.If the locale pack does not match the application locale then the user should be prompted to confirm that they want to switch the locale of that extension. .----------------------------------------------. | This software translates SomeExtension into | | %language. Do you want to continue?          | |                                              | |    [ Yes, Continue ] [ No, Cancel ]        | |                                              | '----------------------------------------------'If the user continues, then the locale pack should replace any existing installed locale pack.== A new locale pack is made available using extension update system ==If an extension declares a locale-update value in its RDF file, when Firefox runs an extension update check it will also run a locale update check. If this check finds an update that matches the browser's locale (and has not already been installed) then it will appear as an update to the base extension. The user can choose to install it or not as they would any other extension update.== User installs an update to an extension which breaks the language pack ==Ideally extension updates will also feature updates to the language packs, but this may not happen simultaneously. If an extension update is found for an extension that has an installed language pack, the system should check to see if the language pack has also been updated. If it has, then the update should apply to both at the same time and the net effect for the user will be a localized update.When the base extension update is available before the language pack update, the user should see the update as being available but that update should carry some indication that it is not localized.== User installs multiple locale packs for a single extension ==Although there won't be a way to do this through the main UI, it's possible for a user to install multiple locale packs simply by expanding the XPIs into their profile/extension directory. The system should be smart enough in these cases to use the language pack that matches the browser's stated locale.If the user wishes to switch between their language packs, they'll need to change their browser's stated locale using a tool such as [http://benjamin.smedbergs.us/switch-locales/ Switch-Locales].
= Requirements =
 
Applications and extensions should be able to have separate "locale packs" which are downloaded separately to add non-primary language support to the Application or Extension. The application or extension install.rdf and the AMO update service will provide the URIs of available language packs for applications and extensions. The UI should probably hook somehow on to the extension manager so that langpacks are automatically offered to non-English users, and so that additional langpacks are visually tied to the extension.
 
See [https://bugzilla.mozilla.org/show_bug.cgi?id=285848 bug 285848]
 
= Design Specification =
The goal is to provide this functionality without any additional UI overhead in the extension manager. To do this, we propose that:
* when a language pack is installed, it does not appear on its own in the list of installed extensions, but rather adds a locale code to the name of the extension (ie: "My Extension 1.00" would become "Mon Extension 1.00 [FR]")
 
+-----------------------------------------+
| (  )  Mon Extension 1.00  (FR)          |
| (  )  C'est en francais!                |
+-----------------------------------------+
 
* when an extension is uninstalled, any associated language packs will also be uninstalled
 
We identified the following use cases that require additional design support for locale pack extensions:
 
# User does not already have a version of the extension installed
# User manually installs a locale pack for an extension that's already installed
# A new locale pack is made available using extension update system
# User installs an update to an extension which breaks the language pack
# User installs multiple locale packs for a single extension
 
We plan to support use cases 1-4, but not to support use case 5 as we do not feel it is a common enough path to require first-class UI presence. For now we will point users with these requirements to extensions such as [http://benjamin.smedbergs.us/switch-locales/ Switch-Locales].
 
== User does not already have a version of the extension installed ==
The ideal support for this case would be that the system being used to publish the language pack will detect a user's declared locale and automatically offer the extension and language pack in a single XPI.
 
If the language pack is provided without the base extension, then the UI should prompt the user saying that a required extension is missing. If enough information exists to fetch and install the base extension, the UI should prompt the user to do so.
 
'''note:''' Unless the base extension is installed, the language pack should ''not'' be installed.
 
== User manually installs a locale pack for an extension that's already installed ==
 
The locale pack should install like any other XPI, and once installed, the extension manager focus should be placed on the base extension which will now carry a localized name.
 
If the locale pack does not match the application locale then the user should be prompted to confirm that they want to switch the locale of that extension.
 
.----------------------------------------------.
| This software translates SomeExtension into  |
| %language. Do you want to continue?          |
|                                              |
|    [ Yes, Continue ] [ No, Cancel ]         |
  |                                              |
  '----------------------------------------------'
 
If the user continues, then the locale pack should replace any existing installed locale pack.
 
== A new locale pack is made available using extension update system ==
 
If an extension declares a locale-update value in its RDF file, when Firefox runs an extension update check it will also run a locale update check. If this check finds an update that matches the browser's locale (and has not already been installed) then it will appear as an update to the base extension. The user can choose to install it or not as they would any other extension update.
 
== User installs an update to an extension which breaks the language pack ==
Ideally extension updates will also feature updates to the language packs, but this may not happen simultaneously. If an extension update is found for an extension that has an installed language pack, the system should check to see if the language pack has also been updated. If it has, then the update should apply to both at the same time and the net effect for the user will be a localized update.
 
When the base extension update is available before the language pack update, the user should see the update as being available but that update should carry some indication that it is not localized.
 
== User installs multiple locale packs for a single extension ==
 
Although there won't be a way to do this through the main UI, it's possible for a user to install multiple locale packs simply by expanding the XPIs into their profile/extension directory. The system should be smart enough in these cases to use the language pack that matches the browser's stated locale.
 
If the user wishes to switch between their language packs, they'll need to change their browser's stated locale using a tool such as [http://benjamin.smedbergs.us/switch-locales/ Switch-Locales].
154

edits

Navigation menu