Confusing Text problem in 1.8Beta2

Having trouble with the game? Report issues and get help here. Read this first!

Moderators: Forum Moderators, Developers

Forum rules
Before reporting issues in this section, you must read the following topic:
Post Reply
Star Gazer
Posts: 110
Joined: April 6th, 2004, 10:06 am
Location: North Norfolk, UK

Confusing Text problem in 1.8Beta2

Post by Star Gazer » December 12th, 2009, 10:55 pm

I'm getting a problem when playing 'Legend of Wesmere' in the scenario 'Elves' Last Stand'. When switching to giving orders to the allies, the screen is failing to display the 'Exit' box from the pop-up orders menu. This managed to really confuse me as to how to get back out of the menu when I had finally decided what to do!! :roll:

I am running in Mac OSX 10.5.8 on a dual 4-core 2.8GHzMacPro, 8GB RAM, nVidia 8800GT video.

The console tells me this:
12/12/2009 22:30:19 [0x0-0x3c03c].org.wesnoth.Wesnoth[314] (process:314): Pango-CRITICAL **: _pango_engine_shape_covers: assertion `PANGO_IS_FONT (font)' failed
12/12/2009 22:30:27 [0x0-0x3c03c].org.wesnoth.Wesnoth[314] 20091212 22:30:27 error gui/layout: ttext::set_text text '<span size='big'>Exit</span>' has broken markup, set to normal text.
This second item would seem to be the culprit.

I've included a snapshot to display the problem.
Attachments
WesnothScreenSnapz001.pdf
Snapshot of visible error
(338.87 KiB) Downloaded 134 times

User avatar
Zarel
Posts: 700
Joined: July 15th, 2009, 8:24 am
Location: Minnesota, USA
Contact:

Re: Confusing Text problem in 1.8Beta2

Post by Zarel » December 13th, 2009, 1:59 am

...PDF?

You do realize that if you press Cmd+Shift+3, it'll take a screenshot in PNG format and put it on your desktop, right? And we could be seeing it in the webpage, instead of having to download some PDF...
Proud creator of the :whistle: smiley | I prefer the CC-0 license.

User avatar
Crab
Inactive Developer
Posts: 200
Joined: March 18th, 2009, 9:42 pm

Re: Confusing Text problem in 1.8Beta2

Post by Crab » December 13th, 2009, 12:29 pm

Fixed in [rev]40214[/rev], invalid markup was used in one of the configuration files. Fix will be available in the next wesnoth release.
Thanks for reporting.

Post Reply