|
From: | Sayak Sarkar |
Subject: | Re: [m17n-list] Packaging bn-disha into m17n-contrib and system issues |
Date: | Sat, 3 Nov 2012 19:24:06 +0530 |
Hey Kenichi,
My apologies for the considerable delay in submitting the final version of the input method. I was a bit busy with my final examinations at college.
I've completed a thorough testing of the input method and have resolved most of the bugs that I could find in it. It turns out changing the version description of the input system to version 1.6.1 resolved most of the compatibility issues in the system.
I've tried and tested Disha to work seamlessly in Gnome based Fedora systems, notably Fedora 15 onwards. Although I haven't been able to do thorough testing on earlier systems, I have seen it work quite well in previous versions as well.
It would be great if you could you please incorporate bn-Disha to m17n-contrib.
The input method's repository can be found at: https://github.com/sayak-sarkar/Disha.
The Input layout's manual and documentation can be found at the project wiki: https://github.com/sayak-sarkar/Disha/wiki.
Please go through the same and let me know if anything further is required for the same.
Regards,
SayakOn Fri, Aug 31, 2012 at 5:28 AM, Kenichi Handa <address@hidden> wrote:
In article <CANrO7TfJJVD4pk_YBSJF1=-address@hidden>, Sayak Sarkar <address@hidden> writes:Oops, sorry. I have forgotten to update the library version
> Thanks a lot for the quick reply. I've tried making the changes that you
> suggested, however, as soon as I change (version "1.0.0") to (version
> "1.6.2"), m17n-edit stops identifying the disha input system. Is this due
> to some internal IM issues?
numbers in the code. So, even though the latest version is
1.6.3, the API for getting the library version returns
1.6.1 now. :-( So, please specify "1.6.1".
No, I didn't confirmed it. I just guessed.
> Now that you have confirmed that the application program related issues are
> due to the IM-engines,
Ok. I'll try to investigate what is wrong after reading
> there are a few features that I want to add to the
> input system.
> I'll also let you know once I'm done creating the proper test-cases for the
> issues and updating the steps for reproducing the problem.
that report.
Just send a diff or the whole new file to this list.
> Also, could you please let me know what's the procedure for submitting
> patches to the new system, once it is included into m17n-contrib?
---
Kenichi Handa
address@hidden
--
About Me:http://about.me/sayak_sarkar
Twitter: http://twitter.com/sayak_sarkar
Blog: http://sayaksarkar.wordpress.com
[Prev in Thread] | Current Thread | [Next in Thread] |