3,267
edits
Changes
Jump to navigation
Jump to search
Line 21:
Line 21: − − With this feature it should be easier for deployments who rely on a small translator team to accomplish their job since they no longer need to keep pace with the Sugar release cycle. Furthermore, we hope to alleviate activity maintainers from the burden of making a new release whenever a new translation becomes available. Line 168:
Line 166: − + + + + + + + + + +
no edit summary
[[Image:3G_CP.png|thumb|none|800px|The 3G control-panel section]]
[[Image:3G_CP.png|thumb|none|800px|The 3G control-panel section]]
=== A message is displayed when an activity fails to start ===
=== A message is displayed when an activity fails to start ===
=== Update an activity translation independently of the Sugar release process ===
=== Update an activity translation independently of the Sugar release process ===
In general the translation process is tightly coupled with the release workflow. In order to get the latest translations for a particular activity, deployments need either to wait for the activity maintainer to provide a new release or to use the language-pack mechanism, which is distribution specific (and at its best an ugly hack). The [[Features/Enhanced_Gettext | Enhanced Gettext Feature]] adds an extra search path for the translation files of Sugar activities. This allows deployments to add and update activity translations independently of the release process. The alternate search path can be configured using [http://projects.gnome.org/gconf/ GConf configuration system].
In general the translation process is tightly coupled with the release workflow. In order to get the latest translations for a particular activity, deployments need either to wait for the activity maintainer to provide a new release or to use the language-pack mechanism, which is distribution specific (and at its best an ugly hack). The [[Features/Enhanced_Gettext | Enhanced Gettext Feature]] adds an extra search path for the translation files of Sugar activities. This allows deployments to add and update activity translations independently of the release process. The alternate search path can be configured using the [http://projects.gnome.org/gconf/ GConf configuration system].
With this feature it should be easier for deployments who rely on a small translator team to accomplish their job since they no longer need to keep pace with the Sugar release cycle. Furthermore, we hope to alleviate activity maintainers from the burden of making a new release whenever a new translation becomes available.
=== Option to disable the name input screen ===
=== Option to disable the name input screen ===
An option has been added to disable the "enter your name" screen which is displayed when you use Sugar for the first time. The screen is only needed in live environments. If Sugar is ran in an installed to disk environment, the user will need to provide a name and password to start the session, so asking for a name again is not needed. The sugar session will use the name provided by the $USER environment variable.
/schemas/desktop/sugar/user/default_nick
The name input screen can be disabled using the [http://projects.gnome.org/gconf/ GConf configuration system].
http://bugs.sugarlabs.org/ticket/1497
http://bugs.sugarlabs.org/ticket/1497