Support rich line output in both speech and braille

chrome/browser/resources/chromeos/chromevox/braille/spans.js

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 /**
  * @fileoverview Objects used in spannables as annotations for ARIA values
  * and selections.
  */
 
 goog.provide('cvox.ExtraCellsSpan');
+goog.provide('cvox.FormSpan');
 goog.provide('cvox.ValueSelectionSpan');
 goog.provide('cvox.ValueSpan');
 
+goog.require('cvox.LibLouis.FormType');
 goog.require('Spannable');
 
 /**
  * Attached to the value region of a braille spannable.
  * @param {number} offset The offset of the span into the value.
  * @constructor
  */
 cvox.ValueSpan = function(offset) {
   /**
    * The offset of the span into the value.
@@ skipping 41 matching lines @@
 /**
  * Causes raw cells to be added when translating from text to braille.
  * This is supported by the {@code cvox.ExpandingBrailleTranslator}
  * class.
  * @constructor
  */
 cvox.ExtraCellsSpan = function() {
   /** @type {ArrayBuffer} */
   this.cells = new Uint8Array(0).buffer;
 };
+
+
+/**
+ * Indicates a text form during translation in Liblouis.
+ * @param {cvox.LibLouis.FormType} formType
+ * @constructor
+ */
+cvox.FormSpan = function(formType) {

[dmazzoni, 2017/06/27 21:21:52]

The word "form" has other meanings. formType or typeForm are both used in the
liblouis api so it makes sense to use that, even though they're confusing - but
cvox.FormSpan is our own abstraction so how about naming it something more
verbose and easier to understand.

Maybe cvox.BrailleTextStyleSpan or something like that?

[David Tseng, 2017/06/27 23:52:41]

The spans are really only useful for liblouis, but agreed on readability. Done.

+  /** @type {cvox.LibLouis.FormType} */
+  this.formType = formType;
+};