localization

XML Schema (xsd)

Damn those documents get hefty quick, and I can’t quite seem to find a way to say a given element has an attribute that should reference an element in another container.


<!-- Given: -->

<xs:element name="Languages">
<xs:complexType>
<xs:sequence>
<xs:element name="Language">
<xs:complexType>
<xs:attribute name="Code" type="xs:language" use="required"/>
<!-- ... -->
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:element>

<!-- How do you bind ... ->
<xs:element name="Translations">
...
<xs:element name="Translation">
...
<xs:attribute name="Language" ref="/Languages/Language" refkey="Code"/>

Or is this validation just something you have to do yourself in code?

A far more painless unicode experience

Poor Ramp: When he had to localize our web sites and tools etc, he had to wrestle with Apache, Tomcat, Perl, MySQL 3.x, the billing system and an assortment of other tools to try and get everything talking UTF8.

I still use Roxen‘s webserver¬†for our internal management tools and systems, and by-and-large it just does the right thing. All the fancy features that Apache/Tomcat have added in the last 4-5 years – like JSP Tags – basic stuff in Roxen, and very much matured.

And UTF-8? Almost totally a walk in the park, which was surprising given the Roxen server I was running has an uptime of 20 months and the install itself is actually 5 years old…

Little Loc’ Marathon

Tuesday was a bit of a loss, I utterly failed to make notes last week on my plan for overcoming a bunch of Unicoding obstacles, so I spent most of Tuesday catching up.

I Had a package from England arriving yesterday (Wednesday) so I called in that I’d be late, I have to admit that as much as I intended to start working at 10am, I found myself making toast and eggs, having a coffee while I answered a few (work-related) calls, and then I sort of sauntered over to the computer and sat down.