Formatting View

Standard View is for the words and Formatting View for the formatting: a French translation typed without formatting, then the switch to Formatting View, which shows bold, italics, superscript and code tags, and the kinds of code.

1. Two views: Standard View for words, Formatting View for formatting

   bAIbel AV shows a translation two ways. Standard View is for the words; Formatting View is for the formatting.

   

2. A translation typed in Standard View

   This care sheet has been translated into French in Standard View, so the targets have no formatting yet. In the source, a small † marks a footnote.

   

3. Click Formatting View

   Click Formatting View. The source shows its bold, italic, superscript and subscript, and a small tag wherever a link, a footnote or a line break sits. Formatting buttons and Place Codes appear on the toolbar.

   

4. Optional and mandatory codes

   Some codes are optional and some are mandatory. Formatting View shows where the formatting goes, not how the page will look.

   

Formatting is placed by hand: bold, a link with Alt+1 from the missing-codes strip, superscript and a footnote, subscript, a TM match that brings its codes, the rule-based Place Codes pass without an AI model, and nested codes placed from the inside out.

1. Select a word and press Ctrl+B

   In row 9, select moitié and press Ctrl+B, as in the source. Ctrl+I and Ctrl+U work the same way. A blue ¶ in the status cell marks a segment with formatting placed.

   

2. Read the missing-codes strip

   Row 6 has a link. With the caret in it, the yellow strip above the grid lists the codes still missing, in source order: the link’s opening and closing codes, and a pair inside them for its character style.

   

3. Place the link with Alt+1

   Click before notre and press Alt+1 twice, then after d’assistance and press Alt+1 twice more. Alt+1 always places the first code left in the strip, so the strip empties.

   

4. Click Superscript; place the footnote with Alt+1

   In row 4, select the 2 of m2 and click Superscript on the toolbar. Then click after pelouse. and press Alt+1 three times: the footnote and the style around it.

   

5. Click Subscript

   In row 5, select the 2 of CO2 and click Subscript. Superscript, subscript and strikethrough have toolbar buttons but no shortcut.

   

6. Press Ctrl+1 for a TM match with its formatting

   Row 2 has a 92% match in the TM. Press Ctrl+1: the match’s French comes in with après chaque usage already bold. A match brings its codes only when the TM stored them the same way; an entry from another tool’s TMX brings the text only.

   

7. Click Place Codes on the section bar

   Each section bar has Place Codes. With no model set for it, only the rule-based pass runs: it places codes at the start or end of the text, keeps codes already placed, and leaves a code inside the text. Here that is row 3’s italic, marked tagging incomplete.

   

8. Codes inside codes: Ctrl+B, Alt+2, then Alt+1

   In row 18 the link’s text is bold, inside a style, inside the link. Work from the inside out: select la boutique de pièces Thistlecombe and press Ctrl+B; select it again and press Alt+2 for the style; select it once more and press Alt+1 for the link.

   

F8 finds a segment with a mandatory line break missing, and export is refused until it is placed. The consistency check compares the two views, a table's codes are placed from its own bar, and the export goes through with one warning for an optional code.

1. From the top, press F8

   Before you export, press F8 from the top. It jumps to the next segment with a mandatory code missing: row 19, where a line break belongs. Bold and italic don’t count here; they are optional.

   

2. Export is refused; read the notification log

   Exporting now is refused. The notification log says why: without its line break, the two lines of row 19 would run together.

   

3. Place the line break with Alt+1 and press F8 again

   Back in Formatting View, click before Du in row 19 and press Alt+1. Press F8 again: No segments with missing mandatory codes.

   

4. Click the consistency button

   The consistency button checks that the two views hold the same text; it does not check codes. Here they agree on every segment. If segments are listed, Regenerate all listed rebuilds their codes from the text, so codes placed by hand are lost.

   

5. Click Place Codes on the Table 1 bar and Process All

   A section’s Place Codes skips its tables, so each table has its own button on its Table 1 bar. AV first asks whether to retry only the segments that failed last time; Process All runs them all, and the rule places the footnote after Toutes les 25 heures.

   

6. Export: a missing optional code only warns

   Now the export goes through, with one warning: the optional italic in row 3, left out. A missing optional code only warns.

   

Switching back to Standard View after Formatting View edits, what happens to codes when a formatted segment's text is edited, and the good habits that follow.

1. Switch back to Standard View and Confirm

   Once the file has a Formatting View edit, AV asks every time you switch back. Confirm only switches. But editing the text of a formatted segment in Standard View marks its codes stale, with an amber ¶: they are rebuilt from the text, and codes placed by hand must be placed again.

   

2. Good habits

   Words in Standard View, codes in Formatting View, and F8 before you export.