r/EncapsulatedLanguage • • Jul 20 '20

Considering my post on the SVO, here’s another poll to see if I changed anyone’s mind

1 Upvotes

SVO or SOV?

19 votes, Jul 23 '20
11 SVO
8 SOV

r/EncapsulatedLanguage • • Jul 24 '20

Name Proposal The name of the language

1 Upvotes

I have been trying to find a good name for the encapsulated language.

The goal of this language is to "store as much scientific and mathematical knowledge as possible" in order to "facilitate an intuitive understanding of the world around us". Dare I say, in order to make the speaker inherently wise?

The Latin word for wise is 'sapiens' and the word for very wise is 'persapiens'.

https://latin-dictionary.net/search/latin/persapiens

So, I propose that the name of the encapsulated language is derived from the Latin word persapiens (very wise).

There are many possibilities for the name, to mention a few:

  • pers

  • persa

  • persap

  • persapi

  • persapien

  • persapiens

  • ...and many more, if it will be combined with some other word or modified in some other way (although I don't see the need for that)

This proposal does not specify the final name, it just specifies that the name is derived from the Latin word 'persapiens'.

If this proposal is confirmed, the final name will be searched for/defined in the subsequent steps.

P.S.: This is not part of the proposal, but as a joke, a speaker of this language could be refered to as Homo persapiens


r/EncapsulatedLanguage • • Jul 27 '20

Phonology Proposal Remove the phoneme /ɣ/

1 Upvotes

We suggest to remove /ɣ/ from the phoneme inventory. The reason is that /ɣ/ is a cross-linguistically an uncommon sound. This will make the language harder to learn.

The issue is that /ɣ/ might break the encapsulation. For that, we suggest adopting /j/ as a voiced counterpart of /x/. /j/ is currently unpaired and is phonetically quite close to /ɣ/.

The bonus point of this proposal is that every consonant in this language is pairable. /m-n/ /p-b/ /t-d/ /k-g/ /f-v/ /s-z/ /x-j/ /r-l/


r/EncapsulatedLanguage • • Jul 19 '20

Phonology Proposal Draft Proposal for the Removal of the Trill

2 Upvotes

This would be quite a minor change to the phonology, but I believe that such a change to remove the trill would be widely appreciated, as many English (and non-English) speakers have a particular trouble pronouncing this sound (myself included).

Furthermore, it is my belief that because the trill is notoriously difficult for English speakers, having such a sound would most certainly limit public interest in the project as a whole, or rather, would in a sense "put them off."

Now, there are other phonemes like the velar fricatives that are also quite hard for most people, but there is a difference. The velar fricatives serve as an end to maintain a sort of pattern within the phonology, which follows this project's main goals, regardless of the difficulty. In essence, pattern trumps difficulty (or at least that's the way I perceive it). The trill, however, is both difficult and does not serve to fulfill any sort of pattern that I am aware of, and so is simply unnecessary.

I am not, however, in favor of abolishing rhotic consonants altogether. I believe that a perfectly good substitute for the trill should be the flap/tap phoneme. This sound is generally regarded to be far easier to pronounce than the trill, and may help to remove further unnecessary phonetic difficulties.

Definitively, I propose that we replace the trill with the alveolar tap.


r/EncapsulatedLanguage • • Aug 22 '20

An idea for a Chinese-style classifier system

3 Upvotes

Edit: Added some clarification about classifiers

Currently, we have words like tsān wil khan that generally mean yellow but more accurately mean a color of 9 lightness and hue rotation of 2.

But what if we wanted to say 9 yellow dogs? We couldn’t say tsān tsān wil khan [dog] without being confused.

In addition to that, mathematics and science is central to every aspect of this language so I believe large portions of this language will be built in similar ways. Numbers will probably become some of the most common words in our language.

Therefore, I propose we introduce a chinese-style classifier system. This will have the following two major benefits:

  • It will enable us to separate the numbers used for plurality from the numbers used in word / idea creation.

  • It will enable us to encapsulate even more data.

How do Chinese classifiers work?

Chinese classifiers take on the following structure:

[Number] [Classifier] [adjective] [noun]

Here are some examples of classifiers being used to express singularity of nouns:

一只猫[one] [classifier for animals and utensils] [cat]
一个人[one] [classifier for individuals] [human]
一双筷子[one] [classifier for pair] [chopsticks]
一匹马[one] [classifier for horses] [horse]
一条鱼[one] [classifier for long things] [fish]

