== Kate is going to have support for all languages in the world, right ? ==
(This can be useful to make a video where a user can choose the right subtitle language.)
::Right to left now supported (in my local version of xine). Language directionality can be overridden for each data packet from the default given in the headers. [[User:ogg.k.ogg.k]] Thurs Jan 31 13:29 UTC 2008
Be careful to make sure you're using the latest ISO standard (the one with the highest number) about languages. Because there are already a few so you could miss and end up using a wrong one. For the rest Kate looks very good ;)
:: Well, I am not certain about this - assuming you are referring to the latest RFC about language identification (the latest one is RFC 4646 I believe), then it is kinda complex, and I plan on supporting only part of it (yes, I know this is probably the standard's bane to have partial implementations). A full language tag can be quite long, and that RFC suggests a max "sane" size of 42 bytes. I have actually looked at what I'll do with that this weekend and am currently going with a 15 character string, which should handle easily things like primary tag and one (or two small) secondary tags, like "en_GB". Language plus country should cover most needs. However, it is possible to specify a language override in each data packet, if precision is required. [[User:ogg.k.ogg.k]] Wed Feb 6 12:08:03 UTC 2008
:: As a note, Kate uses UTF-8 only at the moment, and supports 31 bit UCS space (if a define is set, off by default), and current code points to 0x10ffff (eg, the currently defined 16 planes). I haven't quite ruled out UTF-16 and UTF-32, but if I add them in, libkate will have an auto conversion option for client code. Note that Kate doesn't concern itself with rules of ligatures, etc, defined by Unicode, that is up to the rendering client. [[User:ogg.k.ogg.k]] Wed Feb 6 12:16:05 UTC 2008
:::I have learned stuff about unicode. That was stupid of me if you think that I was asking about Unicode supporting it.
I was asking about Kate supporting all unicode features. (I didn't knew about Unicode having language, country,... mapping.) If you want to tell me that Unicode has a region, language, currency,... mapping on top of a character mapping. Then say it clearly.
Reading this page: [http://cldr.unicode.org/] All the localization stuff are under the name CLDR. CLDR is about the Unicode Common Locale Data RepositoryIt does a lot more than just language and region mapping. In fact, the other things are also very useful to have.
There is a region definitions header present in Kate. For the CLDR information, there needs to be a new header. Will there be a CLDR Definitions header or extended Unicode Definitions header somewhere in the future? Please?
: While I have not looked in depth at the CLDR, I don't think it's something that matters here.
:That said, I do agree with your argument. [[User:Ogg.k.ogg.k|Ogg.k.ogg.k]]
==Possible additions restrictions trap==
Please don't restrict your codec from having more than 256 colors in a bitmap.
What is your opinion about svgfonts?
: I have no opinion about svgfonts, as I do not know about them.
: I have proof of concept support for SVG images in Kate, but there are unresolved issues.
: It'd be nice to have SVG in, and I suppose (but only suppose) SVG fonts would automagically work then. [[User:Ogg.k.ogg.k|Ogg.k.ogg.k]]