PDF.js no longer depends on TextDecoder

vyv03354 2014-05-27 20:47:30 -07:00
parent 214cca1b97
commit 09aac34e58

@ -657,31 +657,6 @@ if the browser cannot tell if fonts are loaded and can be used.
</tbody>
</table>
## <a id="TextDecoder"></a>TextDecoder is supported
Some East Asian PDFs will be completely garbled, if the browser does not support the `TextDecoder`. See http://encoding.spec.whatwg.org/
<table>
<thead>
<tr>
<th>Chrome</th>
<th>Firefox (Gecko)</th>
<th>Internet Explorer</th>
<th>Opera</th>
<th>Safari</th>
</tr>
</thead>
<tbody>
<tr>
<td>No (v.24)</td>
<td>Yes (v.18)</td>
<td>No (v.10)</td>
<td>?</td>
<td>No (v.6)</td>
</tr>
</tbody>
</table>
## <a id="Worker"></a>Worker is supported/enabled
The PDF.js will execute all code (even long running) on the main thread,
@ -785,28 +760,3 @@ if the browser cannot request network binary data from web workers.
</tr>
</tbody>
</table>
## <a id="Worker-TextDecoder"></a>TextDecoder is supported in web workers
Texts will not be copied properly on some East Asian PDFs. If the browser does not support the `TextDecoder` in web workers, the `FileReaderSync` will be used instead.
<table>
<thead>
<tr>
<th>Chrome</th>
<th>Firefox (Gecko)</th>
<th>Internet Explorer</th>
<th>Opera</th>
<th>Safari</th>
</tr>
</thead>
<tbody>
<tr>
<td>Emulated (v.24)</td>
<td>Yes (v.20)</td>
<td>Emulated (v.10)</td>
<td>?</td>
<td>No (v.6)</td>
</tr>
</tbody>
</table>