Some things to note about classifiers in general:

  • Almost all classifiers mean "of" except those that represent some fuzzy logic.

  • Every noun has a default classifier otherwise it just uses 个.

  • The noun’s classifier doesn’t describe it (there are some exceptions).

  • The noun’s classifier only changes in fuzzy logic expressions (words like “some” etc).

  • The purpose of the classifier is to link the number with its adjective and noun.

As you can probably see above, there is a logic to Chinese classifiers but this logic often doesn’t encapsulate anything useful. For example, classifying all fish as long even when there are small and circular fish isn’t really useful. It’s also not very useful to classify horses as horses.

How can we use Classifier Words?

I now want to go back to my colour example to show how this could potentially be useful. This example is purely for demonstration purposes.

Instead of saying tsān tsān wil khan [dog] when we want to say 9 yellow dogs, we could instead say tsān [color classifier] tsān wil khan [dog].

In the classifier example, we encapsulate some useful information about what kind of construction this is and we nicely divide the plurality from the word itself.

In fact, if this system was adopted it might make the current word, wil (meaning color) redundant as a classifier might be sufficient.

Feedback

This isn’t my final proposal. I’m seeking feedback on how this system can be improved.


r/EncapsulatedLanguage • • Jul 11 '20

Official Proposal Official Phonology Proposal: Group Two Vote (Round Two)

0 Upvotes

Hi all,

We’ve just completed the first round of voting. The second round of voting has now started.

Ensure you read the comments before voting as they may affect your vote!

In this thread, you'll vote for the phonology that you believe best fits the aims and goals of our language. Whichever phonology wins majority support by the end of day two of the vote will move on to round three of voting.

The vote duration has been reduced from three days to two days due to the vast majority of votes being placed within the first 24 hours.

I urge you to follow each link and explore the phonology in full before making your final vote.

Proposal 1 (Devono_knabo)

The full proposal can be found here.

Proposal 2 (Koallary)

The full proposal can be found here.

15 votes, Jul 13 '20
8 I vote for Proposal 1 (Devono_knabo)
7 I vote for Proposal 2 (Koallary)

r/EncapsulatedLanguage • • Jul 11 '20

Official Proposal Official Phonology Proposal: Group One Vote (Round Two)

0 Upvotes

Hi all,

We’ve just completed the first round of voting. The second round of voting has now started.

Ensure you read the comments before voting as they may affect your vote!

In this thread, you'll vote for the phonology that you believe best fits the aims and goals of our language. Whichever phonology wins majority support by the end of day two of the vote will move on to round three of voting.

The vote duration has been reduced from three days to two days due to the vast majority of votes being placed within the first 24 hours.

I urge you to follow each link and explore the phonology in full before making your final vote.

Proposal 1 (ArmoredFarmer)

The full proposal can be found here.

Proposal 2 (Flamerate1)

Please see the section titled Sub-2-Secondary-Proposals here. You’re not voting on the Primary or the Secondary Proposals as they have been rejected.

18 votes, Jul 13 '20
10 I vote for Proposal 1 (ArmoredFamer)
8 I vote for Proposal 2 (Flamerate1)

r/EncapsulatedLanguage • • Jul 25 '20

Name Proposal The name of the language 2

0 Upvotes

So i looked at u/HS1Dever and I saw the wise part of the name I kinda like that

what about children to be wise

pueressapi

the puer is the child

esse/ess is to be

sapiens is wise but sapi is shorter so

pueressapi or pueresapi

[pu.e.ɾes.sa.pi] or [pu.e.ɾe.sa.pi]


r/EncapsulatedLanguage • • Aug 02 '20

Second small step to a better number word system

2 Upvotes

Following the refining of the accepted proposal, that is number word system. I would like point out that some sound are harder to pronounce than other. I don't have the ability to choose an order of sound to make it easier but I can help to the shuffling of it.

The individual order of use are :

Least usedMost used
75E(11)X(10)01893642

To not break the current system, I also created an order of paired number which give us :

Least usedMost used
X,E6,74,50,18,92,3

It is paired this way to not break the way the sound are used on sixth and the eveness of the voicing.

The consonant used by the system are :

f v

s z

ʃ ʒ

x ɣ

t͡s d͡z

