𝌔 Fossil Hub
Login | Fossil manual |
phptags tag tidier

Check-in [4d8d9678db]

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Remove note about pseudo close tags (need UTF-8 obfuscation).
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1:4d8d9678db3191e54bcdb80cf0ba5133d3fd4241
User & Date: mario 2014-11-24 01:29:34
Context
2014-11-28
11:47
commit 1.2 NEWS date check-in: 17edfccd92 user: mario tags: trunk
2014-11-24
01:29
Remove note about pseudo close tags (need UTF-8 obfuscation). check-in: 4d8d9678db user: mario tags: trunk
00:24
Finalize release 1.2 check-in: ff1dca8029 user: mario tags: trunk, 1.2
Changes

Changes to manpage.1.

227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
.br
.I  "print 'Here <? and ?> will get mangled.';
.P
Which might actually be desirable in some cases. But use the
.B --tokenizer
mode otherwise for maximum resiliency.

The tokenizer on the other hand will ignore "\fBsoft close tags\fR". That is
\fI//?>\fR commented out close tags, which PHP itself never recognizes.
Those might decidedly be applied to eschew rewriting.
.P
They're not a widely known syntactic approach, but can keep php scripts
valid in XML/SGML processing context, are useful for script joining, yet
avoid the effusively feared trailing whitespace issues by themselves.

.SH "SEE ALSO"
.BR php (1) 
.BR recode (1)
.BR fromdos (1)

.IB http://fossil.include-once.org/phptags/

.IB http://stackoverflow.com/a/ 4465825







<
<
<
<
<
<
<
<








227
228
229
230
231
232
233








234
235
236
237
238
239
240
241
.br
.I  "print 'Here <? and ?> will get mangled.';
.P
Which might actually be desirable in some cases. But use the
.B --tokenizer
mode otherwise for maximum resiliency.









.SH "SEE ALSO"
.BR php (1) 
.BR recode (1)
.BR fromdos (1)

.IB http://fossil.include-once.org/phptags/

.IB http://stackoverflow.com/a/ 4465825