I spoke to Ben Armstrong and we agreed that I should post a follow-up message.
(a) as far as I know, the no-wrap bug in sisu related to bulleted text has been resolved in sisu upstream, (and live-manual is already using that, and the patch should not be necessary at this time; if this is not the case, please feel free to correct me.) (b) Unknown to Ben or anyone else, I have been working on (read "experimenting") with sisu to po4a output, (based on a few documents for which I have at least partial translations). It either reads a source file and generates a pot of the source with empty translation fields, or; reads in two sisu markup files, the source language and the translation file, and generates a po file for that language. Various text blocks types are identified and marked as such vis. regular paragraph, bulleted text, indented text, headings, tables, grouped text, code blocks, footnotes, book index tags and so on... at this stage I am experimenting with what might be done. The idea being that if text blocks are identified and po4a can be deal with them to produce sisu files, generation of po4a and sisu files should be bi-directional. Work is not complete on this pot file generator, and it is still early to determine how successful it will be, but working on it this way gives the opportunity to tease out what can be done. Most of logical separation of parts being made for the pot file is done with the view to make its use more straightforward for the translator. Once I have something that works, I would hope to share it with the po4a team, so they can provide feedback as to what else might need to be done with respect to sisu po4a output; and what po4a can make of it. I have been content to plod on quietly offline as this is post Squeeze work. Early notes: For most but not all text block types line-wrapped text is perfectly acceptable (text-block types are described as text objects in sisu, I have not yet familiarised myself with po4a lingo) e.g. paragraphs, bulleted text (after today's bugfix), indented text, headings, footnotes. But not for example for code blocks, tables (or at present book index tags). The list will be more comprehensive when the code is complete, as block type is identified. Special treatment would also be required for book index tags (which in producing the sisu document should be attached unwrapped to the preceding text block, rather than with an empty line as other text blocks require); Footnotes have also been taken out of the main text, and follow the code block to which they belong (this resulting in un-interrupted regular text and footnotes, that should be easier on the translators eye) - sisu is able to deal with this markup form, though it would be wonderful if the document that is rebuilt by po4a could contain the footnotes using sisu inline footnote markup ... perhaps a bit cryptic now, if unfamiliar with sisu syntax. Thanks in advance, Ralph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
