After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 526698 - In gnome2-accessibility-guide, not translatable the Orca laptop keyboard commands. The document redirect user with http://live.gnome.org/Orca/LaptopKeyboardCommands webpage.
In gnome2-accessibility-guide, not translatable the Orca laptop keyboard comm...
Status: RESOLVED OBSOLETE
Product: gnome-user-docs
Classification: Core
Component: access-guide
2.22.x
Other Linux
: Normal major
: ---
Assigned To: Maintainers of Gnome user documentation
Maintainers of Gnome user documentation
Depends on:
Blocks:
 
 
Reported: 2008-04-07 12:11 UTC by Hammer Attila
Modified: 2013-10-25 23:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Hammer Attila 2008-04-07 12:11:44 UTC
In gnome2-accessibility-guide, not select translation the Orca laptop keyboard commands. The document redirect user with http://live.gnome.org/Orca/LaptopKeyboardCommands
english webpage. It is good for english users, but not a hungaryan blind users for example. I would like translate this keyboard commands with hungarian language. This problem part with low-vision.xml file. Possible copy this description with the low-vision.xml file?
Comment 1 Joachim Noreiko 2008-04-07 16:43:48 UTC
It's not good enough for users without access to the internet, either.

Changing to correct component, and let's make this an actual bug rather than an enhancement: something is not working correctly.

Could someone CC the Orca developers please?
Comment 2 Claude Paroz 2008-04-07 19:15:00 UTC
Cc'ed Orca's maintainers.
Comment 3 Willie Walker 2008-04-15 17:14:01 UTC
(In reply to comment #2)
> Cc'ed Orca's maintainers.
> 

Hi All:

I believe the original sources for the Orca portion of the gnome2-accessibility-guide came from the WIKI.  I agree that the longer term more appropriate thing to do would be to put the entire user guide under gnome2-accessibility-guide.  Can you advise us on what we need to do here?  We know very little about the overall process.

Will
(Orca project lead)
Comment 4 Shaun McCance 2008-04-15 17:20:31 UTC
Well, Orca doesn't necessarily have to have all its documentation in the Accessibility Guide.  It could have its own document.  The Accessibility Guide should certainly mention Orca, but it could just point to another document for detailed documentation.  Or we could do things all in one document.

What do we currently do for other accessibility tools?  I know Dasher has its own document, but I'm not sure about the rest.
Comment 5 Willie Walker 2008-04-15 17:57:45 UTC
(In reply to comment #4)
> Well, Orca doesn't necessarily have to have all its documentation in the
> Accessibility Guide.  It could have its own document.  The Accessibility Guide
> should certainly mention Orca, but it could just point to another document for
> detailed documentation.  Or we could do things all in one document.

Sounds fair.  Let's suppose we went down the "Orca has its own" route.  I have a bunch of questions :-):

* Where should we keep the docbook sources (under the 'orca' module somewhere)?

* Is there a nightly process to build/publish the docs automatically?  If so, at what URL would the docs be published?

* How do we handle i18n/l10n of the doc content?

* Is there a standard docbook template we should follow?

* How do we make cross references/links to other documents outside Orca and vice versa (e.g., Accessibility Guide pointing to Orca Guide)?
Comment 6 Joachim Noreiko 2008-04-15 18:37:12 UTC
http://live.gnome.org/GnomeDocUtilsCreateNew should get you started :)
Comment 7 Kat 2013-10-25 23:43:49 UTC
The issue does not seem to exist any more: I can't find anywhere that the orca or gnome-user-docs help links to the wiki from accessibility pages.