Menu
▾
▴
phpwebsite-developers
|
From: Don S. <do...@se...> - 2003-01-14 19:08:48
|
In trying to port some documentation over to pagemaster, I noticed that I have a lot of references to variables inside < and > chars, like "<pid>". The problem is pagemaster is interpreting this as an attempted HTML tag and stripping it out. I have a lot of different references so adding every one to the allowed_tags var isn't reasonable. < and > get altered by pagemaster so they literally display "<" or ">" respectively. Is there a way to get those chars to display? Don. |
|
From: Mike N. <mh...@us...> - 2003-01-14 19:36:38
|
On Tue, 2003-01-14 at 11:08, Don Seiler wrote: > In trying to port some documentation over to pagemaster, I noticed that I > have a lot of references to variables inside < and > chars, like "<pid>". > The problem is pagemaster is interpreting this as an attempted HTML tag > and stripping it out. I have a lot of different references so adding > every one to the allowed_tags var isn't reasonable. < and > get > altered by pagemaster so they literally display "<" or ">" > respectively. Don, PageMaster may need to be modified, so it doesn't convert & to & if & is followed by a ;. > Is there a way to get those chars to display? Unknown by me. -- Mike Noyes <mhnoyes @ users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ |
|
From: Adam M. <ad...@tu...> - 2003-01-15 17:58:27
|
Pagemaster does not parse the input or output text in it's own code. It relies on core functions called parseInput() and parseOutput() respectively. These functions may need to be revised to allow for some of these cases. I will get some input for the dev guys here and if any of you have some ideas, please let us know. Adam > On Tue, 2003-01-14 at 11:08, Don Seiler wrote: >> In trying to port some documentation over to pagemaster, I noticed >> that I have a lot of references to variables inside < and > chars, >> like "<pid>". The problem is pagemaster is interpreting this as an >> attempted HTML tag and stripping it out. I have a lot of different >> references so adding every one to the allowed_tags var isn't >> reasonable. < and > get altered by pagemaster so they >> literally display "<" or ">" respectively. > > Don, > PageMaster may need to be modified, so it doesn't convert & to & if > & is followed by a ;. > >> Is there a way to get those chars to display? > > Unknown by me. > > -- > Mike Noyes <mhnoyes @ users.sourceforge.net> > http://sourceforge.net/users/mhnoyes/ > http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: Take your first step towards giving > your online business a competitive advantage. Test-drive a Thawte SSL > certificate - our easy online guide will show you how. Click here to get > started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers --------------------------------------------------------------------- Adam Morton Developer - Electronic Student Services http://phpwebsite.appstate.edu Founder - Appalachian Linux Users Group http://alug.appstate.edu |
|
From: Mike N. <mh...@us...> - 2003-01-15 19:18:50
|
On Wed, 2003-01-15 at 10:04, Adam Morton wrote:
> Pagemaster does not parse the input or output text in it's own code. It
> relies on core functions called parseInput() and parseOutput()
> respectively. These functions may need to be revised to allow for some of
> these cases. I will get some input for the dev guys here and if any of
> you have some ideas, please let us know.
Adam,
Thanks for the correction to my erroneous assumption.
Testing might be simplified, if a single entity format is allowed. I
suggest Unicode compliant &#xxxx; hex entities. This string should be
fairly easy to check for.
Unicode Character Name Index
http://www.unicode.org/charts/charindex.html
Alternately, a raw edit mode could be implemented, that bypasses all
parsing. This mode should probably only be available to deities.
> > On Tue, 2003-01-14 at 11:08, Don Seiler wrote:
> >> In trying to port some documentation over to pagemaster, I noticed
> >> that I have a lot of references to variables inside < and > chars,
> >> like "<pid>". The problem is pagemaster is interpreting this as an
> >> attempted HTML tag and stripping it out. I have a lot of different
> >> references so adding every one to the allowed_tags var isn't
> >> reasonable. < and > get altered by pagemaster so they
> >> literally display "<" or ">" respectively.
> >
> > Don,
> > PageMaster may need to be modified, so it doesn't convert & to & if
> > & is followed by a ;.
> >
> >> Is there a way to get those chars to display?
> >
> > Unknown by me.
--
Mike Noyes <mhnoyes @ users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/
|
|
From: Mike N. <mh...@us...> - 2003-01-15 19:25:50
|
On Wed, 2003-01-15 at 11:24, Mike Noyes wrote: > Testing might be simplified, if a single entity format is allowed. I > suggest Unicode compliant &#xxxx; hex entities. This string should be > fairly easy to check for. Ugh. One of these days I'll learn to proofread my posts. Entity example should be: � < = < > = > > Unicode Character Name Index > http://www.unicode.org/charts/charindex.html -- Mike Noyes <mhnoyes @ users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ |
|
From: Matthew M. <ma...@tu...> - 2003-01-16 15:41:38
|
I have made some code changes to parseInput and parseOutput to try and help in this regard. First, the person who is entering data needs to put [code][/code] around their text. parseInput will then only strip tags from data OUTSIDE the 'code' bracket tags. Next when parseOutput displays the text, all the tags within the code bracket tags will display as is (ie <, &rt;). The ampersands will be changed into & If the module developer uses both functions, it should allow for what you require and let people post code examples. Matt -- Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu |
|
From: Don S. <do...@se...> - 2003-01-16 15:45:15
|
Will [code]'ed text be displayed in a fixed-width font? Don. On Thu, 16 Jan 2003, Matthew McNaney wrote: > I have made some code changes to parseInput and parseOutput to try and > help in this regard. > > First, the person who is entering data needs to put [code][/code] around > their text. > > parseInput will then only strip tags from data OUTSIDE the 'code' bracket > tags. > > Next when parseOutput displays the text, all the tags within the code > bracket tags will display as is (ie <, &rt;). The ampersands will be > changed into & > > If the module developer uses both functions, it should allow for what you > require and let people post code examples. > > > Matt > |
|
From: Mike N. <mh...@us...> - 2003-01-16 16:19:56
|
On Thu, 2003-01-16 at 07:47, Matthew McNaney wrote: > I have made some code changes to parseInput and parseOutput to try and > help in this regard. >=20 > First, the person who is entering data needs to put [code][/code] around > their text. >=20 > parseInput will then only strip tags from data OUTSIDE the 'code' bracket > tags. >=20 > Next when parseOutput displays the text, all the tags within the code > bracket tags will display as is (ie <, &rt;). The ampersands will be > changed into & >=20 > If the module developer uses both functions, it should allow for what you > require and let people post code examples. Matt, Thanks for working on this problem. Unfortunately, your solution doesn't work when Unicode is required in normal text. Example: K.-P. Kirchd=C3=B6rfer http://leaf-project.org/mod.php?mod=3Duserpage&menu=3D14&page_id=3D7 --=20 Mike Noyes <mhnoyes @ users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ |
|
From: Matthew M. <ma...@tu...> - 2003-01-16 16:50:32
|
> Thanks for working on this problem. Unfortunately, your solution doesn't > work when Unicode is required in normal text. Example: Mike, Please give me an example. I am not sure I understand what is needed. -- Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu |
|
From: Matthew M. <ma...@tu...> - 2003-01-16 16:56:58
|
Please take a look at the recent commit and look at parseOutput and parseInput. Let me know if that is what you are refering to. Thanks :) Matt -- Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu >> Thanks for working on this problem. Unfortunately, your solution >> doesn't work when Unicode is required in normal text. Example: > > Mike, > > Please give me an example. I am not sure I understand what is needed. > > > -- > Matthew McNaney > Internet Systems Architect > Electronic Student Services > Appalachian State University > Phone: 828-262-6493 > phpwebsite.appstate.edu > ess.appstate.edu > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: Thawte.com > Understand how to protect your customers personal information by > implementing SSL on your Apache Web Server. Click here to get our FREE > Thawte Apache Guide: > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers |
|
From: Mike N. <mh...@us...> - 2003-01-16 17:43:48
|
On Thu, 2003-01-16 at 09:03, Matthew McNaney wrote:
> Please take a look at the recent commit and look at parseOutput and
> parseInput.
>
> Let me know if that is what you are refering to.
Matt,
I should look at the code instead of trying to interpret your post.
Sorry. I think you accounted for Unicode hex entities with the following
regex.
$text = preg_replace("/&([^#])/", "&\\1", $text);
http://res1.stddev.appstate.edu/horde/chora/co.php/phpws_core/core/Text.php?r=1.43
--
Mike Noyes <mhnoyes @ users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/
|
|
From: Matthew M. <ma...@tu...> - 2003-01-16 17:04:35
|
> Will [code]'ed text be displayed in a fixed-width font? I was thinking it should be <pre>'ed. That ok? Matt |
|
From: Don S. <do...@se...> - 2003-01-16 17:07:02
|
Should be fine. Don. On Thu, 16 Jan 2003, Matthew McNaney wrote: > > Will [code]'ed text be displayed in a fixed-width font? > > I was thinking it should be <pre>'ed. That ok? > > Matt > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: Thawte.com > Understand how to protect your customers personal information by implementing > SSL on your Apache Web Server. Click here to get our FREE Thawte Apache > Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > > |
|
From: Mike N. <mh...@us...> - 2003-01-16 17:09:45
|
On Thu, 2003-01-16 at 08:56, Matthew McNaney wrote: > > Thanks for working on this problem. Unfortunately, your solution doesn'= t > > work when Unicode is required in normal text. Example: >=20 > Mike, >=20 > Please give me an example. I am not sure I understand what is needed. =C3=B6 =3D ö K.-P. Kirchd=C3=B6rfer <a href=3D"/devel/kapeka/">K.-P. Kirchdörfer</a> http://leaf-project.org/mod.php?mod=3Duserpage&menu=3D14&page_id=3D7 Zvon Character Search http://www.zvon.org/other/charSearch/PHP/search.php Unicode Character Name Index http://www.unicode.org/charts/charindex.html I'll take a look at parseOutput and parseInput shortly. --=20 Mike Noyes <mhnoyes @ users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ |
|
From: Don S. <do...@se...> - 2003-01-16 17:17:27
|
You are hurting my pine with your special chars. :( Don. On Thu, 16 Jan 2003, Mike Noyes wrote: > On Thu, 2003-01-16 at 08:56, Matthew McNaney wrote: > > > Thanks for working on this problem. Unfortunately, your solution does= n't > > > work when Unicode is required in normal text. Example: > >=20 > > Mike, > >=20 > > Please give me an example. I am not sure I understand what is needed. >=20 > =C3=B6 =3D ö > K.-P. Kirchd=C3=B6rfer > <a href=3D"/devel/kapeka/">K.-P. Kirchdörfer</a> > http://leaf-project.org/mod.php?mod=3Duserpage&menu=3D14&page_id=3D7 >=20 > Zvon Character Search > http://www.zvon.org/other/charSearch/PHP/search.php >=20 > Unicode Character Name Index > http://www.unicode.org/charts/charindex.html >=20 > I'll take a look at parseOutput and parseInput shortly. >=20 >=20 |
|
From: Matthew M. <ma...@tu...> - 2003-01-16 17:31:39
|
I have two versions of the parse functions. For the characters <, >, & : Normal makes the characters < &rt; and & Unicode version makes them < , >, and & Which should be the final commit? -- Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu |
|
From: Matthew M. <ma...@tu...> - 2003-01-16 17:41:05
|
> Normal makes the characters < &rt; and & Should read < > and & Matt |
|
From: Mike N. <mh...@us...> - 2003-01-16 18:01:44
|
On Thu, 2003-01-16 at 09:37, Matthew McNaney wrote:
> I have two versions of the parse functions.
>
> For the characters <, >, & :
>
> Normal makes the characters < &rt; and &
> Unicode version makes them < , >, and &
>
> Which should be the final commit?
Matt,
I prefer the Unicode hex entity to the named entity.
Unicode hex entities:
+ Better support in browsers
+ Ability to display more characters
+ Standard format for entity string (easier to test for)
- Syntax not as widely used as named entities
Named entities:
+ Syntax known by most website developers
- String length varies with name (harder to test for)
- Not all SGML named entities are supported by browsers
--
Mike Noyes <mhnoyes @ users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/
|
|
From: Don S. <do...@se...> - 2003-01-17 17:24:36
|
Will all these recent changes make it difficult for me to import pages I've been loading into a phpws install from last week's CVS into the final 0.9.0? Same for menus. Don. |
|
From: Matthew M. <ma...@tu...> - 2003-01-18 15:01:26
|
> Will all these recent changes make it difficult for me to import pages > I've been loading into a phpws install from last week's CVS into the > final 0.9.0? Same for menus. It shouldn't. However if you find out otherwise, let me know. Matt -- Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X