[sword-devel] Rendering added words for languages that don't use italics?
Peter von Kaehne
refdoc at gmx.net
Tue Apr 19 08:24:41 MST 2011
> >> Alternatively, the more semantic HTML markup of<em> might be useful?
> > There has been a move away from pushing<em> and<strong> in the HTML
> > world, since it has been recognized that italics do not always
> > semantically mean "emphasis" and bold does not always semantically
> > mean "strong". This situation is a perfect example.
Actually, yes, but reverse to what you want to state.
The <i> interpretation happens very late in our chain - at rendering filter level. And I would think it is probably a wrong decision. It would be trivial to change that to <em> which in turn might be rendered more likely in an appropriate emphasis of whatever sort in scripts which do not do italics.
My comments to not refer to JSWORD, of which I have no real clue of.
Wrt CSS - I do not want to reopen the debate. But at the core of this particular problem is a fairly arbitrary set of conventions which presumably vary wildly across cultures - and even in our own language. The KJV and some related Bibles "tag" translation additions by packing them into . Others use italics. We do not know what Chinese, Mongolians, Arabs use. Maybe they ignore the issue, maybe they use pink colouring for the fonts.
This could therefore be seen as a style issue, as all these issues could be rendered successfully (as long as the render engines understand the directives) at that level - adding a [ via "before" directive, changing font colour or indeed shifting to italics.
Alternatively - and we have discussed this in another place - there is also a need for some locale dependent rendering of references, and this matter would be somewhat related. Instead of css styling the one before last step in the filters could presumably read and apply loalised rendering info ([..], <span style="font-color:pink"> or <i> tags) for any of these issues - i.e. by using the relevant set of alternatives in any of the issues where we want a localised output. This would then work across the board of libsword derived frontends (or not).
Wrt implementation, if the <em> tag would do the job across scripts - and this would be a worthwhile project for someone not too skilled - then this woudl be all we wanted. And it would be a simple implementation.
If we need something more profound we got indeed a problem.
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
More information about the sword-devel