wf49670 / ppgen

Post-processing generator for DP
6 stars 4 forks source link

<i lang="la" xml:lang="la"> are not converted properly into text versions #2

Closed davem2 closed 10 years ago

davem2 commented 10 years ago

Inline markup with lang attributes included are not converted to _ properly

For example:

SEA-JELLIES (Acalepha).

translates to

SEA-JELLIES (Acalepha_).

in the text version

davem2 commented 10 years ago

I just read the section in the Ppgen manual on languages at http://www.pgdp.net/wiki/PPTools/Ppgen/Manual#Language_markup which recommends using the form:

SEA-JELLIES (Acalepha).

Which converts nicely into text.

However, I can see others running into this problem as the "DP: HTML Best Practices" page (http://www.pgdp.org/~jana/best-practices/pages/case-studies/inline-formatting/#marking-up-italics) recommends using the form.

ghost commented 10 years ago

I see what you mean. PPers might think they can put straight HTML as inline markup for ppgen. That's not going to work. Best practices is for marking up HTML. One might argue that even given the proper ppgen markup, it still doesn't generate the BP form. My question would be is there any functional difference between: <i><lang="la">Acalepha</lang></i> and <i lang="la" xml:lang="la">.

Here's what I'm doing: first, there is a bug in the code relating to the lang= processing where an extra double-quote can be injected. That's fixed. The other thing I've done is catch the inline-HTML version of the lang= and handle it as a fatal error (because it is). I've got this code in 3.24P. I have this question into PPV and if there is a difference other than style, I may revisit the generator's coding for the lang attribute.