login

Tick tock goes the clock...

JottiQ
Posted by White Hat (whitehat) on Apr 27 2011
News >> JottiQ

So, it might seem like I sort of forgot about this website. Or JottiQ, for that matter. There has been a definite lack of news and updates for sure.

Fact is - the interest in JottiQ translations has not been large at all, and I have been busy with other things. Additionally I have not found a method of implementing translation support that I am comfortable implementing; and I rather implement something right the first time around than half-ass it. Translations in JottiQ are a gimmick and a nice thing to have, and not a harsh requirement, nor do I get paid for it, so I have nothing holding me back from my idealistic approach in this matter.

To dig a bit further into the technical details: localization support seems to rely on me ('the developer') to compile and maintain the different languages whereas I wish to put any such support into the hands of translators (save for me putting them up for download). The simpler solutions I can invent myself would have their own limitations: I am not stupid enough to believe I can properly do so given the fact that at least half of the interest comes from people who wish to see eastern (right-to-left) languages supported.

Ideally, my requirements are for a free .NET (WPF) library that supports plain (XML?) files that translators can write and test for themselves. I want to implement it so any translations can be selected seperately from the OS language and whatnot: I know plenty of people (including myself) who hate it when some program decides to go irrevocably dutch on me due to my location despite having an english Windows installed. Finally, I need an efficient way to let the (native C++) shell extension profit from a translation.

Summary? There is a lot to keep in mind, and I am not getting paid. So, unless someone gives me a proverbial golden goose that lays golden eggs, translations will sadly be very low on my list of things to do. Feature requests are of course always welcome - new functionality is always fun to put in; it is merely a matter of viability. :) 

Back

Comments

Open-source By Guest on May 22 2011 at 8:27 AM
If you don't have much time to develop this tool and it does not generate revenue then why don't you make it open-source and let others contribute with their time and skills?

Add Comment
 
Design: byte-worker