It maybe intresting somebody, for example russian user, here russian edition version for VertSms. Changes:
1. Russian number (ex. +7(code)1234567 and 8(code)1234567) work correctly.
2. Russian interface and ability to send messages to Russian
This only little patch, and he need install original prog.
It maybe intresting somebody, for example russian user, here russian edition version for VertSms. Changes:
1. Russian number (ex. +7(code)1234567 and 8(code)1234567) work correctly.
2. Russian interface and ability to send messages to Russian
This only little patch, and he need install original prog.
I'am sorry for my bad english
please use the development thread in the future if you have patches, mods etc.
perhaps gettext integration would be ideal? Would make it easier for different translations to be created. If a package is made, perhaps "vertsms-l10n-ru' would be a good idea for the above?
perhaps gettext integration would be ideal? Would make it easier for different translations to be created. If a package is made, perhaps "vertsms-l10n-ru' would be a good idea for the above?
Why different translation need to be made if you can take all the stuff from OS own localisation?
Why different translation need to be made if you can take all the stuff from OS own localisation?
Size. If all the translations are in the same program then it will grow exponentially, and on a mobile device space is precious. Plus, I don't want to download 10000 languages when all I can really understand is English and Korean.
This consideration is far more important IMHO than convenience. Another alternative would be to have the translation files on a server somewhere and have them downloaded on first run.
Not saying any of this should be considered now or in the near future though...
Size. If all the translations are in the same program then it will grow exponentially, and on a mobile device space is precious. Plus, I don't want to download 10000 languages when all I can really understand is English and Korean.
This consideration is far more important IMHO than convenience. Another alternative would be to have the translation files on a server somewhere and have them downloaded on first run.
Not saying any of this should be considered now or in the near future though...
hmmmm. I meant that why should you use localisation separately in your program if all localisation is in OS itself. I assume that you can use localisation from maemo itself?
hmmmm. I meant that why should you use localisation separately in your program if all localisation is in OS itself. I assume that you can use localisation from maemo itself?
localization can be done, but only interface. For message delivery in different languages use different encoding PDU-package.
For example, for russian language use 8-bit encoding, with the size of each character - 2 bytes.
That is why the maximum length of the message of 70 characters instead of 160.
localization can be done, but only interface. For message delivery in different languages use different encoding PDU-package.
For example, for russian language use 8-bit encoding, with the size of each character - 2 bytes.
That is why the maximum length of the message of 70 characters instead of 160.
I understood that that was the case here. So i just wondered that why should develeopers do localisation by themselves if itīs already integrated to Maemo. I do not know how it really works but feels just so weird that only way to implement multilangual simple interface is to use your own language localisation.
I understood that that was the case here. So i just wondered that why should develeopers do localisation by themselves if itīs already integrated to Maemo. I do not know how it really works but feels just so weird that only way to implement multilangual simple interface is to use your own language localisation.
