Apache OpenOffice (AOO) Bugzilla – Issue 14418
php tags should not be replaced
Last modified: 2005-01-06 03:06:03 UTC
Whenever I use the html editor to open an html file with php tags and modify something (specifically table column widths), my php tags are messed up. It seems that <?php and ?> are not recognized because the tags are replaced with <?php and ?> If possible, it would be great if php tags could be recognized and not changed by the html editor.
Noted this problem myself in 1.1beta. The HTML editor doesn't recognize the <? and ?> tags for embedding PHP in a page, and instead converts the < character to < ... The HTML editor is great otherwise, for visual design of static web pages. So it'd be very cool to see it support this kind of PHP script! Tim Thulson
SBA: Reassigned to Bettina from the User Experience team for consideration.
*** Issue 13790 has been marked as a duplicate of this issue. ***
*** Issue 11711 has been marked as a duplicate of this issue. ***
What extention does the file have? If it's .php, ooo opens it as text. If it's .html, then it opens it as html and tags aren't preserved, which is correct. I think this issue should be closed as invalid, since ooo behaves as a html editor, not as an php IDE.
Up through ooo 1.1.2 .php files are not opened in text mode as far as I can tell, and all php tags are lost. I have not been able to check 1.1.3 yet. Furthermore, I disagree on the point about ooo not preserving php tags in html mode. This behavior has nothing to do with behaving like a php IDE or not. Simply because ooo does a pretty good job opening and editing HTML and because HTML and PHP code can be seen side by side, I believe that ooo should be able to handle this case without breaking PHP. Please note that this issue is considered an "enhancement". That is exactly how I view it. The current behavior does not break HTML, so this is not a bug. However, a useful additional feature would be to correctly preserve php tags within HTML mode.
*** Issue 38171 has been marked as a duplicate of this issue. ***
. *** This issue has been marked as a duplicate of 38171 ***
closed