Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-9674

Issues with Support for special and non-ASCII characters to the Externalize Strings Wizard for JSP

XMLWordPrintable

    • Hide
      An error existed where the special characters '\r' and '\n' that are part of the Property Key, were not displayed correctly when the Property Key contained more lines than initially shown. This caused the following error to appear: Unable to render embedded object: File (errorAfterWrongPropertyKeySelection.png) not found. The generated Property Key has been corrected by modifying the ExternalizeStringsUtils.java file by adding in single quotes as characters to be correctly replaced when formatting a web page. Property Key is now displayed correctly and the error no longer appears.
      Show
      An error existed where the special characters '\r' and '\n' that are part of the Property Key, were not displayed correctly when the Property Key contained more lines than initially shown. This caused the following error to appear: Unable to render embedded object: File (errorAfterWrongPropertyKeySelection.png) not found. The generated Property Key has been corrected by modifying the ExternalizeStringsUtils.java file by adding in single quotes as characters to be correctly replaced when formatting a web page. Property Key is now displayed correctly and the error no longer appears.
    • Documented as Resolved Issue

      comment originally from JBIDE-9203:

      Property Key is not selected correctly.
      When cursor position is within text containing more lines Property Key is selected with special characters '\r' and '\n' displayed not correctly

      When Property Key with more lines is used validator is displaying error

      I think translation should not include leading and trailing <EOL>, <CR>, <LF> characters of whole text paragraph because after translation is used formatting of web page source is lost i.e:

      <h1>
      Line1
      Line2
      Line3
      ...
      </h1>

      is replaced with

      <h1>#

      {Message.Line1}

      </h1>

      what can be confusing.

            dmaliarevich_jira Denis Maliarevich (Inactive)
            vpakan Vlado Pakan (Inactive)
            Isaac Rooskov Isaac Rooskov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: