[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [m17n-list] Packaging bn-disha into m17n-contrib and system issues
From: |
Kenichi Handa |
Subject: |
Re: [m17n-list] Packaging bn-disha into m17n-contrib and system issues |
Date: |
Fri, 31 Aug 2012 08:58:35 +0900 |
In article <address@hidden>, Sayak Sarkar <address@hidden> writes:
> 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?
Oops, sorry. I have forgotten to update the library version
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".
> Now that you have confirmed that the application program related issues are
> due to the IM-engines,
No, I didn't confirmed it. I just guessed.
> 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.
Ok. I'll try to investigate what is wrong after reading
that report.
> 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?
Just send a diff or the whole new file to this list.
---
Kenichi Handa
address@hidden