Rice: convert to media wiki format

2024-02-12T21:14:53Z

convert to media wiki format

← Older revision		Revision as of 21:14, 12 February 2024
Line 1:		Line 1:
	~~<markdown>~~		The theory used in Plover's dictionary applies some best practices for stroking certain words. There are some misstroke entries in the Plover dictionary that are very nice (and short), but may cause issues later on. For example, with [https://plover.wiki/index.php/Glossary#Word_Boundary word boundaries].
	The theory used in Plover's dictionary applies some best practices for stroking certain words. There are some misstroke entries in the Plover dictionary that are very nice (and short), but may cause issues later on. For example, with [~~word boundaries](~~https://~~github~~.~~com~~/~~openstenoproject/plover/wiki~~/Glossary#word~~-boundary)~~.

	~~###~~ And		<span id="and"></span>
			=== And ===

	The best practice for "and":		The best practice for "and":

	* Use `SKP` ✓		* Use <code>SKP</code> ✓

	This was chosen arbitrarily, because it is comfortable and there is little chance of a word boundary issue. "and" is a common word ending, so stenographers find it easy to remember to stroke `SKP`.		This was chosen arbitrarily, because it is comfortable and there is little chance of a word boundary issue. "and" is a common word ending, so stenographers find it easy to remember to stroke <code>SKP</code>.

	`SKP` is also allows the use of phrases like `SKPU → and you` and `SKPEU → and I`.		<code>SKP</code> is also allows the use of phrases like <code>SKPU → and you</code> and <code>SKPEU → and I</code>.

	There are some other strokes in the dictionary for "and". However, they are only to serve as a phonetic alternative when you are writing under pressure, and you can't remember `SKP`.		There are some other strokes in the dictionary for "and". However, they are only to serve as a phonetic alternative when you are writing under pressure, and you can't remember <code>SKP</code>.

	~~###~~ Con- words		<span id="con--words"></span>
			=== Con- words ===

	In Plover's theory, the best practice for con- words is:		In Plover's theory, the best practice for con- words is:

	* Use `KAUPB` to start words beginning with con. ✓		* Use <code>KAUPB</code> to start words beginning with con. ✓
	* Only use `KOPB` for the word "con".		* Only use <code>KOPB</code> for the word "con".

	However, when you look up a con word in Plover, it will only return misstrokes that contain the `KOPB` stroke. The reason for this is because the con- prefix doesn't require a dictionary entry.		However, when you look up a con word in Plover, it will only return misstrokes that contain the <code>KOPB</code> stroke. The reason for this is because the con- prefix doesn't require a dictionary entry.

	For example, for the word "conquer":		For example, for the word "conquer":

	* Use `KAUPB/KER` ✓		* Use <code>KAUPB/KER</code> ✓
	* Do not use `KOPB/KER` ✘		* Do not use <code>KOPB/KER</code> ✘

	Other words are not easy to write phonetically because they are to be briefed. For example: `T-PB for "continue"`.		Other words are not easy to write phonetically because they are to be briefed. For example: <code>T-PB for "continue"</code>.

	~~###~~ Hyphen (-)		<span id="hyphen--"></span>
			=== Hyphen (-) ===

	The best practice for "-":		The best practice for "-":

	* `H-PB` ✓		* <code>H-PB</code> ✓

	Why `H-PB`? The reason is that `H-PB` is `H-N` in pseudo-steno, which short for hyphen.		Why <code>H-PB</code>? The reason is that <code>H-PB</code> is <code>H-N</code> in pseudo-steno, which short for hyphen.

	There are a set of misstrokes that use `H-B` instead. These are OK to use.		There are a set of misstrokes that use <code>H-B</code> instead. These are OK to use.

	~~###~~ Was		<span id="was"></span>
			=== Was ===

	The best practice for "was":		The best practice for "was":

	* `WAS` ✓ or		* <code>WAS</code> ✓ or
	* `WAZ`. ✓		* <code>WAZ</code>. ✓

	The default dictionary has `WA → was`, which is most of the time all right. However it can conflict in some cases. For example: `WA/TKPWOPB → wagon (not "was gone")` and `WA/TPHA/SA → wanna sa (not "was NASA")`.		The default dictionary has <code>WA → was</code>, which is most of the time all right. However it can conflict in some cases. For example: <code>WA/TKPWOPB → wagon (not "was gone")</code> and <code>WA/TPHA/SA → wanna sa (not "was NASA")</code>.

	~~###~~ Your		<span id="your"></span>
			=== Your ===

	The best practice for "your":		The best practice for "your":

	* Use`KWROUR` ✓		* Use<code>KWROUR</code> ✓
	* Do not use `KWRUR` ✘		* Do not use <code>KWRUR</code> ✘

	This is because `KWRUR` is a word ending. For example: `KHROES/KWRUR → closure` versus `KHROES/KWROUR → close your`.		This is because <code>KWRUR</code> is a word ending. For example: <code>KHROES/KWRUR → closure</code> versus <code>KHROES/KWROUR → close your</code>.

			<span id="period-"></span>
			=== Period (.) ===

	~~### Period (.)~~		The best practice for ".":
	The best practice for ".":

	* `TP-PL` ✓ or		* <code>TP-PL</code> ✓ or
	* `-FPLT` ✓		* <code>-FPLT</code> ✓

	The other strokes `-P` and `-PL` can be used, but there will be conflicts. For example, `WEUPL/-P` is "wimp" rather than "women." Similarly, `HEL` is "hell" but `HEL/PL` is "helm".		The other strokes <code>-P</code> and <code>-PL</code> can be used, but there will be conflicts. For example, <code>WEUPL/-P</code> is "wimp" rather than "women." Similarly, <code>HEL</code> is "hell" but <code>HEL/PL</code> is "helm".
	~~</markdown>~~

