Closed (outdated)
Project:
Copyright
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 Jul 2007 at 14:15 UTC
Updated:
16 Feb 2022 at 11:56 UTC
Jump to comment: Most recent
Comments
Comment #1
mdlueck commentedSeems Drupal core indeed handles NCR's correctly... having trouble getting the string to show up in this bug report. Trying again:
This is what we get instead of the "R".... "& #174;"
I had to insert a space. No space, though, in the NCR that is producing the error reported.
Comment #2
toemaz commentedPerhaps a stupid question, but are you using any text editor such as tinyMCE?
Is there any filter applied to the text?
Comment #3
mdlueck commentedNo we do not use an alternate editor such as tinyMCE.
No filters were applied to the affected text.
Comment #4
Robrecht Jacques commentedI think you need to type the UTF8 character directly and not use a NCR.
So for example, type: ® instead of & #174;. This works the same with all HTML entities, eg you can't use © but need to use © (the UTF8 character).
If you check on drupal.org, for example by changing the title to include a NCR, you will see that it does not convert & #174; into ®, but rather still displays & #174;. This is so for each textfield.
Now, it seems strange to me that on drupal.org, when typing in the description textarea, NCR do convert.
I'll investigate a bit more to see how the textareas of copyright module should behave (eg convert the NCR or not), similar to other textarea boxes in Drupal.
Testing:
- the UTF8 character: ®, ©
- the HTML entity & #174; or ©: ®, ©
So it seems that in title you can only use UTF8 chars, but in the body you can use both.
Comment #5
mdlueck commentedYou are correct when you state that in the title tag the NCR will not be converted. This is also true of JavaScript.
NCR's can only be used within "normal HTML document areas".
We had both the standard "Footer message" turned on, and Copyright. We used the same NCR in both places as we were thinking to migrate from "Footer message" and use Copyright instead.
As this module makes, at least our servers, cease 404'ing properly... we will let you get at least that corrected before we tinker further. ;-)
Comment #6
avpadernoI am closing this issue, as Drupal 4.7, 5, and 6 are now not supported.