Hi David,

You say "the final result for English hyphenation should follow dictionary
hyphenation not pronunciation".

If I understand your point correctly. You disagree with Matthew Hindson
here
http://hindson.com.au/info/free/free-english-language-hyphenation-dictionary/
.He stated "The hyphenation in this dictionary is based upon how singers
sing syllables and text. The general rule is that each syllable should
begin with a consonant" and as an example "hyphenation = hy-phe-na-tion
(not hy-phen-a-tion, which makes more sense when read, but not when sung)."

If I understand your point correctly, you advocate for hy-phen-a-tion and
not hy-phe-na-tion. Right?

lasconic

2016-03-21 8:55 GMT+04:00 David Bolton <davidkbol...@gmail.com>:

> Akhilesh
>
> Regardless of what happens underneath (dictionary lookup or algorithm),
> the final result for English hyphenation should follow dictionary
> hyphenation not pronunciation. (This is true in every publication style
> guide I've come across).
>
> To use your example, 'e-di-to-"rin"-chief' would be the incorrect
> hyphenation. (It is less readable to English readers if you use
> non-standard hyphenation.) If MuseScore marked it as incorrect, that would
> be okay. (Even though it is a hyphenation mistake rather than a spelling
> mistake).
>
> Note: Hyphenation in other languages (like French and Spanish) usually
> follows pronunciation. Hyphenation for other languages can often be
> described with less than 30 rules.   It is just English that doesn't have a
> clear set of rules. As a result, most English speakers make frequent
> hyphenation mistakes (unless they are editors by training).
>
> If it is helpful I can post hyphenation rules for several other languages.
> It might take me a week or two.
>
> ---
> David Bolton
> On Mar 20, 2016 7:30 AM, "akhilesh" <akhileshs...@gmail.com> wrote:
>
>> Hello lasconic, hello all,
>>
>>   I'm proposing to work on text utilities for GSoC. I have a draft of the
>> idea, but I have a few things that I'm not able to wrap my head around.
>>
>> 1) *Spell checking hyphenated words:* On the GSoC 2014 page
>> (
>> https://musescore.org/en/developers-handbook/google-summer-code/ideas-2014#Proofing-tools-for-lyrics%3A-spellcheck-and-hyphenation
>> )
>> I came across:
>>
>> "Spell checking lyrics also takes some work beyond simply hooking up a
>> spellchecker. For example "ed-i-tor-in-chief" should pass spellcheck as
>> "editor-in-chief". You have to preserve some hyphens and drop others
>> before
>> the spellchecker recognizes the word"
>>
>> *QUESTION* is: wouldn't hyphens in the original word of a hyphenated word
>> confuse the hyphens that are induced due to syllabification? And hence, my
>> suggestion is we should treat all originally hyphenated words as
>> non-hyphenated in musescore.
>>
>> *EXAMPLE:* In the original word 'editor-in-chief', there's a hyphen "r-in"
>> but the user doesn't split the syllable that way in the lyrics (say his
>> lyrics are: e-di-to-"rin"-chief.
>> *
>> PROBLEM*: The spell checker would say the hyphen between "r-in" should be
>> present, but the user would say he wanted "rin" to be sung at as single
>> note, and making it "r-in" would confuse him into thinking that they had
>> to
>> be sung at separate notes.
>>
>> So can the spell checker forgive missing hyphens in the original word?
>>
>> --------------------------------------------------------------------------------------------------------------------------------------------------------
>> 2) *Hyphenation*:
>>
>> I was thinking of a hyphenation model where the user starts typing lyrics
>> from under a particular note (This can be the start note or any other
>> note)
>> and hyphenation happens on the fly, where next syllables keep spilling
>> over
>> to next notes.
>>
>> OR
>>
>> Another model would be where where the user enters the entire lyrics at
>> once, and the hyphenation happens after the entire lyrics have been
>> entered,
>> and each syllable is aligned with one note, starting from the first note.
>>
>> *QUESTION*: Which one of the above would be preferred as an implementation
>> model? I can think of merits to both.
>>
>> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>> 3) *Plugin*:
>>
>> Should the spell checker and hyphenator be implemented as separate
>> plugins?
>> (I am not sure how to decide which is a better paradigm, hence)
>>
>> It'd be great if you could help me out with these queries, after which I'd
>> like to have your advice on the implementation model I have in mind based
>> on
>> your inputs to the above.
>>
>> Thanks,
>> Akhilesh
>>
>>
>>
>> --
>> View this message in context:
>> http://dev-list.musescore.org/Gsoc-2016-Text-utilities-tp7579644p7579707.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=278785231&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=278785351&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=278785351&iu=/4140
_______________________________________________
Mscore-developer mailing list
Mscore-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mscore-developer

Reply via email to