blissymbolics / blissymbols

A database of all official Blissymbols, and their definitions
http://blissymbolics.github.io/blissymbols
GNU General Public License v3.0
24 stars 5 forks source link

How do you want to help out? #3

Open heatherleaf opened 6 years ago

heatherleaf commented 6 years ago

If you are interested in Blissymbolics, and want to help out in some way, please leave a comment here! Also, if you are developing resources for Blissymbolics you can mention and link to them in a comment. If we're lucky there could be new collaborations and even ideas for applications and projects.

coraharmonica commented 6 years ago

Hi heatherleaf! I'm programming a reading application called Blisscribe (found here) which translates text to Blissymbols. Since Blissymbols are grammar-flexible as well as visual, I thought they would make an ideal supplement for reading/learning foreign languages. Another inspiration for this project was to use machine learning to translate words without Blissymbol definitions to new (compound) Blissymbols. I've also been working on a Blissymbols WordNet. As yet, translating text to Blissymbols still isn't perfect, so I've been trying various approaches to improve translations--significantly, it seems a semantic component is necessary.

I'd love to collaborate with others working with Blissymbols, especially those interested in helping port it to WordNet and adding a semantic component. Anyone interested in collaborating can also email me at blisscribe [at] gmail [dot] com.

matlun commented 6 years ago

Hi coraharmonica, and most welcome to this spot! I heard from Hannes hl222ih that you have already established direct contact which is great. Great also that you get in touch right at the time when Hannes and I have teamed up with heatherleaf and the staff at KARP/Språkbanken in order to update and maintain this GitHub resource and the Bliss lexicon at KARP. Hannes and I will surely want to discuss your ambition to link Bliss to WordNet, which is also something that he and I very much would like to see, as some kind of a continuation of what I and friends once started as part of the Concept Coding Framework effort and www.conceptcoding.org. I haven't had time to look much at your Blisscribe, but it looks very interesting, and make me associate to the Simplipedia prototype that heatherleaf and a student of his developed in collaboration with me and some colleagues some years back - a quite interesting start that would deserve some further addition of more elaborated semantic and grammatical sophistication to improve the translation results.
Looking forward to collaborate with you!

coraharmonica commented 6 years ago

Thanks for the warm welcoming Mats! I think we've already emailed each other in the past months, I'm the same Cora who requested resources for my translation project a while ago. It's nice to get back in touch!

I believe Hannes invited you to our Blissymbols chatroom on Slack. I posted 2 JSON files which map Blissymbol BCI-IV# to WordNet synset ID # (one file maps to WordNet 3.0, the other to 3.1) on the #blissymbols channel. You can also find the files here on GitHub (under bci_blissnet_3.0 and bci_blissnet_3.1), where I also have other Bliss-WordNet files (in particular blissnet.py, which maps Bliss-names to synset strings and may be more legible).

Bliss-WordNet integration seems a key step for improving translations as well as improving support for Blissymbols. I would love to hear your input on what more we can do to link Blissymbols to WordNet (as well as the Open Multilingual WordNet), and your knowledge on more sophisticated methods of semantic/grammar parsing : )

martin12333 commented 6 years ago

broken links: the files bci_blissnet* , etc., seem to be moved to https://github.com/coraharmonica/blisscribe/tree/master/bliss_online/bliss_webapp/translation/resources/data

matlun commented 6 years ago

Welcome Martin, and thanks for finding the current link to Cora's resources!

coraharmonica commented 6 years ago

Thanks Martin! I updated both of the links in my original comment to reflect the new file locations.