t͡ʃ d͡ʒ

Currently we have :

X,E6,74,50,18,92,3
t͡ʃ d͡ʒʃ ʒs zf vt͡s d͡zx ɣ

I would like your help to order those consonant to pair them with the paired number and make word more fluid. (In the sense that the most used word should contain the easiest sound and the least used word should have the hardest sound, to help integration)

This are my first draft, you can use this template in the comment section :

X,E6,74,50,18,92,3
x ɣt͡s d͡zʃ ʒf vs zt͡ʃ d͡ʒ

or :

X,E6,74,50,18,92,3
x ɣʃ ʒt͡s d͡zf vt͡ʃ d͡ʒs z

Those order are close to randomness than rational ordering, for that I ask help to finish this idea and make our language thrive.


r/EncapsulatedLanguage • • Jul 25 '20

Numbers Proposal Number System Proposal

1 Upvotes

Here is my proposal of number system

https://docs.google.com/document/d/1T_pKUkfHut57S0dXtJwrhKTooCApTX1rkCQD9wqucD4/edit?usp=sharing

Despite the goal is to optimize for the common usage, this number system is easily the most verbose number system out there. This is because my proposal relies on my phonotactics proposal which has a very restricted phonotactics system. However, it still ends up shorter than number system in my own natlang (Indonesian). It just strings together many more words into one.


r/EncapsulatedLanguage • • Jun 24 '20

Logo 3.0

Post image
1 Upvotes

r/EncapsulatedLanguage • • Aug 02 '20

Draft Proposal An Idea for Official Romanization

1 Upvotes

Hi all,

We'll soon need an official romanization for this language to make sure everyone is on the same page. This is what I believe the Official Romanization should be based on previous proposals and Discord discussions.

Why do we need a romanization?

Even though multiple script proposals are currently in development, we'll still need to type this language on computers and phones. The majority of devices won't support our script and Unicode support is probably a decade away.

Of course, we'll want to use our script whenever we can, but for those times when it's no possible we'll need an Official Romanization.

My proposal

I've only proposed romanizations for those IPA characters that can't be written in ASCII directly.

Consonants

IPARomanization
ʃsh
ʒzh
xkh
ɣgh
t͡sts
d͡zdz
t͡ʃch
d͡ʒjh
ɾr

Vowels

IPARomanization
iːii
yːyy
uːuu
eːee
oːoo
aːaa

Diphthongs

IPARomanization
ai̯ai
ei̯ei
oi̯oi
au̯au
eu̯eu
ou̯ou

Feedback

The only things I'm not sure on is the long vowels.

On phones it is easy to quickly write ā, ē, ī, ō and ū but there's no easy way to write /y/ with a line above it. Additionally, on computers it is a pain to write all of these. Therefore, I suggest we just double the vowel letter when it is a long.

Basically, I want to make this as ASCII friendly as possible.

I will admit though writing the number, 8 as dzyyn with a double /y/ is disgusting.

Totally looking for feedback!


r/EncapsulatedLanguage • • Jul 24 '20

Phonology Proposal phonetics

1 Upvotes

(V)C(C)V(V)

Consonant clusters

[pf] [ts] [kx]

problems:[pf] is hard to pronounce and because it is hard native speakers might one day get lazy and stop using this sound and if we use [pf] to encapsulate data the language falls apart

Final coda: if you don't know the final coda is the end sound of word that are not vowels

caT baCK baT raT riCK

final codas

[m] [n] [l] [ɾ] [k] [g] [t] [d] [p] [b] [j]

Now we have two proposals

Please for the love of god make more

I wasn't gonna make one but nobody was making them


r/EncapsulatedLanguage • • Sep 21 '20

Phonology Proposal Phonotactics rules cannot create homonyms.

1 Upvotes

Proposed state:

Phonotacts rules cannot cause homonyms.

This means a rule like /ti/ becomes /di/ is not allowed unless /di/ turns into something else already.

NOTE:

This does NOT mean homonyms are not allowed, just that they can't be created because of phonotactics.


r/EncapsulatedLanguage • • Jul 31 '20

Phonology Proposal Phonotactics and alternation proposal V2

1 Upvotes

This proposal is my new proposal. The aim is to create an easy to pronounce phonotactics and easy to apply alternation for encapsulation purposes. https://docs.google.com/document/d/1mzAqOwaSeebmj5lxqJ9SJTwBZyhlEfZknywKWj5--E0/edit?usp=sharing

