OLD | NEW |
1 # The Chrome OS PATTS speech synthesis engine | 1 # The Chrome OS PATTS speech synthesis engine |
2 | 2 |
3 Chrome OS comes with a speech synthesis engine developed internally at Google | 3 Chrome OS comes with a speech synthesis engine developed internally at Google |
4 called PATTS. It's based on the same engine that ships with all Android devices. | 4 called PATTS. It's based on the same engine that ships with all Android devices. |
5 | 5 |
6 ## Building from source | 6 ## Building from source |
7 | 7 |
8 This is for Googlers only. | 8 This is for Googlers only. |
9 | 9 |
10 Visit [http://go/chrome-tts-blaze](http://go/chrome-tts-blaze) | 10 Visit [http://go/chrome-tts-blaze](http://go/chrome-tts-blaze) |
(...skipping 63 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
74 After that, reboot your Chromebook and verify that speech works. | 74 After that, reboot your Chromebook and verify that speech works. |
75 | 75 |
76 To upload the change, use repo upload, something like this: | 76 To upload the change, use repo upload, something like this: |
77 | 77 |
78 ``` | 78 ``` |
79 git commit -a | 79 git commit -a |
80 BUG=chromium:12345 | 80 BUG=chromium:12345 |
81 TEST=Write what you tested here | 81 TEST=Write what you tested here |
82 repo upload . | 82 repo upload . |
83 ``` | 83 ``` |
| 84 |
| 85 ## Ebuild |
| 86 |
| 87 Note that sometimes you'll have to update the ebuild file that |
| 88 takes the patts data files and installs them, unzipping the .nexe |
| 89 files in the process. |
| 90 |
| 91 For example, you'll need to edit the ebuild if you add or remove |
| 92 a language code, or if you add or remove a file that needs to be |
| 93 installed as part of the extension. |
| 94 |
| 95 To update the ebuild, edit this file: |
| 96 |
| 97 ``` |
| 98 /third_party/chromiumos-overlay/chromeos-base/common-assets/common-assets-9999.e
build |
| 99 ``` |
| 100 |
| 101 If you need to land changes to both common-assets and chromiumos-assets, |
| 102 upload the changes separately and then make them depend on one another |
| 103 using this syntax in the changelog: |
| 104 |
| 105 ``` |
| 106 CQ-DEPEND=CL:12345 |
| 107 ``` |
| 108 |
| 109 Note that you can (and often should) have two changes depend on one another |
| 110 so they'll land atomically. |
| 111 |
| 112 |
OLD | NEW |