5 réponses à ce sujet

[J.O.G]

Is there a complete list of tags for text anywhere?

< b> < i> and < u > work but I can't seem to get any color tags to work. (tried < c> < color> and the NWN1 variant.)

So... No colorful item descriptions possible?

Modifié par J.O.G, 01 décembre 2009 - 06:23 .

[Challseus]

J.O.G wrote...

Is there a complete list of tags for text anywhere?

and work but I can't seem to get any color tags to work. (tried and the NWN1 variant.)

So... No colorful item descriptions possible?

Perhaps take a look at $Install_Dir/tools/Source/2DA/toolset/dialog_tags.xls? To be honest, I didn't see anything in there useful, but it may point you in the right direction.

Modifié par Challseus, 01 décembre 2009 - 06:29 .

[J.O.G]

I've seen it, but since < u> (underline) works but isn't in there, I don't think this really the whole thing.

[FollowTheGourd]

If the toolset wouldn't complain about invalid tokens, I believe the way you *would* get colour is to do something like [font color='red']Argh! [/font] - just include the HTML (but use angle brackets - I'm just sick of fighting the broken forum), but maybe we'd need to edit dialog_tags.xls and replace the GDA to define some more tokens.  It might be more complicated than that since the GUI seems to call back to the engine to do token substitution and who knows what it might do with elements it doesn't expect, but if worse comes to worst, it's possible to mod the GUI files to let
us define our own tokens, maybe just with a different delimiter that
the toolset's dialogue editor isn't going to fuss about.

At least dialog_tags.xls seems to define a mapping between dialogue tokens and HTML.

Also, I don't know how you got underline to work... the toolset won't let me save with it.

Modifié par FollowTheGourd, 02 décembre 2009 - 12:13 .

[J.O.G]

I tried it in item descriptions, works fine there. Spellchecking suggests but otherwise it saves fine.

Nope, just like , makes the text within the tags vanish completely (no space left between the displayed text and the separator line.

It's not a database issue either, the uti still has the full text.

Modifié par J.O.G, 02 décembre 2009 - 05:36 .

[FollowTheGourd]

Ah, I'd assumed you were talking about conversations for some reason. You might try RGB values instead of a name, like [font color='#ff0000'][/font], but that's how the GUI itself colour codes text in item popups. If that doesn't work, I'd have to figure out where it's breaking down along the way. It doesn't sound like it's getting read as plain text if certain markup tags work.

Modifié par FollowTheGourd, 02 décembre 2009 - 11:45 .