• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 1.4.2
    • 1.4.1
    • None
    • Fedora 3 Linux Sun JDK 1.4.2 Mysql 3.x. Tomcat 5.0.28

      When we upgraded to 1.4.1 (like the improvements – 1.4.1 looks like it rocks!) CamelCase behaves much differently (in a bad way). I'll upload two screenshots and comment.

        1. no-camelcase.jpg
          no-camelcase.jpg
          171 kB
        2. with-camelcase.jpg
          with-camelcase.jpg
          174 kB

            [CONFSERVER-3361] CamelCase behaves much differently in 1.4.1 than 1.3.5

            The CamelCase link parser no longer turns ALLCAPS words into links.

            Charles Miller (Inactive) added a comment - The CamelCase link parser no longer turns ALLCAPS words into links.

            Hi, Elliot.

            Thanks for reporting this bug. We fixed a lot of problems with CamelCase links between 1.3 and 1.4, but it seems now the parser is being a bit too greedy, and trying to link things that don't contain any lower-case characters. We'll try to get this bug fixed for a future point-release of 1.4.

            Charles

            Charles Miller (Inactive) added a comment - Hi, Elliot. Thanks for reporting this bug. We fixed a lot of problems with CamelCase links between 1.3 and 1.4, but it seems now the parser is being a bit too greedy, and trying to link things that don't contain any lower-case characters. We'll try to get this bug fixed for a future point-release of 1.4. Charles

            First: I don't have screenshots comparing 1.3.5 to 1.4.1 which may be the most helpful. However hopefully I can cleary articulate what is the matter.

            For example, the following line is rendered differently from 1.3.5 to 1.4.1:
            'I maintain a WSRP4J source code tree in Subversion since WSRP4J has no formal releases or release cycle.'

            In 1.3.5 the text 'WSRP4J' was not treated as a CamelCase link. In 1.4.1 it is.

            Another example:
            'MSE trunk - may contain MSEL customizations and is copied from https://bajor.mse.jhu.edu/repos/public/trunk/apache/portals/wsrp4j/20050418.'

            In 1.3.5 'MSEL' wasn't camel case, in 1.4.1 it is.

            Another example:
            'Based on experiences it seems best practice to upgrade to the latest and greated Pluto Portal Driver and Pluto Portlet Container. This is especially true if you require Servlet Spec 2.4 and JSP 2.0 (for JSTL enhancements).'

            In 1.3.5 'JSTL' wasn't camel case, in 1.4.1 it is.

            It seems like words in all caps are considered camel case in 1.4.1 and they were not in 1.3.5. Can the behavior be reverted? I'd be happy to test a fix for you.

            Elliot Metsger added a comment - First: I don't have screenshots comparing 1.3.5 to 1.4.1 which may be the most helpful. However hopefully I can cleary articulate what is the matter. For example, the following line is rendered differently from 1.3.5 to 1.4.1: 'I maintain a WSRP4J source code tree in Subversion since WSRP4J has no formal releases or release cycle.' In 1.3.5 the text 'WSRP4J' was not treated as a CamelCase link. In 1.4.1 it is. Another example: 'MSE trunk - may contain MSEL customizations and is copied from https://bajor.mse.jhu.edu/repos/public/trunk/apache/portals/wsrp4j/20050418 .' In 1.3.5 'MSEL' wasn't camel case, in 1.4.1 it is. Another example: 'Based on experiences it seems best practice to upgrade to the latest and greated Pluto Portal Driver and Pluto Portlet Container. This is especially true if you require Servlet Spec 2.4 and JSP 2.0 (for JSTL enhancements).' In 1.3.5 'JSTL' wasn't camel case, in 1.4.1 it is. It seems like words in all caps are considered camel case in 1.4.1 and they were not in 1.3.5. Can the behavior be reverted? I'd be happy to test a fix for you.

            This is a screenshot from 1.4.1 with camel case enabled.

            Elliot Metsger added a comment - This is a screenshot from 1.4.1 with camel case enabled.

            Tried to do this with attach screenshot but my firefox 1.0.4 complained about applet security and wouldn't let me use the applet.

            This is a screenshot of 1 1.4.1 page with camel case disabled.

            Elliot Metsger added a comment - Tried to do this with attach screenshot but my firefox 1.0.4 complained about applet security and wouldn't let me use the applet. This is a screenshot of 1 1.4.1 page with camel case disabled.

              Unassigned Unassigned
              f17c49c9bf6b Elliot Metsger
              Affected customers:
              0 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: