all groups > dotnet internationalization > march 2008 >
You're in the

dotnet internationalization

group:

Why does XAML not contain type information



Why does XAML not contain type information Jaakko Salmenius
3/16/2008 9:49:26 PM
dotnet internationalization: Hi,

In WIN32 we had RC that was relatively painless to localize no matter if you
used RC or binary localization.

Windows Forms has .resx that was much harder because .resx files do not
contains full information about the forms. For example component's
parent-child relationship, colors and many other can be figured out only by
reading source code or decompiling IL. Good thing is that .resx contains
type information of each property.

XAML contains compelete information in a structured XML format. However it
has two major drawbacks:

1) Properties do not have type information. There is not even way to make
difference between property and event. The only way is to know the component
and figure out property vs. event and the type of the data from elements
name. Thsi works for standard controls but not for unknown 3rd party
controls.

2) There is not information about the type of the window/page itself.

Overall I see lots of degeneration if Microsoft current resource formats.
Please for the next try (I bet there will be a new stuff coming in a year or
two) make sure that
- Format is structured (like XAML)
- It contains type information of all properties and there is way to make
difference beween property/event
- It contains information about its parent window or page
These extra information do not make fiel that much bigger.

It is very essential that resource file contains all necessary information
without needing to read several other file or hard code lots of information
to the process.

Best regards,
Jaakko Salmenius

AddThis Social Bookmark Button