Dismiss Notice
This Section is READ ONLY - All Posts Are Archived

[Known] Book Formatting Error Part deaux

Discussion in 'Crafting, Harvesting, Salvage, & Agriculture' started by Chrystoph Reis, Nov 23, 2018.

Thread Status:
Not open for further replies.
  1. Chrystoph Reis

    Chrystoph Reis Avatar

    Messages:
    940
    Likes Received:
    1,879
    Trophy Points:
    105
    Gender:
    Male
    11/24/2018 00:15
    Title: Book Formatting Error
    Reproduction Rate: 100%
    Blocker? No.
    Details: Page for and every page after are missing first 160+ characters on book page. See screenshots. This started in Release 58 after this change was made.
    • Book Formatting: We fixed an issue where formatting tags in books would not apply to text on subsequent pages.
    I thought republishing the book and adjusting formatting would work, when I found the bug.

    Steps to Reproduce: Try to publish a book with more than 3 pages.
    Open any pre-existing book created before tag change in Release
    User Specs:
    OS: Windows 10 (10.0.0) 64bit
    CPU: Intel(R) Core(TM) i7-7800X CPU @ 3.50GHz (12) System RAM: 16062
    GPU: NVIDIA GeForce GTX 1080 GPU RAM: 8079
    SotA.Win.64.855.Date.10.27.18
    Area: POT_mountain_metropolis_01_template/Shogun Ridge
    Area Display Name: Shogun Ridge
    Loc: (-253.2, 24.9, 95.7)
    Debug: UE9UX21vdW50YWluX21ldHJvcG9saXNfMDFfdGVtcGxhdGV8U2hvZ3VuIFJpZGdlfCgtMjUzLjIzOCwgMjQuODU0LCA5NS42OTcpfCgwLCAxLCAwLCAtMC4wMDkpfDQ3OS41NTExfDQ3Ljk2NDk2fDMuOTE4MjAz

    [​IMG]


    Update: This works if I remove any color formatting. Can I get a book formatting update on how to use colors properly?
     
    wizardsmoke and Jaesun like this.
  2. Serafina

    Serafina Portalarian Emeritus

    Messages:
    1,302
    Likes Received:
    1,658
    Trophy Points:
    113
    63135
     
    Jaesun likes this.
  3. wizardsmoke

    wizardsmoke Dev Emeritus Dev Emeritus

    Messages:
    701
    Likes Received:
    822
    Trophy Points:
    93
    Thank you for the detailed report! I believe that I have found and fixed the issue internally, so hopefully there will not be a part trois :p

    This fix will be published in Release 61.
     
    Jaesun likes this.
Thread Status:
Not open for further replies.