The changes are:

  1. Improved alternation: no more counterintuitive /j/ treated as both nasal and voiced fricatives.

  2. Removed the section about syncopation as it doesn't work well with alternation.

  3. Removed the bimoraic restriction.

  4. Removed the phonological inventory change proposal. The free variation proposal still exists.

  5. Explanation of how alternation works.

By this proposal, my older proposal is now retired.


r/EncapsulatedLanguage • • Jun 08 '21

Just A Boss

0 Upvotes

r/EncapsulatedLanguage • • Jul 11 '20

I made a draft for a the flag

Post image
7 Upvotes

r/EncapsulatedLanguage • • Oct 24 '20

Grammar Proposal Noun Phrase Word Order

2 Upvotes

Current State

Word order is head initial and Harmonic. The Noun Phrase and Adpositional Phrase word order is undetermined.

Proposed State

The order of Words in a noun phrase is as follows

Noun, Determiner, adjectives, numerals, genitive phrase, relative clause

Adpositions come before nouns

Examples:

most sunny days
day-PL most sunny 

the old picture of fred that I found
* picture Def old GEN fred REL find-past 1st 

the 3 goats who ate the sandwich
goat-PL Def 3 Rel eat-past sandwhich Def

in the old rickety house 
** in house DEF old rickety
** in house DEF rickety old

(sentences in english glossing for the proposal)

* relative clauses use VSO word order despite that not being official

** either is fine

Reasoning:

This order is harmonic and head initial in line with current proposals. This word order will have little baring on encapsulation. This ordering leaves a lot of freedom moving forward and sets up a structure that provides guidance even if modified.

What's left to do:

An alignment strategy to indicate what argument nouns are to verbs needs to be chosen this may need marking in the noun phrase and will have to solve ambiguity in relative clauses.


r/EncapsulatedLanguage • • Jul 19 '20

The case AGAINST case markers

2 Upvotes

There's been discussions here in Reddit and in the Discord regarding case markers so I figured I'd put my thoughts into a single post that I can refer others back to.

I'm a speaker of Esperanto which uses one case marker (the accusative case). However, this isn't a pure accusative case, because it also acts like a locative case.

Now, I love the accusative case and use it a lot to create interesting sentences. Despite this, I feel we shouldn't include case markers in our language for a number of reasons:

The Accusative case is useless in most scenarios

It has been pointed out (Sherwood 1982) that the accusative marker –n in Esperanto (see also Bergen 2001) may be seen as redundant because of the predominant nature of the fixed SVO word order (for a detailed discussion of word order in Esperanto, see Jansen 2006, 2007, 2008, 2009). Sherwood notes that “many fluent speakers drop the accusative marker in conversation”

State-Of-the-Art: Esperanto Linguistics

Esperanto primary uses SVO although in short, fixed sentences SOV is also common among fluent speakers. This renders the accusative case useless in most scenarios besides poetry and music where it plays an important role. Even Japanese Esperanto speakers primarily use SVO in following the greater speaker community.

However, I must also point out that one study disagrees with this statement (this was pointed out to me after posting this thread):

I have even noted their correcting of the accusative errors of nonnative speakers. Finnish certainly supports direct object marking in some sentence patterns (and one of the markers happens to be -n, as in Esperanto), but there are important sentence patterns in Finnish (such as imperative sentences and impersonal passives) where the object is left unmarked. If Bergen’s theory were right, there should be at least sporadic missing accusatives in my children’s speech. And in Ian Fantom’s notes on his first child (GF), whose Esperanto was initially stronger than his English, the accusative ending is not only retained, but it is sometimes even used as a free morpheme.

http://www.ling.helsinki.fi/sky/julkaisut/SKY2006_1/1FK60.1.5.LINDSTEDT.pdf

The Accusative case is a constant pain point

I'm a fluent speaker of Esperanto and even I often accidentally drop the accusative in conversation. I've never met a speaker of Esperanto who fluently and consistently uses it correctly 100% of the time. Even speakers of languages that have an accusative case often mess it up in Esperanto. I've found this surprisingly high among German Esperanto speakers.

No other grammatical feature seems to cause so much pain.

Case markers will probably be rejected by our native speakers as they start to dominate the speaker base

