Return-path: Envelope-to: jbovlaste-admin@lojban.org Delivery-date: Thu, 18 Dec 2025 21:32:56 -0800 Received: from [192.168.123.254] (port=53678 helo=jiten.lojban.org) by 54872a72d4fc with smtp (Exim 4.96) (envelope-from ) id 1vWT6k-0014nd-04 for jbovlaste-admin@lojban.org; Thu, 18 Dec 2025 21:32:56 -0800 Received: by jiten.lojban.org (sSMTP sendmail emulation); Fri, 19 Dec 2025 05:32:53 +0000 From: "Apache" To: ByronJohnsonFP@gmail.com Reply-To: webmaster@lojban.org Subject: [jvsw] Definition Edited At Word baunpli -- By bairyn Date: Fri, 19 Dec 2025 05:32:53 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Message-Id: X-Spam-Score: 0.0 (/) X-Spam_score: 0.0 X-Spam_score_int: 0 X-Spam_bar: / In jbovlaste, the user bairyn has edited a definition of "baunpli" in the language "English". Differences: 9,9c9,11 < ni'o Recommended ways to explicitly declare the former (scope of permanent switch): «sei baunpli be fi lo vitno»; and the latter (scope as UI) «sei baunpli be fi lo ki'irmapti be zo .ui». «fi'o te baunpli» may also be used, especially after cmavo aliases or contractions like {co'i'e} (e.g. «co'i'e fi'o te baunpli lo vitno»), as well as similar, likely shorter constructs, including {ve'u'ai} (for permanent switch) and {ve'i'ai} (for UI scope). --- > ni'o Recommended ways to explicitly declare the former (scope of permanent switch): «sei baunpli be fi lo vitno»; and the latter (scope as UI) «sei baunpli be fi lo ki'irmapti be zo .ui». «fi'o te baunpli» may also be used, especially after cmavo aliases or contractions like {co'i'e} (e.g. «co'i'e fi'o te baunpli lo vitno»), as well as similar, likely shorter constructs, including {ve'u'ai} (for permanent switch) and {ve'i'ai} (for UI scope). > > ni'o See also: {jo'au}. Old Data: Definition: $x_1=p_1=b_2$ uses language / language feature / complete language / language dialect or variation / dictionary / semantics / other language standard or specification or open source fork $x_2=p_2=b_1$ with scope / for text / purpose / to express / communicate $x_3=p_3=b_3$; $x_1$ is using / declaring language / language extension $x_2$. Notes: A fu'ivlization of {baupli} (fu'ivla synonym variant), especially suited for the purpose of language declarations, e.g. with (or without) {sei}. This can be used to specify a language dialect, feature, variation, or complete standard, optionally with precision; analagous to Haskell LANGUAGE pragma declarations and gcc -std standard specifications. Example: «sei baunpli be la {vajli'epoitau} mi ca tcidu fi la bangu lojbo mulno» (＝＝ «{co'i'e'au'i} mi ca tcidu fi la bangu lojbo mulno»). ni'o Scope is vague and unspecified without «fi» being declared, but generally by default, if {baunpli} stands out on its own, it means a permanent language switch / change for the remaining text, and if {baunpli} is attached / occurs right after a given cmavo (including «.i» for a single bridi, unless the bridi is on its own and only includes {baunpli} related functionality), it is limited to that cmavo's group much like the scope of UI attachment. ni'o Recommended ways to explicitly declare the former (scope of permanent switch): «sei baunpli be fi lo vitno»; and the latter (scope as UI) «sei baunpli be fi lo ki'irmapti be zo .ui». «fi'o te baunpli» may also be used, especially after cmavo aliases or contractions like {co'i'e} (e.g. «co'i'e fi'o te baunpli lo vitno»), as well as similar, likely shorter constructs, including {ve'u'ai} (for permanent switch) and {ve'i'ai} (for UI scope). Jargon: Gloss Keywords: Word: language declaration, In Sense: specifying language Word: using language, In Sense: language declaration Place Keywords: New Data: Definition: $x_1=p_1=b_2$ uses language / language feature / complete language / language dialect or variation / dictionary / semantics / other language standard or specification or open source fork $x_2=p_2=b_1$ with scope / for text / purpose / to express / communicate $x_3=p_3=b_3$; $x_1$ is using / declaring language / language extension $x_2$. Notes: A fu'ivlization of {baupli} (fu'ivla synonym variant), especially suited for the purpose of language declarations, e.g. with (or without) {sei}. This can be used to specify a language dialect, feature, variation, or complete standard, optionally with precision; analagous to Haskell LANGUAGE pragma declarations and gcc -std standard specifications. Example: «sei baunpli be la {vajli'epoitau} mi ca tcidu fi la bangu lojbo mulno» (＝＝ «{co'i'e'au'i} mi ca tcidu fi la bangu lojbo mulno»). ni'o Scope is vague and unspecified without «fi» being declared, but generally by default, if {baunpli} stands out on its own, it means a permanent language switch / change for the remaining text, and if {baunpli} is attached / occurs right after a given cmavo (including «.i» for a single bridi, unless the bridi is on its own and only includes {baunpli} related functionality), it is limited to that cmavo's group much like the scope of UI attachment. ni'o Recommended ways to explicitly declare the former (scope of permanent switch): «sei baunpli be fi lo vitno»; and the latter (scope as UI) «sei baunpli be fi lo ki'irmapti be zo .ui». «fi'o te baunpli» may also be used, especially after cmavo aliases or contractions like {co'i'e} (e.g. «co'i'e fi'o te baunpli lo vitno»), as well as similar, likely shorter constructs, including {ve'u'ai} (for permanent switch) and {ve'i'ai} (for UI scope). ni'o See also: {jo'au}. Jargon: Gloss Keywords: Word: language declaration, In Sense: specifying language Word: using language, In Sense: language declaration Place Keywords: You can go to to see it.