Hi Akhilesh,
Your research looks good. Hunspell and Liang algorithm (you mean for
hyphenation obviously, not search and replace) were also in my list.
Looking forward to read your proposal.
For https://musescore.org/en/node/89866, I will comment there.
lasconic
2016-03-12 11:48 GMT+04:00 akhilesh <akhileshs...@gmail.com>:
> Hello,
>
> I am a third year undergrad Computer Science student, and I've used
> musescore for a while now. I play the piano and occasionally compose a few
> scores. I am pretty much comfortable with C++ and Qt. I've also been able
> to
> compile the source and get it running.
>
> I was particularly interested in working with spell checking,
> auto-hyphenation and search and replace, as I find it rather tiring myself
> to manually hyphenate every time I fill in lyrics. I did go through online
> tools, but the problem with existing ones is that proper nouns aren't
> hyphenated at all. This is because they probably use a dictionary approach,
> and there are too many proper nouns to make a dictionary out of. As noted,
> LaTex like algorithms give issues with one-letter syllables. However, I do
> not agree that using a dictionary based approached is a good idea because
> words like proper nouns and slang are ever-increasing in lyrics these days.
> Or maybe a dictionary is a good way to start?
>
> Here's my rough approach to the text utilities idea:
>
> 1) Could we use hunspell (http://hunspell.github.io/) for starters? Most
> editors use it these days if I'm not wrong.
>
> 2) Since what's unique to spell checking in musescore is the hyphens- what
> about an approach to treating the hyphens induced due to syllable split as
> some sort of "soft hyphens", like browsers do to html files? That way, the
> mandatory hyphens would be enforced by the spell checker because they have
> to be grammatically so, and the syllabification will be ignored during
> spell
> check
>
> 3) For find and replace, the algorithm given in "Word Hy-phen-a-tion by
> Com-put-er" https://tug.org/docs/liang/liang-thesis.pdf seems to be the
> base
> used in LaTex et al, so with some modification, we should be able to
> accomodate single letter syllables. Also, I'm thinking we could maintain a
> small dictionary but only for exceptions.
>
> I am excited to dive in to working on the project. To get familiar with the
> code, I am currently working on the issue:
> https://musescore.org/en/node/89866. Do tell me if I my approach looks
> fine
> and any advice on where I can get started. Also, it would be great if you
> could give me a heads-up on where I could look for the code that displays
> the piano output when the notes are being played (issue-related). Sorry for
> the long post!
>
> Regards,
> Akhilesh
>
>
>
> --
> View this message in context:
> http://dev-list.musescore.org/Gsoc-2016-Text-utilities-tp7579644.html
> Sent from the MuseScore Developer mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
> _______________________________________________
> Mscore-developer mailing list
> Mscore-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
Mscore-developer mailing list
Mscore-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mscore-developer
