Specification & documentation -- Community collaboration to draft a functional specification explaining the intended support coverage for ODF and the provisional implementation choices taken for XLIFF (style for inline tags, etc.)

Friedel says:
We handle duplicates in several ways when converting in the toolkit. The
preferred method is to use msgctxt to add unique information. Having
identical translations without msgctxt is an invalid PO file. We could
merge identical strings (this is one of our existing duplicate handling
strategies), but for document translation I think this will be very
risky, and possibly cause translation out of context.

When converting to XLIFF, let us try to favour the use of tags that remove the codes from the source (<g>, <x/>, <bx/> , <ex/>), rather than tags that mask off codes left inline (<bpt>, <ept>, <sub> , <it>, <ph>). ODF is verbose with long tags that is mostly not useful for a translator.