It is wrong to group scripts as "Western", "CTL" and "Asian" in the font selection dialog.
There are several reasons for this, but the most important reason is that it is quite possible that people would use more than one "CTL" font in one document. This happens more often than many programmers would think.
Besides, most people don't know what "CTL" means. People who write Hindi, Arabic or Amharic, don't consider their language "CTL" or "complex" - for them it's quite simple. Finally, Hindi and Arabic are "CTL", while Chinese and Japanese are "Asian", even though all these languages are spoken in Asia, which adds to the confusion.
The right way to implement this is to allow font selection by language and script and not by arbitrary outdated grouping like "Western", "CTL" and "Asian". This is more or less the way it is done in HTML and CSS, where you can write <span lang="az-Arab">SOME AZERBAIJANI TEXT IN THE ARABIC SCRIPT</span> and then write the following CSS:
font-family: "Nice Azerbaijani Arabic font";
(Maybe this will require a change in the OpenDocument standard, too.)
You're basically stuck with the ODF standard with its three categories. Though maybe it could be possible to subvert that system and leave those distinctions in place and stick a layer on top of it alright.
The discussion on CTL is ongoing with the developers. As far as I've gleaned we're stuck with CTL and these worthless groups because of Microsoft. Most of us agree that we wish we could get rid of them or just enable them by default but the discussion is tricky and many opinions are being added. To see the discussion you can look here:
I am going to mark this as WONTFIX just because currently we are stuck with this implementation but we are definitely discussing alternatives as we move forward. I am adding PATCHESWELCOME to the whiteboard just in case a developer wants to try to redo the entire CTL/language system (it's a huge task to purge CTL and still make it compatible with Microsoft's stuff).