Naeso/Math: Difference between revisions
From FrathWiki
< Naeso
Jump to navigationJump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
==base== | {{PD}}<!-- | ||
Important note: When you edit this page, you agree to release your contribution into the public domain. If you don't want this or can't do this because of license restrictions, please don't edit. | |||
-->==base== | |||
{{V|10|FH|y|RJ|y|JH|y|BF|y}} | {{V|10|FH|y|RJ|y|JH|y|BF|y}} | ||
{{V|special terms for expressing hexadecimal numbers|RJ|y|JH|y|FH|y|BF|y}} | {{V|special terms for expressing hexadecimal numbers|RJ|y|JH|y|FH|y|BF|y}} |
Revision as of 07:40, 19 April 2011
This page has been released into the public domain. Important note: When you edit this page, you agree to release your contribution into the public domain. If you don't want this or can't do this because of license restrictions, please don't edit. |
base
10 — 4/0 (FH,RJ,JH,BF,/0)
special terms for expressing hexadecimal numbers — 4/0 (RJ,JH,FH,BF,/0)
How to form number words
- example: 813
eightonethree — 3/1 (FH,JH,BF,/RJ,)
- I will only propose number words with one syllable, making the above a lot easier to understand. —Fenhl 05:04, 26 October 2010 (PDT)
- I disagree since short words are easier to misunderstand. ~RJ
- Hopefully my proposal avoids this problem. I generated a set of phonologically-redundant words using this algorithm, tweaking the input file so its output overlapped as much as possible with Fenhl and MalfermitaKodo's proposals. --Jim Henry 15:52, 26 October 2010 (PDT)
- It would still cause issues with large and exact numbers. Namely when there are more numbers than the average person can hold in short-term memory. ~RJ
eighthundred-oneten-three — 2/2 (RJ,BF,/FH,JH,)
How to mark hex numbers
- I certainly do not want Naeso speakers to have to guess on whether a number is dec or hex. How do we avoid this? —Fenhl 04:43, 18 April 2011 (PDT)
number words
0
se — 4/0 (FH,RJ,JH,BF,/0)
1
a — 2/2 (FH,BF,/RJ,JH,)
- Redundancy is a feature, not a bug. ~RJ
tsai — 2/2 (RJ,FH,/JH,BF,)
tho — 3/0 (JH,FH,BF,/0)
2
dy — 3/0 (FH,JH,BF,/0)
3
fe — 2/2 (FH,BF,/RJ,JH,)
- Has anyone considered that this might be used to speak phone numbers over a staticyVoIP connection‽ ~RJ
efe — 2/2 (RJ,FH,/JH,BF,)
pu — 3/0 (JH,FH,BF,/0)
4
gi — 4/0 (FH,RJ,JH,BF,/0)
5
ba — 4/0 (FH,RJ,JH,BF,/0)
6
vo — 3/1 (FH,RJ,BF,/JH,)
vae — 2/1 (JH,FH,/BF,)
7
zu — 3/1 (FH,RJ,BF,/JH,)
zui — 2/1 (JH,FH,/BF,)
8
to — 2/2 (FH,BF,/RJ,JH,)
- Too similar to 6 ~RJ
lui — 2/2 (RJ,FH,/BF,JH,)
toa — 2/1 (JH,FH,/BF,)
9
na — 2/2 (FH,BF,/RJ,JH,)
- Too similar to ba —RJ
dzia — 2/2 (RJ,FH,/JH,BF,)
fel — 2/1 (JH,FH,/BF,)
ten
tthi — 1/2 (FH,/JH,BF,)
zym — 3/0 (JH,FH,BF,/0)
eleven
thoanh — 2/1 (JH,FH,/BF,)
zym a — 2/0 (BF,JH,/0)
- I think this is in regard to hex numbers, so zym a would be inappropriate here. —Fenhl 04:43, 18 April 2011 (PDT)
twelve
munh — 2/0 (JH,FH,/0)
zym dy — 2/0 (BF,JH,/0)
thirteen
munh — 1/2 (JH,/FH,BF,)
- Same as twelve —Fenhl 16:42, 10 April 2011 (PDT)
zym pu — 2/0 (BF,JH,/0)
syul — 2/1 (FH,JH,/BF,)
fourteen
doal — 2/1 (JH,FH,/BF,)
zym gi — 2/0 (BF,JH,/0)
fifteen
bem — 2/1 (JH,FH,/BF,)
zym ba — 2/0 (BF,JH,/0)
sixteen
dzim — 1/2 (JH,/FH,BF,)
zym vo — 2/0 (BF,JH,/0)
hundred
on — 2/1 (JH,BF,/FH,)
thousand
jol — 2/1 (JH,BF,/FH,)
onon / on on — 1/2 (BF,/JH,FH,)
- A hundred hundreds is ten thousand, not one thousand. --Jim Henry 10:49, 17 April 2011 (PDT)
ten thousand
djulnen — 0/2 (0/FH,JH,)
zym onon — 1/2 (BF,/JH,FH,)
zym jol — 1/0 (JH,/0)
hundred thousand
founh — 1/2 (BF,/FH,JH,)
million
tinem — 2/1 (FH,BF,/JH,)
jol jol — 1/1 (JH,/FH,)
Naeso | |
---|---|
General: | Voting • Member list • An Introduction to Naeso |
Phonology and orthography: | Phonology • Stress • Orthography • Transliteration |
Grammar: | Grammar • Suffixes • Prepositions |
Lexicon and corpus: | Naeso-English • English-Naeso • Proposed words • Swadesh • Names • Corpus of Sentences • Math |
Conlang relay torches: | LCC4 Relay |
This page is part of the project Naeso. We meet up to discuss changes in 'real time' in #naeso on Freenode. |