You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Paul Benedict (JIRA)" <ji...@apache.org> on 2008/05/14 17:22:05 UTC

[jira] Commented: (STR-3144) Bean Taglib Documentation Has Been Unreadable FOR YEARS...

    [ https://issues.apache.org/struts/browse/STR-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43844#action_43844 ] 

Paul Benedict commented on STR-3144:
------------------------------------

If you want to fix it, please bug the developer of the taglib plugin. I've tried unsuccessfully. I would like the markup unescaped as well. If nothing can be done, removing the tag reference will be our only option. Want to try helping? I would like the extra help! 

http://maven-taglib.sourceforge.net/m2/

> Bean Taglib Documentation Has Been Unreadable FOR YEARS...
> ----------------------------------------------------------
>
>                 Key: STR-3144
>                 URL: https://issues.apache.org/struts/browse/STR-3144
>             Project: Struts 1
>          Issue Type: Bug
>          Components: Taglibs
>    Affects Versions: 1.2.7, 1.2.8, 1.2.9, 1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.3.6, 1.3.7, 1.3.8, 1.3.9
>         Environment: Any OS, any browser.
>            Reporter: Daniel A. Torrey
>
> The page http://struts.apache.org/1.3.8/struts-taglib/tagreference.html has been unreadable for YEARS.  The output has all of the markup tags escaped, so instead of rendering a paragraph tag as the end of a paragraph, the literal string "<p>" is written.  This makes the documentation worth very little.
> The last time I worked on a Struts app, in May of 2007, this was the case.
> The time before that that I worked on a Struts app, in October of 2006, this was the case.
> I've never reported it, as I've always thought that a) someone would fix it and b) you must have already been flooded by reports.  Or maybe nobody in the world except me actually reads documentation?
> This really should be fixed - it reflects very poorly on the development / documentation team.  I'd be glad to help, but I wouldn't have a clue where to start.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.