[Talk-in] GSoC Idea -- Openstreetmap Indic Localization helper tool

[Anivar Aravind]

Dear all,

My previous mail to this list is under moderator approval. Just realized I
was not subscribed to the list.
So copy pasting it below

Thanks Srikant. I hope you want to propose it as Indic Project's idea list
for this GSoC. we submitted org application to google  and now in the
process of populating student project idea list[1]. Google will announce
selected organizations by this month.  The only change I wish to suggest on
the idea is possibilities in exploring libvarnam[2]  Integrations to the
suggestions architecture. Libvarnam is used by platforms such as
storyweaver.org.in for Indian language typing. For the idea we need one or
two mentors for guiding this idea. Indian language part we can also pool
existing expertise in our team.

Srikant, Can you mentor this ?


[1] https://gitlab.com/indicproject/gsoc-2017/edit/master/ideas-list.md
[2] http://varnamproject.org

Anivar Aravind
Executive Director
Indic Project
http://indicproject.org
http://twitter.com/indicproject

On Wed, Feb 15, 2017 at 7:39 PM, Yogesh K S <yogesh at itforchange.net> wrote:

> This tool is very much needed.
>
> This idea should perhaps be suggested on the GSoC 2017 Project Ideas page
> on OpenStreetMap wiki[1] or on the indicproject discuss site[2] for
> prospective students and community members to take a look at it.
> [1]https://wiki.openstreetmap.org/wiki/Google_Summer_of_
> Code/2017/Project_Ideas
> [2]https://discourse.indicproject.org/c/dev/gsoc
>
>
>
> On 02/14/2017 09:00 AM, Thejesh GN wrote:
>
> Awesome idea. We need it like now :)
>
> Let me know if you need any help in writing.
>
>
> Thej
> --
> Thejesh GN ⏚ ತೇಜೇಶ್ ಜಿ.ಎನ್
> http://thejeshgn.com
>
>
> On 13-Feb-2017 4:58 PM, "Arun Ganesh" <arun.planemad at gmail.com> wrote:
>
> Great idea Srikanth, this is definitely much needed. Maybe you can share
> the idea on the talk list as well for feedback.
>
> On Mon, Feb 13, 2017 at 2:35 PM, Srikanth Lakshmanan <srik.lak at gmail.com>
> wrote:
>
>> Hi,
>>
>> I wanted to suggest an idea to build a tool which could help in improving
>> the ease of localization of map data for openstreetmap. Currently, OSM
>> localisations are done manually by volunteer editors manually mostly. Some
>> editors have built custom tools to bulk upload localizations, but there is
>> no easy tool which could be easily used to localize manually / verify
>> machine-assisted localizations to improve the speed of localization in OSM
>> map data.
>>
>> Nomino[1] is a tool available to perform localization, but the tool is
>> unmaintained, doesnt offer suggestions. With Wikidata and google translate
>> API's we can reasonably ensure correctness of automated translation if they
>> match, when they dont match, it still provides reasonably good suggestions,
>> which users can just pick. Since we are dealing with names of places,
>> copyright issues dont arise. A tool, like Nomino, with suggestions from
>> Wikidata, Google translate integrating with OSM APIs would be of great
>> utility in increasing the pace of localizations, while ensuring that such
>> localizations are manually verified by user and not purely machine
>> translated.
>>
>> Let me know if this is acceptable GSoC idea, which students can work. I
>> can offer any help in improving this idea / project. Thanks.
>>
>> [1] http://nomino.openstreetmap.fr/
>>
>> --
>> Regards
>> Srikanth.L
>>
>> _______________________________________________
>> Talk-in mailing list
>> Talk-in at openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-in
>>
>>
>
> _______________________________________________
> Talk-in mailing list
> Talk-in at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-in
>
>
>
>
> _______________________________________________
> Talk-in mailing listTalk-in at openstreetmap.orghttps://lists.openstreetmap.org/listinfo/talk-in
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-in/attachments/20170215/a84faf86/attachment-0001.html>