Rice: Created page with " The theory used in Plover's dictionary applies some best practices for stroking certain words. There are some misstroke entries in the Plover dictionary that are very nice (and short), but may cause issues later on. For example, with [word boundaries](https://github.com/openstenoproject/plover/wiki/Glossary#word-boundary). ### And The best practice for "and": * Use `SKP` ✓ This was chosen arbitrarily, because it is comfortable and there is little chanc..."

2024-02-06T04:01:42Z

Created page with "<markdown> The theory used in Plover's dictionary applies some best practices for stroking certain words. There are some misstroke entries in the Plover dictionary that are very nice (and short), but may cause issues later on. For example, with [word boundaries](https://github.com/openstenoproject/plover/wiki/Glossary#word-boundary). ### And The best practice for "and": * Use `SKP` ✓ This was chosen arbitrarily, because it is comfortable and there is little chanc..."

New page

<markdown>
The theory used in Plover's dictionary applies some best practices for stroking certain words. There are some misstroke entries in the Plover dictionary that are very nice (and short), but may cause issues later on. For example, with [word boundaries](https://github.com/openstenoproject/plover/wiki/Glossary#word-boundary).

### And

The best practice for "and":

* Use `SKP` ✓

This was chosen arbitrarily, because it is comfortable and there is little chance of a word boundary issue. "and" is a common word ending, so stenographers find it easy to remember to stroke `SKP`.

`SKP` is also allows the use of phrases like `SKPU → and you` and `SKPEU → and I`.

There are some other strokes in the dictionary for "and". However, they are only to serve as a phonetic alternative when you are writing under pressure, and you can't remember `SKP`.

### Con- words

In Plover's theory, the best practice for con- words is:

* Use `KAUPB` to start words beginning with con. ✓
* Only use `KOPB` for the word "con".

However, when you look up a con word in Plover, it will only return misstrokes that contain the `KOPB` stroke. The reason for this is because the con- prefix doesn't require a dictionary entry.

For example, for the word "conquer":

* Use `KAUPB/KER` ✓
* Do not use `KOPB/KER` ✘

Other words are not easy to write phonetically because they are to be briefed. For example: `T-PB for "continue"`.

### Hyphen (-)

The best practice for "-":

* `H-PB` ✓

Why `H-PB`? The reason is that `H-PB` is `H-N` in pseudo-steno, which short for hyphen.

There are a set of misstrokes that use `H-B` instead. These are OK to use.

### Was

The best practice for "was":

* `WAS` ✓ or
* `WAZ`. ✓

The default dictionary has `WA → was`, which is most of the time all right. However it can conflict in some cases. For example: `WA/TKPWOPB → wagon (not "was gone")` and `WA/TPHA/SA → wanna sa (not "was NASA")`.

### Your

The best practice for "your":

* Use`KWROUR` ✓
* Do not use `KWRUR` ✘

This is because `KWRUR` is a word ending. For example: `KHROES/KWRUR → closure` versus `KHROES/KWROUR → close your`.

### Period (.)
The best practice for ".":

* `TP-PL` ✓ or
* `-FPLT` ✓

The other strokes `-P` and `-PL` can be used, but there will be conflicts. For example, `WEUPL/-P` is "wimp" rather than "women." Similarly, `HEL` is "hell" but `HEL/PL` is "helm".
</markdown>

Misleading Strokes in Plover's Dictionary - Revision history

Rice: convert to media wiki format