From bouzim at gmail.com Thu Sep 27 05:12:15 2012 Content-Type: multipart/mixed; boundary="===============5410242990647579038==" MIME-Version: 1.0 From: D. Barbier To: devel at lists.po4a.org Subject: Re: [Po4a-devel] parsing asciidoc styles Date: Thu, 27 Sep 2012 07:11:44 +0200 Message-ID: In-Reply-To: CABuykp=Dr3_ww-5_rpKBi_Jw+cWE4KVp-NCAPCmHp3y+k3VbNw@mail.gmail.com --===============5410242990647579038== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On 2012/9/27 Anders Nawroth wrote: [...] >> I still do not fully understand Asciidoc syntax, but I guess that we >> need to allow customization as is done in other po4a modules (for >> instance LaTeX or Xml). > > The question for me is how this holds up for really long lines? > If such lines get wrapped into multiple lines in the generated translatio= n, > it's not AsciiDoc any more. Ah yes, I skipped that part of your question. This is doable, see for instance Locale::Po4a::Xml documentation: translated Space-separated list of tags you want to translate. The tags must be in the form , but you can join some (), if a tag () should only be considered when it's into another tag (). You can also specify some tag options by putting some characters in front of the tag hierarchy. For example, you can put 'w' (wrap) or 'W' (don't wrap) to override the default behavior specified by the global "wrap" option. Example: W The main issue is to define a syntax which will be intuitive for Asciidoc u= sers. Denis --===============5410242990647579038==--