Character Encodings with Tridion

This is probably a bigger subject to tackle in a single blog post, but I wanted to suggest the following if you ever run into a "strange character" or "my language looks wrong" problem with Tridion or any other content management system.

The correct Pavlovian response to character issues is to diligently search for any mismatched character encoding settings.

Troubleshooting Encoding Issues

Start with the source content (database, Word, text file) and work your way through the Content Management Explorer (CME), including schema filters and templates, then through the deployer, databases, presentation servers, databases and all the settings in between. Both Java and ASP.NET have global and page settings to confirm as well.

As a general guide to find all these settings, do an online search for {technology} + character encoding to find where to check for your given technology stack. Then check database settings with your DBA, web server settings with your development or design team, and Tridion settings with your implementation partner, developers, or support. Better yet, follow your content to determine where the issue happens and narrow down this long chain from authoring to presentation!

Logo Fun with the Tridion PowerTools

(05-Oct-2011) Update: See the final below or on the PowerTools Google Code site.

Previously on PowerTools...

Midas Rule of Open Source Projects

You may be familiar with the Golden Rule, where we treat others how we want to be treated?

Or maybe the Petroleum Rule, where we treat others how they deserve? Yes, like petrol it's crude by valuable.

How about a new one, the Midas Rule of volunteer work and Open Source projects?

Background

King Midas loved gold so much that he wished everything he touched would turn into gold. He got his wish but sadly... he got his wish and everything he touched would turn into gold. The fable had a useful lesson about greed and being careful for what you wish for, but I'm going to toss those parts aside and focus on the "ooh, you touched it" part.

The Midas Rule:

Whoever touches something first (takes initiative) and cares the most gets to decide what to do with it.

In other words, "yes you can, but you have to do the work." It's similar to licking or touching your sandwich so the other kids don't try to take your food. "Eww, you touched it!" Note this refers to actually poking, working on, and contributing to something beyond thinking or talking about it.

Tridion Schema Change

Someone has probably warned you to be careful when updating Tridion schema (the basic Tridion item that defines fields for Tridion components). So, what really happens after you update a Tridion schema?

First of all, be very careful when updating schema as this could potentially wipe out existing content.

These are relatively safe:

• add a new field
• update description on exsiting field
• change display type between radio, drop-down, or text select (might want to test this first)
• add additional options (or add keywords to a category used by a text field)

Dangerous:

• change xml name of a field or root
• change a schema namespace

Annoying:

• changing mandatory options (semi-dangerous, this may cause validation issues as well as confuse editors)
• change options (old existing selections will not change, except for keywords, at least with Tridion 2011)

If you don't have any components, then feel free to change away! However, once you have content (components based on said schema), a change will have the following affect.

None. No effect on content... yet!