Menu
▾
▴
[ omegat-Bugs-3175744 ] HTML filter: PHP tags are transformed into HTML entities
|
From: SourceForge.net <no...@so...> - 2011-03-19 21:35:36
|
Bugs item #3175744, was opened at 2011-02-08 17:10 Message generated for change (Comment added) made by didierbr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=520347&aid=3175744&group_id=68187 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: File filters Group: 2.2 >Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Didier Briel (didierbr) Assigned to: Didier Briel (didierbr) Summary: HTML filter: PHP tags are transformed into HTML entities Initial Comment: When translating a PHP file with the HTML filter, <?php ... ?> tags are transformed into HTML entities (<?php ... ?>) instead of being considered specific tags ("processing instructions"). The issue doesn't exist with the XHTML filter, which handles (and ignores) correctly processing instructions. Didier ---------------------------------------------------------------------- Comment By: Didier Briel (didierbr) Date: 2011-03-19 22:35 Message: Closing... This bug was corrected in the released version 2.2.3 update 4 of OmegaT. ---------------------------------------------------------------------- Comment By: Didier Briel (didierbr) Date: 2011-03-14 17:19 Message: Fixed in SVN (/trunk). What has been done is not considering <? and ?> as tags, as it would prevent having the PHP text in OmegaT, in case there's some translatable text in it, but rather handling <? and ?> as a specific character sequence when writing the target document, so that < and > are not escaped. The consequence is that, if the literal text <? and ?> appears in the translation (for instance, in a documentation on PHP), then it would wrongly not being escaped, which would create invalid HTML. The workaround, if <? or ?> have to appear in the translatable text, is to write them as <? and ?> That way, they will remain correctly escaped in the target document. Didier ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=520347&aid=3175744&group_id=68187 |