-
Bug
-
Resolution: Fixed
-
Medium
-
8.0.0, 8.0.1, 8.0.2
-
None
-
14
-
Severity 3 - Minor
-
41
-
Problem
Page tree view fails to render double byte chars and display question mark
Environment
Windows OS
Confluence 8.0
Postgres 13
Steps to Reproduce
- Install Postgres and create a database with:
- Encoding UTF-8
- Charset Windows English_US 1252
- Collation Windows English_US 1252
- Install Confluence 8.0 using the DB created with the above steps
- Create a page in a space with a double byte char in the title
- Publish the page and check the Page Tree view
Expected Results
Page tree display the double byte char
Actual Results
Question mark are displayed
Workaround
To get around this behaviour add the following to the JVM startup options:
-Dfile.encoding=UTF8
Notes
[CONFSERVER-81330] Page tree display double byte char as question mark
Remote Link | New: This issue links to "Page (Extranet)" [ 733318 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 727838 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 726182 ] |
Support reference count | Original: 13 | New: 14 |
Testing Notes |
Original:
WHW other action result which also used NoDecorator
WHW non UTF-8 data (when we enforcing Confluence default Charset) |
New:
WHW other action result which also used NoDecorator
WHW non UTF-8 data (when we enforcing Confluence default Charset) - don't need system property to by pass the behavior of NoDecorator. We could use Confluence default encoding instead |
Status | Original: Awaiting Merge [ 10064 ] | New: Waiting for Release [ 12075 ] |
Status | Original: In Review [ 10051 ] | New: Awaiting Merge [ 10064 ] |
QA Demo Status | Original: Not Done [ 14330 ] | New: Done [ 14331 ] |
QA Kickoff Status | Original: Not Done [ 14234 ] | New: Done [ 14235 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10051 ] |
Remote Link |
New:
This issue links to "Confluence Release › Release Confluence 8.0.X Milestone › issue-80- |