Again I want to reference Esperanto as I feel our early development will mimic Esperanto's current development. The below extract describes to use of the accusative among native Esperanto speaking children:

Accusative usage closely reflects the role of case in the adstrate language, being used only where consistent with the other language, but not always ever there. Usage ranged from ≈100% with the Slovak-speaking children, to 0% with the French-speaking child, despite the fact that the French mother consistently used the accusative case in her own speech. Slovak has an accusative case on nouns, French does not. Other children used the accusative in only some of the contexts required by standard Esperanto, largely reflecting usage in their other language. There were other patterns to emerge as well. The Croatian child, for example, used the accusative only on personal pronouns immediately following a verb.

Native speakers of Esperanto

Despite 130 years of development, Esperanto has a relatively small native speaker because most Esperanto speakers consider native speakers against the internal ideals of the language. However, they do exist and there has been a number of studies done on them. Most of the studies reflect the above sentiment.

Our aims and goals are diametrically opposed to that of Esperanto. Our goal is to pass our language onto the next generation natively and as soon as possible. In fact, that's the very reason the language even exists. We're trying to create a generation of children who are geniuses.

The end goal of this project is to create a language parents can raise their children speaking natively alongside their other native languages.

I worry that if we introduce case markers then our first generation of native speakers may simply reject them. The only way I can imagine them adopting case markers and correctly using them is if our language 100% requires cases to even function. Technically, you can speak Esperanto without the accusative case and people would easily understand you.

What about Toki Pona, Ido and Mandarin Chinese?

Toki Pona doesn't have an accusative case but it does have a preposition which acts like an accusative case. I'm not 100% against. However, in Toki Ponas case sentences just wouldn't make sense without this preposition.

Ido uses the accusative case only when not using the default word order, SVO. I'd ague that this is the worst position implementation because then the speaker uses the accusative so rarely that it would even be more difficult for them to remember to use correctly.

Mandarin Chinese has a preposition 把 that's only used when the default word order SVO isn't followed. It's like Ido but instead of a case marker it uses a preposition. I think this is probably the best possible system if we want to free up the word order.


r/EncapsulatedLanguage • • Dec 20 '20

Draft Proposal Simple pronouns

2 Upvotes

Proposal 1: First and second person

Current state

No pronouns for first or second person exist.

Proposed state

The language includes only one first person pronoun (meaning "I"/"we"), using the placeholder word "ki", and one second person pronoun (meaning "you"), using the word "su". These words include lower persons, ie ki could mean "I" or "we (me and you)" or "we (me and them)" and so on.

Reason

It is clear that some pronouns are needed. Having a small number of pronouns increases the phonological space available for other words. The correct lower persons can almost always be inferred from context. This system is used in many natural languages.

Proposal 2: Third person and demonstratives

Current state

No third person pronouns or demonstratives exist.

Proposed state

Pronouns can be formed by saying the name of any consonant letter in the language. Each pronoun must refer to the same thing continuously - if you refer to something using the name for <p>, you must continue using that name for that thing throughout the rest of the conversation.

The pronouns can be used as third person pronouns (he/she/it/they) or as demonstratives (this/that/these/those). In some cases it may be necessary to explain their intended meaning the first time they are used. One way to do this is to use them as adjectives - "house P" means "this house, which I'm calling P."

Reason

This system allows you to unambiguously refer to something from earlier in the conversation, or something nearby to you. Many languages use the same words as third person pronouns and demonstratives, so this is naturalistic. In addition, having a small number of pronouns increases the phonological space available for other words. (We will probably have letter names anyway, so this phonological space is already used.)


r/EncapsulatedLanguage • • Jul 25 '20

Phonology Proposal Phonotactics Proposal

2 Upvotes

I created a proposal for phonotactics and also a phonological simplification proposal

https://docs.google.com/document/d/19mRIK0Ubgr_VFEzg1uwc-9zQHrarwAve0N51yXPzBOA/edit?usp=sharing

The phonological simplification is optional and will be removed if the community rejects it.

The goal of this design to make a phonotactics that is easy to pronounce by a speaker of a major language.


r/EncapsulatedLanguage • • Sep 29 '20

Informal Vote: Numeral-Phoneme Mapping Proposal

2 Upvotes

Hi all,

Since we've recently switched to base-6, we need new numeral-phoneme mappings (previously called Phonological Values) as the previous ones are no longer valid.

