Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(247)

Unified Diff: docs/accessibility/patts.md

Issue 2701603002: Update accessibility documentation. (Closed)
Patch Set: Created 3 years, 10 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « docs/accessibility/overview.md ('k') | third_party/WebKit/LayoutTests/accessibility/readme.md » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: docs/accessibility/patts.md
diff --git a/docs/accessibility/patts.md b/docs/accessibility/patts.md
new file mode 100644
index 0000000000000000000000000000000000000000..5a7fce52891beaf0ce8ee90149aa5873d16f6eeb
--- /dev/null
+++ b/docs/accessibility/patts.md
@@ -0,0 +1,77 @@
+# The Chrome OS PATTS speech synthesis engine
+
+Chrome OS comes with a speech synthesis engine developed internally at Google
+called PATTS. It's based on the same engine that ships with all Android devices.
+
+## Building from source
+
+This is for Googlers only.
+
+Visit [http://go/chrome-tts-blaze](http://go/chrome-tts-blaze)
+for instructions on how to build the engine from source and get the
+latest voice files.
+
+When debugging, start Chrome from the command-line and set the
+NACL_PLUGIN_DEBUG environment variable to 1 to print log messages to stdout.
+
+## Updating
+
+First, follow the public
+[Chromium OS Developer Guide](http://www.chromium.org/chromium-os/developer-guide) to check out the source.
+At a minimum you'll need to create a chroot.
+You do not need to build everything from source.
+You do need to start the devserver.
+
+Next, flash your device to a very recent test build. Internally at Google
+you can do this with the following command when the dev server is running,
+where CHROMEBOOK_IP_ADDRESS is the IP address of your Chromebook already
+in developer mode, and $BOARD is your Chromebook's board name.
+
+```cros flash ssh://CHROMEBOOK_IP_ADDRESS xbuddy://remote/$BOARD/latest-dev/test```
+
+Before you can make changes to PATTS, the first thing you need to run
+(from the chroot) is call cros_workon with two relevant ebuilds:
+
+```
+cros_workon --board=$BOARD start chromeos-assets
+cros_workon --board=$BOARD start common-assets
+```
+
+Next, make sure you're in the platform/assets directory and run
+```repo start``` and create a branch.
+
+```
+cd platform/assets
+repo start <branch_name> .
+```
+
+
+The PATTS data files can be found in this directory:
+
+```platform/assets/speech_synthesis/patts```
+
+When updating the files, the native client files (nexe) need to be zipped.
+
+Replace all of the files you need to update, commit them using git,
+then from the chroot, run:
+
+```
+emerge-$BOARD common-assets
+cros deploy CHROMEBOOK_IP_ADDRESS common-assets
+```
+
+Note that you need to call cros_workon on both chromeos-assets and
+common-assets. You will be changing files in chromeos-assets, but
+to flash it onto your device, you need to emerge and deploy
+common-assets.
+
+After that, reboot your Chromebook and verify that speech works.
+
+To upload the change, use repo upload, something like this:
+
+```
+git commit -a
+ BUG=chromium:12345
+ TEST=Write what you tested here
+repo upload .
+```
« no previous file with comments | « docs/accessibility/overview.md ('k') | third_party/WebKit/LayoutTests/accessibility/readme.md » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698