[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lojban] "salty"



Earlier i invented {krumami}. gismu would make the word unrecognisable. https://groups.google.com/d/topic/lojban/0rtjEXWTdVM/discussion

The new algorithm: https://groups.google.com/d/topic/lojban/QdZb0Cg2RhI/discussion

According to that algorithm
ISO-code - lojbanisation - frequency
cmn siani 0.246117399315609
eng salti 0.213872071597789
spa salado 0.094630165833114
ara malix 0.090023690444854
hin namkin 0.084890760726507
ben nonta 0.05672545406686
rus salion 0.051855751513556
por salgado 0.048828639115557
jap ciokarai 0.03224532771782
pun saluni 0.028691760989734
deu saltsig 0.027375625164517
fra sali 0.024743353514083

Whenever several translations were possible i tried to use those that could raise the overall rating. E.g. i chose "saluni" in Pujnajbi cuz it's similar to other languages.

If we try to use synonyms in Hindi and Bengali we get:

cmn siani 0.246117399315609
eng salti 0.213872071597789
spa salado 0.094630165833114
ara malix 0.090023690444854
hin lavanaiukt 0.084890760726507
ben labanakt 0.05672545406686
rus salion 0.051855751513556
por salgado 0.048828639115557
jap ciokarai 0.03224532771782
pun saluni 0.028691760989734
deu saltsig 0.027375625164517
fra sali 0.024743353514083


Now we have a problem. It would allow us {salni} if we hadn't already {sarni} for triangle. This possible conflict is described in http://dag.github.io/cll/4/14/
A quite reasonable rule I'd say. It's a pity it's not used when creating lujvo with short rafsi.

So I suggest removing {sarni}. It won't make {salni} a winner but at least would let it in.



On Sat, Dec 21, 2013 at 1:56 PM, Paul Rapoport <coronacoreanici@gmail.com> wrote:
Also, I'd assumed that a basic taste like umami would need a gismu as well.


On Sat, Dec 21, 2013 at 4:54 AM, Paul Rapoport <coronacoreanici@gmail.com> wrote:
You mean the letter-counting one? I thought I had. Those are the numbers in parentheses in the previous email. I thought it only cared about those 6 languages though.


On Sat, Dec 21, 2013 at 3:45 AM, Gleki Arxokuna <gleki.is.my.name@gmail.com> wrote:
I mean did you run the algorithm counting ratings of generated gismu?

http://dag.github.io/cll/4/14/

Mandarin: "siani" ("x" in pinyin is rather "si" than "c")
Hindi: "namakin"
Urdu: "namakin"
Spanish: "salado"
English:"salti"
Arabic: "malix"
Russian: "sylion"
Portuguese: "salgado"
French "sali"
German: "saltsig"
Japanese: "copai" / "ciokarai"
Bengali: ???
Punjabi: ???
Javanese: ???
Wu: ???
Marathi: ???
Telugu: ???
Vietnamese: ???


On Sat, Dec 21, 2013 at 12:29 PM, Paul Rapoport <coronacoreanici@gmail.com> wrote:
It seems OK to me. I'm not sure what you mean. What do you mean by standard algorithm?
E: salti (4)
C: cian (2)
S: salado (3)
R: solenyy (3)
H: namakina (2)
A: malx (2)

As for definition: salty seems sufficient for an English definition, because that refers to table salt/sea salt/cooking salt. A "perfect example" of NaCl (ctisilna vrusi) would definitely work.


On Sat, Dec 21, 2013 at 2:52 AM, Gleki Arxokuna <gleki.is.my.name@gmail.com> wrote:
lorxus added to jbovlaste
salni  = x1 is salty/briny to observer x2.

See also silna, xamsi, titla, slari, kurki. This word is oddly missing; note that silna can mean sweet lead acetate, sour sodium citrate, bitter magnesium sulfate, or umami (which also needs a word!) sodium glutamate, so "silna vrusi" is almost meaningless.

Is everything okay to you? I mean may be we should have used the standard algorithm?
What is the etymology of this word?
Russian:"solion"
English:"solti"
etc.

Besides, I suggested that we used a taste prototype for it, namely NaCl and/or KCl.

For now I can't accept neither sounding nor definition.

--
You received this message because you are subscribed to the Google Groups "lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban.
For more options, visit https://groups.google.com/groups/opt_out.


--
You received this message because you are subscribed to the Google Groups "lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban.
For more options, visit https://groups.google.com/groups/opt_out.