If you’re not sure what the Numeral-Phoneme Mapping System is then please see the Official Proposal on the Numeral-Phoneme Mappings (currently out-of-date).

Now, people have proposed different systems for the Numeral-Phoneme Mapping but a consensus still hasn’t formed over the phonemes to use. In essence, people have expressed dislike for each proposal due to different reasons. The only consensus that seems to have formed is over which vowels to use for the Numeral-Phoneme Mapping System. These vowels are i, a, u, e, y, o. Therefore, this informal vote won’t deal with the vowels, only the consonants of the Numeral-Phoneme Mapping System.

This informal vote is strictly over which phonemes to use. It doesn’t deal with the order of the phonemes in the Numeral-Phoneme Mapping System. We’ll deal with that next.

Proposed Set 1

/ʃ/ /s/ /f/ /ʒ/ /z/ /v/

To understand how encapsulation could possibly work with this proposed set, please see this post.

Proposed Set 2

/p/ /f/ /t/ /s/ /k/ /x/

There hasn’t been a post regarding this set, but it’s been discussed a few times in the Discord.

Proposed Set 3

/p/ /z/ /m/ /d/ /f/ /n/

To understand how encapsulation could possibly work with this proposed set, please see this post.

12 votes, Oct 01 '20
7 I prefer “Proposed Set 1”
1 I prefer “Proposed Set 2”
1 I prefer “Proposed Set 3”
3 I don’t care

r/EncapsulatedLanguage • • Aug 13 '20

Script Proposal Draft Proposal: Use -h instead of colon in alternative vowel romanization

2 Upvotes

Edit: This poll is UNOFFICIAL.

After looking over the different schemes for the alternative (NOT primary) vowel romanizations, an idea came to mind. What if an -h was attached to a vowel to mark it as being long? Let's compare this proposal with the current scheme.

  • Proposed: i, ih, y, yh, u, uh, e, eh, o, oh, a, ah

  • Current: i, i:, y, y:, u, u:, e, e:, o, o:, a, a:

  • IPA: /i, iː, y, yː, u, uː, e, eː, o, oː, a, aː/

To demonstrate the proposal, let's write the numbers 1-9 with the proposed system along with the current system and the IPA. The source for the numbers can be found here.

  • Proposed: vin, fun, ghyn, khan, zen, son, zhihn, shuhn, dzyhn, tsahn

  • Current: vin, fun, ghyn, khan, zen, son, zhi:n, shu:n, dzy:n, tsa:n

  • IPA: /fun, ɣyn, xan, zen, son, ʒiːn, ʃuːn, d͡zyːn, t͡saːn/

The benefits of using -h include:

  • A more natural resulting text as opposed to using colons,

  • Slightly easier to type and more accessible on the keyboard,

  • Follows this language's pattern of using -h to create digraphs, and

  • Can be used in variables in some programming languages that don't allow colons in variables.

Consequences of using -h include:

  • An extremely high proportion of h's in written text,

  • Harder to spot long vowels, and

  • Reduces the similarity of the written text to the IPA.

Vote whether you support this proposal or whether you prefer to keep the current alternative vowel romanization system. If you wish, post a comment explaining the reasons for your choice.

(The poll that decided the current alternative vowel romanization can be found here, and the official romanization proposal can be found here.)

24 votes, Aug 16 '20
11 The suffix -h (Support the proposal)
13 Colons (Keep the current system)

r/EncapsulatedLanguage • • Oct 22 '20

Official Proposal Official Proposal: Vote to make specific phonemes unwritten

2 Upvotes

Hi all,

u/AceGravity12 has raised an Official Proposal to make specific phonemes unwritten. This proposal has been approved by the Official Proposal Committee for voting.

Current State:

/l/, /j/, and /w/ are all written and have romanizations.

Proposed State:

/l/, /j/, and /w/ are all not written and don't have romanizations.

Reason:

According to the current Phonotactics, these phonemes can only be used as part of the Vowel pair realization. That means they can't be used for Encapsulation or any other system. Therefore, these phonemes shouldn't be written as it might visually break Encapsulation systems within the written language for the native speaker. This is already the case when one one looks at the current state of the Numeric Prefixes.

23 votes, Oct 24 '20
10 I vote to ACCEPT the Modification
8 I vote to REJECT the Modification
5 I don't care