If you want to reuse a style, create a custom style sheet for it, and apply it to text through the <style>
rich text tag.
A custom style can include opening and closing rich text tags, and leading and trailing text.
For example, you might want headings in your text to be big, red, bold, with an asterisk to either side and a line break at the end.
Instead of typing this for every heading:
<font-weight=700><size=2em><color=#FF0000>*Heading*</color></size></font-weight><br>
You can create a style, called H1
that includes all of that formatting, and then apply the style to your headings.
For instructions on how to create a custom style sheet, see Style-with-style-sheets in Get started with text
To use a custom style sheet in the rich text tag, reference the style sheet asset name and the style name: <style="assetName" name="styleName">
.
For runtime UI, if you have set a style sheet as the default style sheet in the UITK Text Settings, you can omit the asset name: <style="styleName">
. For example: <style="H1">This is heading 1</style>
.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.