text:
Palliative Pharmacotherapy/Drug-Specific Information/Opioids/Information About Specific Drugs/Non-Traditional Opioids/Buprenorphine

= Buprenorphine Basics =

Pharmacology
Buprenorphine is a semi-synthetic opioid derived from thebaine. Structurally, buprenorphine is different from other opioids in that it contains an N-CPM group.

Pharmacodynamics
Buprenorphine is most often classified as a "partial opioid agonist," however it's activity is more nuanced than that. This "partial agonist" description comes from the previous belief that buprenorphine is a partial agonist at μ opioid receptors as well as being an antagonist at δ and κ opioid receptors. It is the only FDA-approved drug with known activity at the ORL-1 receptor, at which it is an agonist.

Buprenorphine & Oral Morphine Equivalents (OMEs)
Due to its unique mechanism of action, it is not appropriate to design therapeutic regimens based on the OMEs of a given buprenorphine formulation. However, for knowledge's sake let's discuss how one would go about converting buprenorphine to OMEs.

The first step to doing this is to consider the bioavailability of each of the buprenorphine formulations.

Perioperative Management of Buprenorphine
A frequently asked question from primary teams and surgeons: what do we do with this patient's buprenorphine?

The American Society of Regional Anesthesia & Pain Medicine published a review regarding the perioperative management of buprenorphine in 2021. In this review, they recommended against the routine perioperative discontinuation of buprenorphine. Generally, patients receiving 16mg/day of buprenorphine or less, can be maintained on buprenorphine and treated with PRN "traditional" full mu opioid agonists for breakthrough pain, though these patients may require higher doses of the "traditional" full mu opioid agonists compared to patients not taking buprenorphine. Multimodal pain management strategies should always be utilized. If a patient is taking buprenorphine for OUD, the goal should be to taper the patient off of any other opioids aside from buprenorphine prior to discharge.

Several organizations have published their own guidelines or algorithms on the perioperative management of buprenorphine:

 * UCSF Guideline for the Perioperative Management of Buprenorphine Algorithm
 * Notably, this guideline advises that patients receiving 8mg buprenorphine per day or more may need to be tapered, compared to expert opinion and other guidelines that suggest a higher threshold of 16mg/day.
 * VA PBM Guidelines for the Perioperative Management of Buprenorphine Algorithm
 * Essentially the same as the UCSF algorithm, but threshold for high vs. low buprenorphine is 16mg/day.
 * VA PBM Perioperative Pain Management Guidance for Patients on Chronic Buprenorphine Therapy Undergoing Elective or Emergent Procedures full guidance document

= Buprenorphine Formulations = Buprenorphine comes in several different formulations, all of which are considered "long-acting" except for the IV injection. Regardless which formulation is chosen, it is important to educate patients and providers about the administration technique of the chosen formulation. Furthermore, if initiating buprenorphine inpatient, it is wise to check with nursing staff and gauge their familiarity with the buprenorphine product. Nursing staff education on buprenorphine may be necessary if they are unfamiliar.

In patients where there is a large "psychological" component to their pain, an oral medication may be more effective compared to buprenorphine transdermal. Patients are conditioned to expect pain relief after taking a medication, hence why a twice-daily buccal film or several-times-a-day SL tablet/film may be perceived as more effective for pain relief by the patient compared to a once-weekly transdermal patch. This is why sometimes patients report analgesia within minutes of taking a medication even when it is known that the absorption and onset of effects take hours – it isn’t that the medication started working sooner, it’s just psychology!

Buprenorphine Buccal Film
Practice Pearl: You may find it helpful to include the following directions in inpatient orders for buprenorphine buccal films:
 * Do not cut or tear the film. With a dry finger, place yellow side of film against the inside of cheek - press and hold in place for 5 seconds. Do not chew or swallow the film. Rinse water around teeth after fully dissolved (~30 minutes). Wait one hour after application before brushing teeth.

Buprenorphine Transdermal Patch
See Also
 * PCNOW Fast Fact # 268 - Low-Dose Buprenorphine Patch for Pain

Buprenorphine Sublingual Tablet
The analgesic effects of buprenorphine SL tablets lasts approximately 6 to 8 hours. Patients who are prescribed buprenorphine or buprenorphine/naloxone SL tablets for opioid use disorder or complex opioid dependency usually take their buprenorphine as one dose daily. If a patient who is prescribed buprenorphine or buprenorphine/naloxone SL tablets is in need of acute pain management, consider maintaining the same daily dose of buprenorphine but administering it in divided doses. For example, a patient taking buprenorphine 16mg/naloxone 4mg once daily can be transitioned to buprenorphine 4mg/naloxone 1mg SL Q6H -- this would ensure patient is receiving the same total daily dose of buprenorphine (16mg/day) but at dosing intervals that will better address the acute pain.

Buprenorphine Intravenous Injection
= Further Reading = PCNOW Fast Facts: = References =
 * PCNOW Fast Fact # 457 - Buprenorphine Initiation – Low Dose Methods
 * PCNOW Fast Fact # 441 - Sublingual Buprenorphine Initiation: The Traditional Method
 * PCNOW Fast Fact # 221 - Treatment of Pain in Patients Taking Buprenorphine for Opioid Use Disorders


text:
Palliative Pharmacotherapy/Drug-Specific Information/Opioids/Equianalgesic Tables & Opioid Conversions

Why Equianalgesic Tables are Broken
Most equianalgesic tables assume that one can use the same ratio to convert to and from any two opioids. However, these ratios are not always accurate bidirectionally.

For a good summary of why equianalgesic tables are inaccurate at best, please read "Opioid Equianalgesic Tables are Broken" by Daniel Rosielle on Pallimed.org.

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/


text:
Character Encodings/Code Tables/MS-DOS/Code page 30007

Code page 30007 is a code page intended for Latin and the Romance languages (excluding Eastern Romance languages like Romanian and the languages in Portugal).

Character set
The following table shows code page 30007. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 859}}


text:
Character Encodings/Code Tables/MS-DOS/Code page 30008

Code page 30008 is a code page intended for Abkhaz and Ossetian.

Character set
The following table shows code page 30008. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 808}}


text:
Character Encodings/Code Tables/MS-DOS/Code page 30009

Code page 30009 is a code page intended for the Romani languages and the Turkic languages.

Character set
The following table shows code page 30009. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 857}}


text:
Palliative Pharmacotherapy/Miscellaneous/Abbreviations

A

 * ASHP: American Society of Health-Systems Pharmacists

B

 * Bup/nal: buprenorphine/naloxone combination

M

 * MMEs: morphine milligram equivalents

O

 * OMEs: oral morphine equivalents

P

 * Pgx: pharmacogenomics

S

 * SL: sublingual

T

 * TDF: transdermal fentanyl


text:
Character Encodings/Code Tables/MS-DOS/Code page 30010

Code page 30010 is a code page intended for Gagauz and Moldovan Cyrillic.

Character set
The following table shows code page 30010. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 808}}


text:
Palliative Pharmacotherapy/Introductory Information/Role of the Palliative Care Pharmacist

Training & Education
There are many paths to becoming a pharmacist who works in palliative care. Likewise, there are many settings in which a palliative care pharmacist can be employed: inpatient hospice, outpatient hospice, inpatient palliative care, outpatient palliative care, inpatient pain management, outpatient pain management, long-term care, self-employed as a consultant, etc. Perhaps the most straightforward path to becoming a pharmacist in palliative care is by successfully completing a PGY-2 residency program in Pain Management & Palliative Care.
 * ASHP's 'Required and Elective Educational Outcomes, Goals, Objectives, and Instructional Objectives for Postgraduate Year Two (PGY2) Pharmacy Residencies in Pain Management and Palliative Care'

Although pharmacists can pursue board certification through the Board of Pharmacy Specialties (BPS) for many areas of pharmacy practice, pain management and palliative care is not yet a board specialty. However, a petition was submitted in 2023 to BPS for a Pain Management specialty certification. The petition in can be read in full here.


text:
Character Encodings/Code Tables/MS-DOS/Code page 30011

Code page 30011 is a code page intended for Cyrillic languages in the southern district of Russia.

Character set
The following table shows code page 30011. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 808}}


text:
Character Encodings/Code Tables/MS-DOS/Code page 30012

Code page 30012 is a code page intended for Cyrillic languages in Siberia and the far eastern districts of Russia.

Character set
The following table shows code page 30012. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 808}}


text:
Character Encodings/Code Tables/MS-DOS/Code page 30013

Code page 30013 is a code page intended for Cyrillic Turkic languages in the Volga district of Russia.

Character set
The following table shows code page 30013. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 808}}


text:
Character Encodings/Code Tables/MS-DOS/Code page 30014

Code page 30014 is a code page intended for Cyrillic Uralic languages in the Volga district of Russia.

Character set
The following table shows code page 30014. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 808}}


text:
Character Encodings/Code Tables/MS-DOS/Code page 30015

Code page 30015 is a code page intended for the Khanty language.

Character set
The following table shows code page 30015. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 808}}


text:
User:Tankey6/sandbox

SANDBOX SANDBOX

title: User:Tankey6/sandbox


text:
Character Encodings/Code Tables/MS-DOS/Code page 30016

Code page 30016 is a code page intended for the Mansi language.

Character set
The following table shows code page 30016. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 808}}


text: Category:White radish recipes

title: Category:White radish recipes


text:
Character Encodings/Code Tables/MS-DOS/Code page 30017

Code page 30017 is a code page intended for Cyrillic and Latin languages in the northwestern district of Russia.

Character set
The following table shows code page 30017. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 808}}


text:
Character Encodings/Code Tables/MS-DOS/Code page 30018

Code page 30018 is a code page intended for Russian, Bulgarian, and Latin Tatar.

Character set
The following table shows code page 30018. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 808}}


text:
Palliative Pharmacotherapy/Drug-Specific Information/Opioids/Information About Specific Drugs/Non-Traditional Opioids

= "Non-Traditional" Opioids =

Definition
What exactly constitutes a non-traditional opioid? Non-traditional is a term used loosely to mean opioids that are a bit quirky, the opioids that have interesting additional mechanisms of action: buprenorphine, methadone, tapentadol, and tramadol. These opioids are often underutilized or utilized inappropriately by prescribers less experienced in their intricacies. In other words, most prescribers outside of pain management, palliative care, and hospice will not have dealt routinely with these medications and are generally unfamiliar with them.


text:
Character Encodings/Code Tables/MS-DOS/Code page 30019

Code page 30019 is a code page intended for Russian, Bulgarian, and Cyrillic and Latin Chechen. For a Chechen code page using the newer Latin alphabet, C̈c̈ and S̈s̈ (C and S with diaeresis) would replace Çç and Şş. The digraph C̈hc̈h would replace Ç̇ç̇.

Character set
The following table shows code page 30019. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 808}}


text:
Palliative/Pharmacotherapy/Introductory Information/Useful Resources for the Palliative Care Pharmacist/Must-Reads

Books

 * McPherson ML. Demystifying Opioid Conversion Calculations: A Guide for Effective Dosing. 2nd ed. American Society of Health-System Pharmacists, Inc.; 2019.

Online Education / Websites

 * Fast Facts by Palliative Care Network of Wisconsin (PCNOW)


text:
User:Immanuelle/sandbox/Kii Faith

The Kii clan stands as a highly esteemed family among the Kuni no Miyatsuko, second only to the Izumo clan in prestige. As noted in the Encyclopedia of Shinto, the Kii clan's significance is unparalleled except by the Izumo clan.

The Kii clan descend from Amanomichine, a deity of unclear genealogy mentioned in the Kujiki.

According to the Kujiki he was one of the 32 deities to accompany Nigihayahi during the Tenson korin.

The Kii clan is responsible for two conjoined shrines Hinokuma-jingu and Kunikakasu-jingu

This complex is a Moto-Ise shrine and formerly a Beppyo shrine before leaving the jinja honcho

These two shrines each enshrine a mirror made by Ishikoridome before making Yata no Kagami. Higata no Kagami and Hiboko no Kagami respectively.

Ukai family and Kamayama shrine
The Ukai Family, a cadet branch of the Kii no Kuni no Miyatsuko run Kamayama Shrine. It is a shrine dedicated to Itsuse no Mikoto, who is buried on the premises.

title: User:Immanuelle/sandbox/Kii Faith


text:
User talk:2600:6C67:2800:567:454B:3E9C:14FD:1B5A

May 2024
MathXplore (discuss • contribs) 06:18, 31 May 2024 (UTC)


text:
MediaWiki talk:Revision-info-current

Lint.
The source should include a closing tag for the emboldening. ShakespeareFan00 (discuss • contribs) 07:21, 31 May 2024 (UTC)
 * ✅ --SHB2000 (discuss • contribs) 10:58, 31 May 2024 (UTC)

title: MediaWiki talk:Revision-info-current


text:
Selfish

Selfish is a series of card games published by the company Ridley's Games. The series began with Space Edition in 2018, and currently consists of six editions. These editions are themed around a certain concept or intellectual property, but the overall goal is the same - the players must aim to complete a goal whilst preventing the others from doing the same, and aiming to keep their supply of a certain resource from running out to avoid elimination.

This wikibook will detail how to play the Selfish games.

 * Space Edition
 * Zombie Edition
 * Star Wars Edition
 * Disney Villains Edition
 * Marvel Edition
 * Shipwrecked Edition

title: Selfish


text:
Selfish/Shipwrecked Edition

Selfish: Shipwrecked Edition, released in 2023, is, as of the time of this writing, the most recent game in the Selfish lineup.

This version casts the players as castaways on the Isle of No Return, where all doesn't seem above board. Players will need to escape the island and swim six spaces to the safety of the rescue raft - but with rations running low and the sharks hungry, that's easier said than done. As the players swim to the raft they must navigate and outwit treacherous shark-infested waters, violent hurricanes, colossal sea monsters - and worst of all, each other - to try and get to the raft first.

The goal of the game is to be either the first player to reach the raft, or the last player left swimming when all others have perished.

Game Equipment
The game comes with the following equipment:

 * Five Castaway cards. These represent the playable characters - all of them play identically.
 * Two waypoint strips - these are long pieces of paper with ocean illustrations and a beach at one end. They provide a guide to movement during gameplay.
 * 42 Ocean cards. These are played onto the field as players move and provide effects that can help or harm the players.
 * The Ocean deck contains two Shark cards, which move during gameplay and can devour rations and players.
 * 78 Game cards. These provide players with actions to perform on their turn.
 * Included in the Game cards are 48 Ration cards - 38 single, ten double. These are Shipwrecked Edition's critical resource - if a player runs out of rations and cannot play any when required, that player dies and is out of the game.
 * One Raft card. This card is the goal.

Setup
To prepare the game:

 * Each player selects a Castaway card. The selected Castaway cards are lined up in a horizontal line.
 * The two waypoint strips are placed on either side of the Castaway cards, beach end down.
 * The Raft card is placed in the centre of the playing field, just above the waypoint strips.
 * From the Game deck five Ration cards - four single, one double - are dealt to each player.
 * Four extra cards are dealt to each player.
 * The remaining Game cards are shuffled and laid face down next to the playing field as a draw pile, leaving room for a discard pile.
 * The two Shark cards are separated from the Ocean deck and placed face up near the Game deck.
 * The rest of the Ocean cards are shuffled and laid face down as another draw pile, again leaving room for a discard pile.
 * One player is selected to take the first turn, then play proceeds clockwise.

Basic Gameplay
Each player's turn is divided into three steps, as follows:

Step One: Draw a Game Card
The player draws a Game card from the draw pile and adds it to their hand. If the Game draw pile runs out, reshuffle the discard pile into a new draw pile.

Step Two: Play an Action Card
In this step the player may play Action cards from their hand as they like. Action cards have dark strips at the top and bottom, and have instructions for effects that will help that player. To play an Action card, the player follows the instructions written on the bottom of the card, then places the card into the Game card discard pile. A player may play as many Action cards from their hand as they like during their turn.

Step Three: Float or Swim
In this step the player must decide whether they want to float and stay where they are, or swim one space towards the raft.

If the player decides to float, they must discard one Ration card and leave their Castaway card where it is.

If they decide to swim, the player must discard two Ration cards and move their Castaway card one space forward. Next the player must draw an Ocean card from the Ocean draw pile and place it face up in the space their Castaway card just vacated. They then follow the instructions on the Ocean card, which can have either positive or negative effects. If the Ocean card features a shark icon, the shark moves (explained in the next section).

If a player is moved backwards into a space occupied by an Ocean card, the Ocean card is discarded. A new Ocean card will replace it when the player again moves forward from that space.

A player can also be moved by an Action card, following the same rules.

If a player is in the unfortunate situation where they have to play a Ration card, but do not have any on hand, that player dies and is out of the game. They must discard all of their Game cards, and then flip over their Castaway card to reveal their waterlogged corpse on the back. From then on, that player's turn will be skipped.

Sharks
Let's face it - this couldn't be a castaway-themed game without hungry sharks prowling the waters.

Around half of the cards in the Ocean deck have a shark icon in the top-right corner, which depicts a white shark fin on a red circle. When an Ocean card with a shark icon is drawn for the first time in the game, one of the two Shark cards will be placed directly behind the player who drew said card. The shark does not move - this turn.

The second shark can only be added to the game if the "Feeding Frenzy" Ocean card is drawn whilst a shark is already in play.

Shark Movement
If a shark icon Ocean card is drawn whilst a shark is already in play, the shark moves, according to the following instructions:

 * Every player selects one of the Game cards in their hand.
 * These Game cards are then flipped over, one at a time. Each of the Game cards has a compass pointing in one of four directions - north, east, south or west.
 * As each card is revealed, the shark moves one space in that direction, even if the space does not have an Ocean card. If the shark cannot move any further in a specific direction, that movement is disregarded.
 * Once the movement is complete, the Game cards used are discarded.

Caught by a Shark
If at any point during its movement, the shark lands on a Castaway card, that player must immediately discard one Ration card to avoid being eaten by the shark. If either shark eats some rations, their movement ends even if there are cards left to move by.

If a player moves onto a shark, whether by discarding rations or by another player, they must also discard one Ration or get eaten. The shark will remain in that space until its next move.

If a player does not have any Rations on hand to feed the shark, the shark devours them and they are out of the game.

Winning the Game
The winner of the game is either the first player to swim six spaces and reach the Raft card, or the last player left swimming after everyone else dies.

Ocean Cards
Excluding the Shark cards there are forty Ocean cards, with the following effects:

Action Cards
There are 30 Action cards in the Game deck, with the following effects:

title: Selfish/Shipwrecked Edition


text:
Chess Opening Theory/1. d4/1...g5/2. Bxg5/2...f6

2. f6?
f6 seems like a relatively decent, if strange move by Black at first, kicking out the bishop and preparing for an advance to e5. However, this move weakens the king, as well as blocks development of the knight and the queen to f6. This can be abused by White with the move e4!, which makes the bishop poisoned, takes control of the center, and threatens to attack with the queen.

White always goes Qh5 after a few moves to either checkmate the king or force it to move away. This is not a good situation for Black to be in at all, with little development chances, being attacked, and a weak kingside.


text:
Palliative Pharmacotherapy/Condition-Specific Information/Pulmonary & HEENT (Head, Eyes, Ears, Nose, Throat)/Cough

Opioids

 * Dextromethorphan (DXM)

Non-Opioids

 * Benzonatate
 * Gabapentin
 * Guaifenesin


text:
Palliative Pharmacotherapy/Condition-Specific Information/Hematologic & Oncologic/Cancer-Related Bone Pain

Calcitonin
According to a 2006 (updated in 2015) Cochrane Review, calcitonin does not significantly improve cancer-related bone pain but does increase the risk of side-effects.


text: Category:Book:Selfish

title: Category:Book:Selfish


text:
Ada Programming/Attributes/'Preelaborable Initialization

Description
Returns whether the type of S has preelaborable initialization.


text:
Ada Programming/Attributes/'Index

Description
Within a precondition or postcondition expression for entry family E, denotes the value of the entry index for the call of E.

title: Ada Programming/Attributes/'Index


text:
Ada Programming/Attrobutes/'Enum Rep

Description
Return the number representing a given enumeration literal.

title: Ada Programming/Attrobutes/'Enum Rep


text:
Ada Programming/Pragmas/Admission Policy

Description
An admission policy governs the order in which competing tasks are evaluated for acquiring the execution resource associated with a protected object.


text:
October 7th Massacre/Alumim

Kibbutz Alumim is famous for its white houses, rows of handsome winged trees, and well-kept wide green lawns. The Kibbutz however looked very different after the events of October 7th. Abandoned vehicles were scattered, some of them were burned, and others pierced by bullets. On the night of Simchat Torah the Kibbutz members attended synagogue and did not suspect what was about to happen in less than 12 hours.

A terrorist who participated in the attack on Alumim and was arrested by arrested by the security forces told that the Hamas leaders commanded to commit atrocities including murder and rape. He admitted the plan was to go from house to house, from room to room, throw grenades, and kill everyone including women and children. The Hamas also approved abusing and dismembering the dead bodies.

On October 7th at 6:30 in the morning The holiday peace was disturbed by alarms and intense explosions from the Iron Dome batteries in the area. The residents got out from their beds and went to their shelters. Being accustomed to such events, they were not excited, however this time it was not as usual - the alarms went on and on.

When Rafi Babian, a resident of Alumim as well as security officer of the Sdot Negev Regional Council, heard the alarms and the Iron Done batteries nonstop, he understood that something out of the ordinary is happening. So he made sure his family was in the shelters, and organized to go to the council's headquarters to activate the emergency center. He approached the Saad junction, and saw there a bullet-ridden car. The driver waved with his injured hand and yelled that there are terrorists in the junction. As he got closer, he saw a van with a machine gun shooting everyone in the area. The junction was full of people running away from the music festival in Re’im forest in their way north. They stopped on the sideways due to alarms, and Rafi started sending them east since it was impossible to pass the junction.

At 6:45, the army ordered to raise the standby squad. At 7:00, ten terrorists arrived at the main gate on motorcycles. They rode to the back gate, and broke in. Once in, the terrorists started shooting indiscriminately at vehicles that passed. They hit about 20 cars. Two of them stormed the cars and shot the passengers. One of the terrorists got hit, either by from one of his friends or by a soldier. This group of terrorists retreated.

At 8:00, terrorists were detected at the residence of the foreign workers. The standby squad started shooting at them, however the terrorists entered the residence and started murdering the Nepalese and Thai workers. 16 of them were killed and 8 were taken hostages to Gaza. Eyal Rein, the security coordinator of the kibbutz, testified: “Unfortunately, we were unable to save them. They are our employees, we know each and every one by name.”

At 8:30, the terrorists set on fire the nearby milking parlor, and murdered all of the dairy workers. The haystacks were also set on fire. 700 cows were left without milking or food. Some of them died when the roof collapsed. Cows that are not milked develop inflammations and infections. At 8:45, the terrorists destroyed a shed with equipment worth hundreds thousands of shekels.

A report was received at 9:00 about terrorists in Gan Hadar at the western part of the Kibbutz. The standby squad hurried to the area. Zvika, who directed the operation from the command room in the heart of the kibbutz, told the following about the battle:

"There began the heroic battle of the squad against dozens of terrorists who tried to break out from there towards the kibbutz houses. We managed to kill two terrorists, including the commander of the force, and prevent the terrorists from entering the houses. If they crossed that line, God forbid, there would be a disaster like in the other kibbutzim."

Eyal testified about the battle:

"The terrorists broke through the fence and entered the kibbutz. Here we were already in front of them. This battle saved the kibbutz. We spotted a terrorist - we shot, we spotted another one - we shot. They shot at us. We managed to take down the first, followed by the second. The third tried to retreat towards the plantation. We took some friends up to the top floor of the prep school, and from there we were able to snipe at them. In this battle we killed three terrorists. In total we killed 15-20 terrorists and more. Some of them were discovered only the next day in all kinds of places."

Zvika added:

"In this battle, three members of the squad were injured. One of them received a bullet in the chest and turned back to receive treatment at the clinic. The other was slightly injured. A third member, Eran, said 'I was hurt but I keep fighting'. He continued for another two hours until we evacuated him."

Michaela works as a midwife in Soroka Hospital in Be’er Sheva, however on this day, she worked as a medic on a battlefield. She testified about the events:

"I heard a shot but ran to get a first aid kit. I was operating on automatic and I didn't think about the fact that I was putting myself at risk. If I knew what was going on under my house, it is not clear if I would function. They brought the first wounded man and I see that it is my neighbor. I started to treat him and saw an injury to his hands, a bullet or shrapnel. After half an hour they brought another wounded man, much more seriously, with three gunshot wounds in the back. I called the doctor to get instructions. My husband and my father-in-law, an IDF invalid from the six days, who did not agree to stay in the shelter, helped me. He helped me, washed the wounded and helped put them in the evacuation vehicle."

Preparations were made for evacuating the wounded, and one of the members took his personal car and drove with a medic to Netivot. On the way out, they got shot by terrorists and the medic was slightly injured. At 11:30, another injured person came to Michaela’s house. This was Eran, who as mentioned above kept on fighting even after his injury. Michaela told about him:

"He continued to fight for another four hours with three bullets in his thigh. At first he didn't feel hurt because of the adrenaline in his blood. I forced him to evacuate. My husband gave me his personal weapon and said 'let my father watch over you'. He loaded Eran onto the car and started driving. When he reached Netivot, the brakes and the engine began to emit smoke, and they were extinguished with a fire extinguisher. After Eran was evacuated to Soroka, my husband had to wait three hours until they let him come back."

After this battle, the squad started searching for any remaining terrorists.

At 12:00, another terrorist group was identified on cameras, this time in the avocado groves in the west of the Kibbutz. The squad arrived to the area and they were assisted by soldiers in an armored vehicle who arrived.

At 12:15, one of the residents reported the injury of her husband. The couple was in the shelter when terrorists started shooting at their doors. Soldiers rushed and eliminated these terrorists. Another terrorist shot at another house and the resident was injured by the shrapnel.

Two terrorists who didn't manage to cross the fence returned to the plantations. In the scans anothe terrorist was found lying and waiting. He raised his hands and was taken by the soldiers.

At 12:30, dozens of other terrorists arrived at the Kibbutz. This time to the packing house at the south-east of the Kibbutz. A helicopter eliminated most of them.

title: October 7th Massacre/Alumim


text:
Character Encodings/Code Tables/MS-DOS/Code page 30020

Code page 30020 is a code page intended for Frisian, Low Saxon, and other West Germanic languages in Europe.

Character set
The following table shows code page 30020. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 859}}


text:
Character Encodings/Code Tables/MS-DOS/Code page 30021

Code page 30021 is a code page intended for Oceanic languages. The modifier letter turned comma is unified with the apostrophe in this code page, because they look similar in FreeDOS.

Note that the L and N with cedilla have regular cedillas, unlike in Latvian and Livonian.

Character set
The following table shows code page 30021. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 859}}


text:
Cookbook talk:Yuvarlak (Greek Meatballs)

Avgolemono soup
Hi, Can a recipe for avgolemono soup also be contributed? Thanks, ... PeterEasthope (discuss • contribs) 00:36, 1 June 2024 (UTC)


text:
Character Encodings/Code Tables/MS-DOS/Code page 30022

Code page 30022 is a code page intended for Native American languages in Canada.

Character set
The following table shows code page 30022. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 859}}


text:
Cookbook:Beurre Monté

Beurre monté is a French sauce with many applications; it can be used plain as a dip, cooked in, or adjusted with savory or sweet ingredients. The sauce is simply an emulsion of butter into water, which gives butter a saucier consistency. It can act as a base sauce, meaning ingredients can be added to enhance its flavor, or it can be served plain. It acts as a sister sauce of beurre blanc, which emulsifies the butter in reduced white wine and vinegar.

Ingredients

 * 3 parts by weight of water
 * 8 parts by weight of butter, cold
 * Seasoning, as desired

Procedure

 * 1) Bring the water to a low boil in an appropriately sized cooking vessel, such as a saucepan.
 * 2) Add butter, gradually whisking until smoothly incorporated. Make sure the butter is completely emulsified in before adding the next chunk.
 * 3) Season to taste as desired.
 * 4) Keep warm until use. Don't overheat, as this will break the emulsion.

title: Cookbook:Beurre Monté


text:
Selfish/Zombie Edition

Selfish: Zombie Edition, released in 2019, is the second Selfish game.

The players are cast as the last survivors of a devastating zombie apocalypse. Their supplies are running low, and the zombies are getting close. So now it's time for the players to make their last stand. Or more accurately, they'll need to race to the safety of the escape chopper, outwitting hordes of the undead, roving bandits - and worst of all, each other - all whilst making sure their supplies can last them on the journey.

Unlike most other versions of Selfish, in Zombie Edition a player is not out of the game when they die, but can keep playing as a zombie under a new set of rules.

Game Equipment

 * Five Survivor cards. These represent the playable characters - all of them play identically. These cards are double-sided with an "alive" side on the front and a "zombie" side on the back.
 * One Survival Guide - this is a long piece of paper with illustrations of the playable characters, a zombie and the helicopter. It provides a guide to movement during gameplay.
 * 41 Wasteland cards. These are played onto the field as players move and provide effects that can help or harm the players.
 * 81 Game cards. These provide players with actions to perform on their turn.
 * Included in the Game cards are 48 Supplies cards - 38 single, ten double. These are Zombie Edition's critical resource - if a player runs out of supplies at any time, that player dies and turns into a zombie.
 * One die. It has the numbers zero through three marked on each of its six faces.

Setup
To prepare the game:

 * Each player selects a Survivor card. The selected Survivor cards are lined up in a horizontal line. Any remaining Survivor cards are returned to the box.
 * The Survival Guide is placed on either side of the Survivor cards, chopper end up.
 * The Chopper card is placed in the centre of the playing field, just above the line marked on the Survival Guide.
 * From the Game deck five Supplies cards - four single, one double - are dealt to each player.
 * Four extra cards are dealt to each player. Game cards must be kept secret from other players.
 * The remaining Game cards are shuffled and laid face down next to the playing field as a draw pile, leaving room for a discard pile.
 * The Wasteland cards are shuffled and laid face down as another draw pile, again leaving room for a discard pile.
 * One player is selected to take the first turn, then play proceeds clockwise.

Basic Gameplay
Each player's turn is divided into three steps, as follows:

Step One: Draw a Game Card
The player draws a Game card from the draw pile and adds it to their hand. If the Game draw pile runs out, reshuffle the discard pile into a new draw pile.

Step Two: Play an Action Card
In this step, the player may play Action cards from their hand as they like. Action cards have dark strips at the top and bottom, and have instructions for effects that will help that player. To play an Action card, the player follows the instructions written on the bottom of the card, then places the card into the Game card discard pile. A player may play as many Action cards from their hand as they like during their turn.

Step Three: Rest or Travel
In this step, the player must decide whether they want to rest and stay where they are, or travel one space forward through the wasteland.

If the player decides to rest, they must discard one Supplies card and leave their Survivor card where it is. If this is the player's last Supplies card, they die and turn into a zombie (more information on this later).

If they decide to travel, the player must discard two Supplies cards and move their Survivor card one space forward. Next the player must draw a Wasteland card from the Wasteland draw pile and place it face up in the space their Survivor card just vacated. They then follow the instructions on the Wasteland card, which can have either positive or negative effects. If the player discards their last Supplies cards to travel, and the Wasteland card they reveal does not grant them any supplies, they die.

The effects of Wasteland cards can only be avoided if a player moves by playing the "Abandoned Vehicle" Action card.

If a player is moved backwards into a space occupied by a Wasteland card, the Wasteland card is discarded. A new Wasteland card will replace it when the player again moves forward from that space.

A player can also be moved by an Action card, following the same rules.

Once the player has rested or completed the action for the Wasteland card, their turn ends and play proceeds clockwise.

Playing as a Zombie
Just because you may be dead does not mean you are out of the game. Because we are dealing with zombies here, once you die you may rise from the grave as a zombie to take your revenge!

A player will die and turn into a zombie if one of two things happens: the player runs out of Supplies at any time, or they reveal a Wasteland card that reads "You Have Been Bitten". Should a player die, they immediately discard all of their Game cards (since zombies don't need supplies) and flip their Survivor card over to reveal their rotting corpse. If the player dies on their turn, said turn immediately ends.

From now on, the zombified player's goal will be to eat the other players and turn them into zombies, too.

Taking a Turn as a Zombie
A player begins a turn as a zombie by rolling the die. The number that comes up denotes the number of "action points" the player has available for that turn. If the player rolls a zero, their turn immediately ends - zombies can be slow.

A zombified player may use their action points to perform any combination of one of two actions:

 * The player may move to another level of the playing field. Each level moved costs one action point, and the player may move forward or backward. If the player moves backward, they place their Survivor card on top of the Wasteland card behind them without discarding it. If they move forward into an unoccupied space the zombified player places a Wasteland card facedown in the space they vacated. Wasteland cards do not affect zombies (because they cannot read).
 * The player may attack a living player on the same level as them by discarding one card from their hand. The player may attack one target multiple times or multiple targets once. Each attack costs one action point.

Once a zombified player's action points run out, their turn ends and play proceeds clockwise.

Winning the Game
The winner of the game is the first player to reach the chopper with at least one Supplies card on hand.

If everyone is turned into a zombie, the zombies win.

Wasteland Cards
There are 41 Wasteland cards in the deck, with the following effects:

Action Cards
There are 30 Action cards in the Game deck, with the following effects:

title: Selfish/Zombie Edition


text:
Wikibooks:Reading room/Proposals/2024/February

Wikibooks the project with the least number of interwikis
It seems that Wikibooks in different languages are quite separate. As I said previously there isn't a clear interwiki policy, and for this reason each language version is like an independent project. In my opinion, Wikibooks needs a guide more explanatory than that of Wikipedia. --Doostdar (discuss • contribs) 20:57, 9 July 2023 (UTC)

 * I imagine that Wikinews has far fewer, as very little content is going to have a one-to-one correspondence. In principle, there is no reason why we couldn't have (e.g.) a guide to Common Lisp in Xulu and a textbook of advanced statistical methods in Quechua and have all of these various books link to one another with structured data, but in practice, Wikibooks is a very small project and individual books on individual subdomains tend to be single-person passion projects, so there just won't be many interwiki links in the first place. —Justin ( koavf ) ❤T☮C☺M☯ 07:04, 10 July 2023 (UTC)
 * Some Wikibooks like German, Italian, French and Japanese are big enough and we need a guide for how to link pages between these projects. I haven't yet added interwikis for categories in Persian Wikibooks. Today I'll start to add Persian Wikibooks categories to Wikidata. --Doostdar (discuss • contribs) 07:29, 12 July 2023 (UTC)
 * Thank you to bring this subject up. [//en.wikibooks.org/wiki/Special:Search?fulltext=Search+current+discussions+and+archives&fulltext=Search&prefix=Wikibooks%3AReading+room&search=wikidata+links&ns0=1&ns4=1&ns102=1&ns110=1&ns112=1 Since 2015 a part of the community was reluctant to use Wikidata], but because of this decision, I regularly see newcomers being revoked by replacing the "old interwiki system" from most of the other wikis point of view, by Wikidata links. In addition, these good old interwiki links are never up-to-date comparatively to the Wikidata system. With these experiences, I now consider that maintaining the old system is a waste of time and a source of frustration, and propose to vote to import and adopt w:Help:Interlanguage links here too. And that won't impact the individual writers badly, on the contrary because for example they wouldn't be notified anymore in their watchlists for someone adding an interwiki link into their books. These links do not belong to the books contents so let's host them elsewhere and avoid a bad surprise for Wikipedia contributors. JackPotte (discuss • contribs) 16:46, 15 July 2023 (UTC)
 * Interwiki policy can help us find hot subjects in each Wikibooks project. For example physics and art are hot subjects in Dutch Wikibooks. --Doostdar (discuss • contribs) 07:12, 18 July 2023 (UTC)
 * To clarify: Would this make it so things like interlanguage links in the sidebar are automatically updated (based on wikidata) without having to edit the articles themselves to create the links? This seems like it would be very useful. @JackPotte in general, what were the objections about? —Kittycataclysm (discuss • contribs) 22:38, 18 July 2023 (UTC)
 * As far as I understand, the reluctance was not about using Wikidata but removing the local links, which are in the markup format. But I can't see the problem myself because the links from the Wikidata database are displayed with the same HTML markups. JackPotte (discuss • contribs) 06:08, 19 July 2023 (UTC)
 * Just read through the discussion you linked! Like you said, it seems like the main concern is removing all the local links indiscriminately—this issue can be avoided by leaving any local links that aren't broken. To clarify again: @JackPotte is your proposal simply that we adopt a new policy/guide (i.e. the policy described at w:Help:Interlanguage links)? Since the wikidata-based interlanguage links are already implemented here? —Kittycataclysm (discuss • contribs) 12:25, 19 July 2023 (UTC)
 * Exactly, and if the not broken local links are redundant of Wikidata, we should remove them to avoid watching them in real time by bot. JackPotte (discuss • contribs) 13:33, 19 July 2023 (UTC)
 * Got it, thanks! I would be in support of drafting a Wikibooks policy like w:Help:Interlanguage links to provide clear guidelines on how to handle these links, and then reviewing and voting on it. —Kittycataclysm (discuss • contribs) 13:55, 19 July 2023 (UTC)
 * I emphasize that Wikibooks needs a guide more explanatory than that of Wikipedia. Currently, Wikipedia is known as a multilingual project but what about Wikibooks? Wikipedia is currently working with language speakers and computing organizations to support as many languages as possible. Is Wikibooks doing the same or not? Doostdar (discuss • contribs) 09:13, 10 November 2023 (UTC)
 * It looks like there is already a smaller section on this at Help:Editing. Is there any opposition to me creating a draft guide at either Interlanguage links or Help:Interlanguage links so we can flesh it out? @JackPotte @Doostdar? I can't decide which namespace would be more appropriate. @MarcGarver any insight here? —Kittycataclysm (discuss • contribs) 16:50, 10 November 2023 (UTC)
 * Any name you choose, first define what to do with Wikibooks many subpages? As you know Wikibooks has more subpages than othe projects like Wikipedia and Wikivoyage. How should the writer or editor find interwikis for these subpages? Does Wikidata currently accept subpages or not? Doostdar (discuss • contribs) 20:47, 11 November 2023 (UTC)
 * Different Wikibooks versions should know how to connect with each other. Now at Persian Wikibooks, for example, I've made a book on Latex named "لاتک". Is it correct to link it with the book named Latex in English Wikibooks or not? If yes, what about the sub pages of these two books? Doostdar (discuss • contribs) 20:55, 11 November 2023 (UTC)
 * In contrast to Wikipedia, Wikibooks consists of many subpages. These subpages usually lack interwikis in other languages. Is it needed to choose interwikis for subpages or not? This is one the questions never answered. --Doostdar (discuss • contribs) 20:04, 22 January 2024 (UTC)
 * That's a great question. My instinct is that it might make sense to link the chapters to the other language versions? —Kittycataclysm (discuss • contribs) 01:23, 26 January 2024 (UTC)
 * This, of course, assume the different language versions are analogous to each other. —Kittycataclysm (discuss • contribs) 01:24, 26 January 2024 (UTC)
 * No, most of books are not translated versions of another Wikibooks version; in other words, they are not analogous to each other. So we need guidelines in Wikibooks to decide how to use interwikis. Otherwise, Wikibooks is not a multilingual project and it would be better to remove all interwikis ASAP. Doostdar (discuss • contribs) 13:42, 26 January 2024 (UTC)
 * Subpages should all be linked to Wikidata entries. Whether or not there are any strictly one-to-one interwiki links stored at Wikidata is irrelevant. —Justin ( koavf ) ❤T☮C☺M☯ 16:23, 26 January 2024 (UTC)
 * For example LaTeX/Introduction should be linked to ...? to Q1358138? Doostdar (discuss • contribs) 22:07, 27 January 2024 (UTC)
 * No, no. d:Q1358138 is an item about forewords as a concept. We shouldn't link every foreword to that one item. Each item in the form of "Book/Foreword" should have its own item. —Justin ( koavf ) ❤T☮C☺M☯ 22:34, 27 January 2024 (UTC)
 * Now, 23 Wikibooks have an e-book called "LaTeX" but only 4 of them have a subpage called "LaTeX/Introduction" so it would be better to remove all interwikis. Persian Wikibooks has a subpage called "LaTeX/fonts and colors" but English Wikibooks has two different subpages called "LaTeX/fonts" and "LaTeX/colors". Doostdar (discuss • contribs) 09:20, 31 January 2024 (UTC)
 * That's fine. There doesn't need to be a one-to-one correspondence for all pages. That was exactly the point I was just making. —Justin ( koavf ) ❤T☮C☺M☯ 11:15, 31 January 2024 (UTC)
 * Now you're talking! One-to-one correspondence for all pages is impossible. For main pages of the books in more than 50% of cases there's a one-to-one correspondence but for subpages it's less than 5% (Between French and German Wikibooks) in my opinion. Don't you agree that Wikibooks is the project with the least number of interwikis? Doostdar (discuss • contribs) 10:19, 1 February 2024 (UTC)
 * Nah, second to Wikinews or third after Wikiversity. —Justin ( koavf ) ❤T☮C☺M☯ 10:30, 1 February 2024 (UTC)


text:
World Tea Bag Catalogue/Kazi & Kazi

Kazi & Kazi Tea Estate Ltd. is the only internationally certified organic tea grower in Bangladesh. their garden is located in Tetulia, in the northernmost district of Panchagarh, Bangladesh, only 50 km south of Darjeeling.

Kazi & Kazi Tea Estate Ltd. started its journey in 2000. They acquired virgin lands which had never before been used for cultivation. After extensive research and consultation with the Bangladesh Tea Board, the plantation began on August 6, 2000.

KK Tea entered the local market in 2006. It is esteemed to be one of the highest valued teas in the Chittagong tea auction since 2006. Their

garden produces only organic tea, manufacturing bio-fertilizers and bio-pesticides on-site with only natural and organic means.

title: World Tea Bag Catalogue/Kazi & Kazi


text:
Chess Opening Theory/1. d4/1...Nf6/2. c4/2...g6/3. Nc3/3...Bg7/4. e4/4...d6/5. Nf3/5...O-O/6. Be2/6...e5

6. e5
The move e5 from Black attacks the center and gains space. The main line continues by White castling kingside to get the king away from the center, then Black plays Nc6 to gain space and develop a piece, which White immediately kicks with d5, forcing it to e7. From there, the game can branch off in several different ways.

b4 makes a pawn storm on the queenside, with the rooks developing to support in the attack. In some games, Black's kingside knight goes to h5 then back to f6 on its own volition to push the f pawn to f5 to destabilize the center and prepare g4.

Ne1 eventually rotates the knight to the center after Nd3 where it can defend better against Black's counterattack, be protected from g4as well as attack in the future,. Black's kingside knight also moves to allow f5.

Theory Table
'''1. d4 Nf6 2. c4 g6 3. Nc3 Bg7 4. e4 d6 5. Nf3 O-O 6. Be2 e5'''


text:
User talk:103.178.186.177

June 2024
MathXplore (discuss • contribs) 15:55, 1 June 2024 (UTC)

title: User talk:103.178.186.177


text:
Ada Programming/Libraries/System.Atomic Operations.Exchange

This language feature has been introduced in Ada 2022.

System.Atomic Operations.Exchange is a unit of the Predefined Language Environment since Ada 2022.


text:
Ada Programming/Libraries/System.Atomic Operations.Test And Set

This language feature has been introduced in Ada 2022.

System.Atomic Operations.Test_And_Set is a unit of the Predefined Language Environment since Ada 2022.


text:
Ada Programming/Libraries/System.Atomic Operations.Integer Arithmetic

This language feature has been introduced in Ada 2022.

System.Atomic Operations.Integer_Arithmetic is a unit of the Predefined Language Environment since Ada 2022. The operations of this package are defined as follows:


text:
Ada Programming/Libraries/System.Atomic Operations.Modular Arithmetic

This language feature has been introduced in Ada 2022.

System.Atomic Operations.Modular_Arithmetic is a unit of the Predefined Language Environment since Ada 2022. The operations of this package are defined as follows:


text:
Ada Programming/Libraries/Ada.Numerics.Big Numbers.Big Integers

This language feature has been introduced in Ada 2022.

Ada.Numerics.Big Numbers.Big Integers is a unit of the Predefined Language Environment since Ada 2022.


text:
Ada Programming/Libraries/Ada.Numerics.Big Numbers.Big Reals

This language feature has been introduced in Ada 2022.

Ada.Numerics.Big Numbers.Big Reals is a unit of the Predefined Language Environment since Ada 2022.


text:
Ada Programming/Libraries/Ada.Containers.Bounded Indefinite Holders

This language feature has been introduced in Ada 2022.

Ada.Containers.Bounded Indefinite Holders is a unit of the Predefined Language Environment since Ada 2022.


text:
Chess Opening Theory/1. e4/1...e5/2. Nc3/2...Nf6/3. Bc4/3...Nxe4/4. Qh5/4...Nd6/5. Qxe5

5. Qxe5+
This move is an anti-climax, useful if White wanted to scare Black but not actually follow through with the plan. After a queen exchange with 6. Qe7 7. Qxe7+ Bxe7, White can save the bishop with Bb3 or Be2 then develop with Nf3, d4, and castling, having a slight advantage due to Black's knight blocking the d5 pawn and a rather bad queen's bishop, as well as first move advantage. However, Black can move the knight to f5 and allow the d pawn to move to activate the queen's bishop, and c6 to support a future d5 to take space in the center. This is still a rather interesting game, just not crazy.

Theory Table
.

1. e4 e5 2. Nc3 Nf6 3. Bc4 Nxe4 4. Qh5 Nd6 5. Qxe5+


text:
Character Encodings/Code Tables/MS-DOS/Code page 30023

Code page 30023 is a code page intended for languages in Southern Africa.

Character set
The following table shows code page 30023. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 859}}


text:
Character Encodings/Code Tables/MS-DOS/Code page 30024

Code page 30024 is a code page intended for languages in Northern and Eastern Africa.

Character set
The following table shows code page 30024. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 859}}


text:
Character Encodings/Code Tables/MS-DOS/Code page 30025

Code page 30025 is a code page intended for languages in Western Africa.

Character set
The following table shows code page 30025. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 859}}


text:
Salut, Jonathan! (Interocidental)

Salut, Jonathan! is a translation of Mithridates's language course Salute, Jonathan! into Interocidental, a synthesis of Interlingua and Occidental introduced by valodnieks in 2012.

Capitul 1
Un om sta in un citat. Le om scriba un diario. Le om vida un citat.

Esque le om sta in un citat? Oc, il sta in un citat.

Esque le om sta in...un om? No, il no sta in un om. Il sta in un citat.

Esque le om sta in un tren? No, il no sta in un tren. Il sta in un citat. Le om sta in un citat.

Esque le om scriba un diario? Oc, il scriba un diario.

Esque le diario scriba le om? No, le diario no scriba le om. Un diario no scriba. Un om scriba. Le om scriba le diario.

Esque le citat vida le om? No, le citat no vida le om. Un citat no vida. Un om vida. Esque le om vida le citat? Oc, le om vida le citat.

Donde sta le om? Il sta in un citat. Que le om scriba? Il scriba un diario. Que le om vida? Il vida un citat. Il sta in un citat, e il scriba un diario, e il vida un citat.

Esque le om sta in un diario? No, il scriba in un diario. Esque le om vida un om? No, il no vida un om; il vida un citat.

Le om es grand. Le om es bon, e le om es inteligent. Il pensa. Il pensa super le citat. Le pensa: "Que es le citat? Esque le citat es bon? Esque le citat es grand?"

Esque le om scriba un citat? No, il no scriba un citat; un citat es grand. Il scriba un diario; un diario no es grand.

Esque le diario pensa super le om? No, un diario no pensa. Un om pensa. Il pensa super le diario, e pensa super le citat.

E il scriba in le diario. Il scriba super le citat. Il scriba: "Le citat es bon, e le citat es grand."

Il pensa: "Le citat es bon;" il pensa que le citat es bon. Il pensa: "Le citat es grand;" il pensa que le citat es grand. Il pensa super le citat, e il pensa super le diario.

Que es le diario? Le diario es donde le om scriba; il scriba in un diario. In le diario, le om scriba super le citat. In le diario, le om no scriba super le tren; le om sta in le citat, no in le tren. Il no pensa super le tren; il pensa super le citat, le citat München.

Quel es le citat? It es München. Donde es München? It es donde le om sta. Donde es le om? Il es in München.

Oc, München es un grand citat, e un bon citat. Le om pensa que le citat es un bon citat, e il pensa que it es un grand citat. Le om es inteligent. Il dica: "Salut, München!" Il es un bon om!

Le om sta e pensa: "Donde es le tren?" Il vida...il vida le tren! Il pensa: "Le tren!" Ara il no pensa super le diario e no pensa super le citat; il pensa super le tren!

Capitul 2
Ara le om es in le tren. Il no es in München; il es in un tren. Il viagea. Il pensa: "Ara yo viagea de München a Wien. It es un bon viage. Yo ama viages."

Il pensa super München. Il pensa: "Ara yo es in le tren, ma hier yo esava in München. E ara yo scriba un diario in le tren, ma hier yo scribava un diario in München. E ara yo pensa in le tren, ma hier yo pensava in München. Hier yo pensava super München in München, e ara yo pensa super Wien in le tren. Ara yo es in le tren, no in Wien. Ma yo pensa e scriba super Wien."

Esque le om ara pensa in München? No, il ara no pensa in München. Il pensa in le tren. Hier il pensava in München. Il dica: "Salut, tren!"

Le om es in le tren, e il viagea a un citat. Le citat no es München; München es le citat de hier. Le citat es Wien; Wien es le citat de avui.

Le om pensa super München e Wien. Il pensa: "München esava le citat de hier, e München esava bon. Ara it es avui, e yo es in un tren; le tren es bon. Esque Wien va esar bon?"

Le om pensa super München: München esava le citat de hier. Il pensa in le tren: il es in le tren avui. E il pensa super Wien: Wien va esar le citat de deman.

E il pensa: "München esava grand. Le tren es grand. Esque Wien va esar grand?"

E il pensa: "In München yo scribava in un diario. In le tren yo scriba in un diario. Esque in Wien yo va scribar in un diario? Oc, deman in Wien yo va scribar in un diario. Yo ama diarios." Le om pensa molt (il pensa molt = il pensa e pensa e pensa), e il scriba molt. Oc, il es un inteligent om. Inteligent omes scriba molt, e pensa molt. Il es Jonathan; Jonathan es un inteligent om.

Il scriba: "Yo es Jonathan. Yo es in un tren. Hier yo stava in Münich; deman yo va star in Wien."

Il pensa, e scriba: "Le tren...it es bon, ma vel. It no es nov; it es vel. Esque in München le trenes es vel? Oc, le trenes de München es vel. Ma le trenes de München es bon, e yo ama le trenes de München. Hier yo amava le tren in München, e avui yo ama le tren ara, e deman yo va amar le tren in Wien. Yo ama trenes!"

Jonathan scriba: "München es un bon citat e un vel citat, e Wien es un bon citat e un vel citat. München e Wien no es nov, ma es bon. München e Wien es vel, ma bon citates. Le citates no es nov, ma bon. Yo ama citates!"

Jonathan pensa, que le secund di de viage es bon. Il dica: "Avui esava un bon secund di de viage. Yo ama viages!"

Capitul 3
Jonathan sta in Wien: le citat de Wien. Jonathan pensa que Wien es bon, e que Wien es bel. Jonathan no pensa que Wien es led; il pensa que Wien es bel. Il dica: "Wien es un bel citat! Yo va scribar de it!" E il scriba in le diario de Wien. In le diario il scriba: "Mi tresen di es tre bon! In le secund di yo stava in München. München e Wien es dos citates; München no es Wien e Wien no es München. Yo sta in Wien e le citat es tre bel. Yo ama Wien; le citat no es led. Qual bel es Wien! Ma yo hava un problem."

Que? Jonathan hava un problem? Quel problem? Ara il no vida le diario; il vida le citat e pensa. Il pensa molt del problem.

Le problem de Jonathan es que il ama Wien, ma il no hava tempor.

Il pensa: "Hmm. Ara it es set (7) hores. A deci (10) hores le tren departa. Deci (10) hores min set (7) hores es tres (3) hores. Tres hores no es molt tempor por un bel citat! Yo no hava tempor. Havar tempor es bon, ma yo no hava it! Scribar un diario es bon, ma yo no hava tempor por scribar it! Que facar in Wien?"

Il pensa: "Yo no hava molt tempor. Que facar - scribar un diario, o manjar, o vidar le citat?"

Il pensa plus, e dica: "Yo hava un bon ide! Un moment...yo pensa. Mi tren departa a deci (10) hores. Esque es un tren plus tard, a deci-un (11) hores, o deci-dos (12), deci-tres (13), deci-quar (14) o deci-cinque (5) hores?"

Il vida...oc! Es un tren lequel departa a deci-cinque hores. Ara Jonathan es felis.

Jonathan dica: "Deci-cinque (15) min set (7) es ot (8). Ara yo hava ot hores de tempor! Que yo va facar?"

Il dica: "Yo sava! Yo va manjar un bifstec. E yo va bibar un bir. Un moment...no, yo va bibar dos bires, o tres bires. Bon ide!"

Ara Jonathan biba un bir in Wien, e manja un bifstec. Il es felis. Il dica: "Qual yo es felis! Yo ama le citat de Wien. Qual yo ama viages!"

title: Salut, Jonathan! (Interocidental)


text:
Character Encodings/Code Tables/MS-DOS/Code page 30026

Code page 30026 is a code page intended for languages in Central Africa.

Character set
The following table shows code page 30026. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 859}}


text: Template:By whom

title: Template:By whom


text: Transwiki:Nowrap

title: Transwiki:Nowrap


text:
Transwiki:Template link

{{Template:}}

title: Transwiki:Template link


text: Transwiki:Yesno

title: Transwiki:Yesno


text: Transwiki:Category handler

title: Transwiki:Category handler


text: Transwiki:Fix

title: Transwiki:Fix


text: Transwiki:Delink

title: Transwiki:Delink


text: Transwiki:Template other

title: Transwiki:Template other


text: Transwiki:Icon

title: Transwiki:Icon


text: Transwiki:Navbox

title: Transwiki:Navbox


text:
Transwiki:Navbar/styles.css

/* */ .navbar { display: inline; font-size: 88%; font-weight: normal; }

.navbar-collapse { float: left; text-align: left; }

.navbar-boxtext { word-spacing: 0; }

.navbar ul { display: inline-block; white-space: nowrap; line-height: inherit; }

.navbar-brackets::before { margin-right: -0.125em; content: '[ '; }

.navbar-brackets::after { margin-left: -0.125em; content: ' ]'; }

.navbar li { word-spacing: -0.125em; }

.navbar a > span, .navbar a > abbr { text-decoration: inherit; }

.navbar-mini abbr { font-variant: small-caps; border-bottom: none; text-decoration: none; cursor: inherit; }

.navbar-ct-full { font-size: 114%; margin: 0 7em; }

.navbar-ct-mini { font-size: 114%; margin: 0 4em; }

title: Transwiki:Navbar/styles.css


text:
Transwiki:Navbox/styles.css

/* */ .navbox { box-sizing: border-box; border: 1px solid #a2a9b1; width: 100%; clear: both; font-size: 88%; text-align: center; padding: 1px; margin: 1em auto 0; /* Prevent preceding content from clinging to navboxes */ }

.navbox .navbox { margin-top: 0; /* No top margin for nested navboxes */ }

.navbox + .navbox, /* TODO: remove first line after transclusions have updated */ .navbox + .navbox-styles + .navbox { margin-top: -1px; /* Single pixel border between adjacent navboxes */ }

.navbox-inner, .navbox-subgroup { width: 100%; }

.navbox-group, .navbox-title, .navbox-abovebelow { padding: 0.25em 1em; line-height: 1.5em; text-align: center; }

.navbox-group { white-space: nowrap; /* @noflip */ text-align: right; }

.navbox, .navbox-subgroup { background-color: #fdfdfd; }

.navbox-list { line-height: 1.5em; border-color: #fdfdfd; /* Must match background color */ }

.navbox-list-with-group { text-align: left; border-left-width: 2px; border-left-style: solid; }

/* cell spacing for navbox cells */ /* Borders above 2nd, 3rd, etc. rows */ /* TODO: figure out how to replace tr as structure; * with div structure it should be just a matter of first-child */ tr + tr > .navbox-abovebelow, tr + tr > .navbox-group, tr + tr > .navbox-image, tr + tr > .navbox-list { border-top: 2px solid #fdfdfd; /* Must match background color */ }

.navbox-title { background-color: #ccf; /* Level 1 color */ }

.navbox-abovebelow, .navbox-group, .navbox-subgroup .navbox-title { background-color: #ddf; /* Level 2 color */ }

.navbox-subgroup .navbox-group, .navbox-subgroup .navbox-abovebelow { background-color: #e6e6ff; /* Level 3 color */ }

.navbox-even { background-color: #f7f7f7; }

.navbox-odd { background-color: transparent; }

/* TODO: figure out how to remove reliance on td as structure */ .navbox .hlist td dl, .navbox .hlist td ol, .navbox .hlist td ul, .navbox td.hlist dl, .navbox td.hlist ol, .navbox td.hlist ul { padding: 0.125em 0; }

.navbox .navbar { display: block; font-size: 100%; }

.navbox-title .navbar { /* @noflip */ float: left; /* @noflip */ text-align: left; /* @noflip */ margin-right: 0.5em; }

title: Transwiki:Navbox/styles.css


text:
Transwiki:C

Category:

title: Transwiki:C


text: Transwiki:Yesno-no

title: Transwiki:Yesno-no


text: Transwiki:Para

title: Transwiki:Para


text: Transwiki:Documentation

title: Transwiki:Documentation


text: Transwiki:Sandbox other

title: Transwiki:Sandbox other


text: Transwiki:Template link code

title: Transwiki:Template link code


text: Transwiki:Documentation subpage

title: Transwiki:Documentation subpage


text: Transwiki:Icon link

title: Transwiki:Icon link


text: Transwiki:High-use

title: Transwiki:High-use


text:
Transwiki:TemplateData header

TemplateData for

title: Transwiki:TemplateData header


text: Transwiki:Template parameter usage

title: Transwiki:Template parameter usage


text:
Transwiki:Category link with count

Category:

title: Transwiki:Category link with count


text: Transwiki:Inline cleanup tags

title: Transwiki:Inline cleanup tags


text:
Character Encodings/Code Tables/MS-DOS/Code page 30027

Code page 30027 is a code page intended for languages in Benin.

Character set
The following table shows code page 30027. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 859}}


text:
Character Encodings/Code Tables/MS-DOS/Code page 30028

Code page 30028 is a code page intended for languages in Niger.

Character set
The following table shows code page 30028. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 859}}


text:
User:Panic2k4/Sandbox/ShareMemory/Seeking Utopia

Seeking Utopia
Humans, in general terms, can be said to abhor all and any changes that does not create an immediate (or nearly so) benefit (or the expectation of it) that trumps the perceived (and the subconsciously assessed) cost/effort vs benefit of the adoption of those changes.

As we look at our past societies and present society, the now global one, we can clearly see huge problems that are deeply structural. Most of them constant and old, and some are so pronounced that go beyond petty political divergences to be criminalized by most states. It is absurd that we see those same states close their eyes in claimed impotence, where the only calculation is how the state may benefit for it.

Nothing was more obvious during the Cold War years, where stated ideological conflict would justify despicable actions. All in a pattern we now know is permanent. We have seen it in the past with religious wars, and further back in tribal attacks for wives, resources and territorial claims.

Today we are born captives to a global societal system, we had no say in it and very few will be able to impact in it during their lifetime. This is now a place with no escape, its is globalized and will slowly but certainly remove any lingering minority view that serves its purpose to eradicate. We live in a world where the dissatisfied and oppressed, are ever-increasing but simply prevented to become a majority, an organized body that has an audible voice, so they, as always have, expectantly awaits for a large enough social-economical system convolution to enable a revolutionary tabula rasa, a reset, hopefully toward the general betterment of all mankind (but especially theirs or those that pop the bubble as to obtain a convenient direction toward their own goals).

What is good may be bad, in a measure of time and knowing experience or as contradictory conceptualizations across consciences
As good and evil, the difference between the words utopia and dystopia, is only on how you think it. And there are an infinite number of possibilities, so it is minor the chance to get it right in the inevitable revolution that is to come, as it was in the one that created our present situation. Can we even say we are being slowly nudged into a better future for our species? It is undoubtedly easier to create a failure than a success, especially when the aim is not only perfection but a collectively shared one, a perpetually maintainable perfect society.

Thomas More -> coined the word utopia (Latinized Greek yoo-toh-pee-uh) = no place, his book Utopia published in 1516 included a poem that spelled eutopia (Latinized Greek ee-yoo-toh-pee) = good place, the fleeting defining of utopia (fiction and reality), utopia is linked to individual freedom, utopic concepts depend on the political inclination of the proponent but what are the generalities, French revolution? (Main political ideologies aim for it?) Major Religions ? (monastic existence,Quakers)), democracy? (who defines perfection?), equality, no property rights, utopia is about defining what is a right, proper, sustainable and ever lasting social order (control?), what are the costs for individualism and diversity to survive in an utopic society ?, is it possible to collectively share a complex utopic social system without divergences? what trade offs are necessary?, Information revolution and automation, always pleasant there is no place for pessimism in utopic dreams, a collaborative effort, Twin Oaks Community, Virginia, why are social orders and architecture/design so interlinked? (foundation, identity, function, structure, order, society is defined by its environment Buckminster Fuller), +urban planning (Garden Cities of To-morrow, Germania (city))

List of notable attempts reflecting the rich tapestry of thought for social utopia, sorted by increasing date of inception / publication, along with brief introductions and URLs for further reading:

Edenic Myth (Prehistoric Era) - The story of Eden from the Book of Genesis in the Old Testament represents a utopian garden where humans lived in harmony with nature and each other before the fall of man. Bible Gateway

Heaven Concept (Est. 1000 BCE - Present): Represents a celestial realm of perfection and eternal bliss, varying significantly across religions. - Confucianism: Heaven (Tian) is the home of ancestors and embodies the supreme deity or nature, influencing moral conduct 5. - Dōgen's "Shōbōgenzō" (Zen Buddhism): While not a utopian vision per se, Dōgen's writings emphasize mindfulness and direct experience of reality, which can be seen as a form of societal harmony.- - Laozi's "Tao Te Ching" (Taoism): Outlines a philosophy of balance and harmony with nature, which can be interpreted as a form of utopian living in accordance with the Tao. - Abrahamic Religions - Heaven is often depicted as a utopian realm free from suffering, where believers are rewarded for their faith and actions. Catholic Encyclopedia -- Christianity: Heaven is the final destination for the righteous, where God and His angels reside, contrasting with hell for the wicked. Purification through confession leads to eternal salvation. -- Catholicism: Expands on Christian concepts with purgatory, a transitional state for souls undergoing purification before entering heaven. -- The Qur'an (Islam): While not explicitly utopian, Islamic teachings emphasize social justice, equality, and the welfare of all members of society.

The Republic by Plato (circa 380 BCE) - An ancient philosophical text outlining an ideal society based on justice and virtue. Project Gutenberg 6130

Communal Life in Early Christianity (1st Century CE - Present) - Early Christian communities practiced communal living, sharing resources, and caring for each other, embodying a form of utopian social organization. The Book of Acts (New Testament) Describes the early Christian community living in harmony, sharing everything in common, and caring for one another. Bible Gateway - Book of Acts

Utopia by Sir Thomas More (1516) - Describes a fictional island nation where the inhabitants live under a system of laws promoting contentment and prosperity.

Campanella's "City of the Sun" (1602) - An early work of science fiction that describes a theocratic society based on Christian communism.

New Atlantis by Francis Bacon (1627) - Describes a utopian land where science and technology flourish, leading to advancements in knowledge and well-being.

Harmony Society (Founded in Germany in 1785, Moved to the United States in 1803) - A Christian theosophy and pietist group that practiced communal living and shared resources.

Ethiopia's Hadiya Kingdom (1813-1855) - This kingdom, led by King Tekle Haymanot II, practiced a unique form of communism, sharing resources among its members, and is considered an early attempt at a utopian society in Africa.

The Communist Manifesto by Karl Marx and Friedrich Engels (1848) - Proposes the establishment of a classless society where private property is abolished and the means of production are owned communally.

Shaker Communities (Established in the United States in the 18th Century) - Originating from England, the Shakers established communities in America practicing communal living, equality, and pacifism.

Amana Colonies (Established in Iowa in 1855) - A communal society of German Pietists emphasizing simplicity, honesty, and hard work.

Oneida Community (Founded in New York in 1848) - Known for its complex marriage system and communal living, aiming for economic independence and gender equality.

Looking Backward by Edward Bellamy (1888) - A novel depicting a utopian society in the year 2000, where economic inequality has been eliminated through a nationalization of industry. Internet Archive - Looking Backward by Edward Bellamy (1888)

A Modern Utopia by H.G. Wells (1905) - Explores the idea of a global utopia achieved through a world government and the abolition of nationalism. Internet Archive - A Modern Utopia by H.G. Wells (1905)

Brave New World by Aldous Huxley (1932) - Presents a dystopian vision of a futuristic society where people are genetically engineered and controlled through technology and drugs.

The Shape of Things to Come by H.G. Wells (1933) - A science fiction novel predicting a future world united under a single government to solve humanity's problems.

Tanzania's Ujamaa Socialism (1967) - Tanzania implemented Ujamaa, a policy advocating for self-reliance and communal farming, aiming to reduce wealth disparities and promote social welfare.

The Derg's Socialist Experiment in Ethiopia (1974-1991) - Following the Ethiopian Revolution, the Derg regime attempted to implement socialist reforms, including land redistribution and the creation of workers' cooperatives, though it faced significant challenges.

This list includes both historical and contemporary attempts at creating utopian societies, showcasing the enduring human desire to envision and strive towards a better way of living.


text:
Character Encodings/Code Tables/MS-DOS/Code page 30029

Code page 30029 is a code page intended for languages in Mexico.

Character set
The following table shows code page 30029. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 858/859}}


text:
User talk:2600:1003:B05E:6EC6:0:33:95BF:E701

--SHB2000 (discuss • contribs) 00:46, 2 June 2024 (UTC)

 * Two letters, N-O. 2600:1003:B05E:6EC6:0:33:95BF:E701 (discuss) 00:49, 2 June 2024 (UTC)
 * Since you aren't willing to contribute constructively, you've earned yourself a 3-day block. --SHB2000 (discuss • contribs) 00:50, 2 June 2024 (UTC)


text:
Character Encodings/Code Tables/MS-DOS/Code page 30030

Code page 30030 is a code page intended for languages in Mexico.

Character set
The following table shows code page 30030. Each character is shown with its equivalent Unicode code point. Only the second half of the table (128–255) is shown, the first half (0–127) being the same as code page 437.

{{legend|#EFF|Symbols and punctuation}} {{legend|#FFD|Differences from code page 859}}


text:
User:Immanuelle/sandbox/Fall of Susanoo

Here is a minor but potentially quite consequential difference between the Nihon Shoki and the Kojiki

In the Kojiki Susanoo no MIkoto kills Ukemochi here

In the Nihon Shoki on the other hand, it is Tsukuyomi, the moon god, who kills Ukemochi

This may indicate the NIhon Shoki having a more positive account of Susanoo-no-Mikoto.

However after this the Kojiki goes into an extensive mythical cycle about the story of Susanoo no MIkoto,

This goes from Susanoo to Okuninushi no mikoto.

Helen Hardacre (or the forgotten religion guy) argues that this may have been an earlier Izumo exclusive myth that was incorporated into the Kojiki as an attempt to include but subordinate Izumo.

title: User:Immanuelle/sandbox/Fall of Susanoo


text:
User:Immanuelle/sandbox/Inari Faith

Inari faith is one of the most widespread and well-known sects within Shinto, the indigenous spirituality of Japan. The faith centers around the worship of Inari Ōkami, a kami (deity) associated with rice, agriculture, fertility, foxes, industry, and prosperity. With thousands of shrines dedicated to Inari throughout Japan, this faith plays a significant role in the everyday lives of many Japanese people and reflects the deeply intertwined relationship between Shinto and Japanese culture.

The Origins of Inari
The origins of Inari worship are somewhat shrouded in mystery, but it is believed to date back to the early eighth century. Inari is traditionally depicted as a deity of rice, which has been the staple food of Japan for centuries and holds great cultural and economic significance. As Japan's economy evolved, so too did the attributes of Inari, who came to be associated with various aspects of prosperity and success.

The Symbolism of Foxes
One of the most distinctive features of Inari faith is the reverence for foxes, known as kitsune. Foxes are considered the messengers of Inari and are believed to possess magical abilities, including the power to shape-shift. Statues of foxes often flank the entrances to Inari shrines, where they are depicted holding symbolic objects in their mouths or under their paws, such as keys (representing the keys to rice granaries) or scrolls (symbolizing wisdom).

Major Inari Shrines
The primary center of Inari worship is Fushimi Inari Taisha, located in Kyoto. This grand shrine, with its thousands of vermilion torii gates, is a significant pilgrimage site and attracts millions of visitors each year. Other notable Inari shrines include the Takekoma Inari Shrine in Miyagi Prefecture and the Yūtoku Inari Shrine in Saga Prefecture.

Rituals and Festivals
Inari worship involves various rituals and festivals that reflect the agricultural roots of the faith. The most important festival is the Inari Matsuri, held annually at many Inari shrines across Japan. During this festival, offerings of rice, sake, and other foods are made to Inari, and rituals are performed to ensure a bountiful harvest and general prosperity.

One unique ritual associated with Inari shrines is the custom of donating torii gates. Worshippers, often businessmen seeking success, donate these gates as a sign of gratitude or in hopes of receiving blessings. The result is the iconic pathways of torii gates found at places like Fushimi Inari Taisha, creating a striking and memorable visual experience.

Modern Significance
Today, Inari faith remains relevant not only in agriculture but also in various industries, including commerce and manufacturing. Inari shrines can be found in urban areas, and businessmen and entrepreneurs frequently visit these shrines to pray for success and protection in their ventures. This adaptability and broad appeal have ensured the continuity and vitality of Inari worship in contemporary Japan.

title: User:Immanuelle/sandbox/Inari Faith


text:
User:Immanuelle/sandbox/Kamo Faith

The Kamo shrines defent the Northeastern side of Kyoto. There are two main shrines Kamigamo Shrine and Shimogamo Shrine. .

They do not have a very well known historical or mythical origin

Kamigamo shrine worrhips Ajisukitakahikone under another name

Shimogamo shrine worships Tamakushi-hime (玉依姫命) and Kamotaketsunumi no Mikoto (賀茂建角身命)

title: User:Immanuelle/sandbox/Kamo Faith


text:
User:Immanuelle/sandbox/Kumano Faith

Kumano (deity) (熊野権現), also known as Three Mountains of Kumano (熊野三山), is a Japanese deity associated with Kumano Shrines. The kami enshrined in the three Kumano Sanzan Grand Shrines and worshipped in Kumano shrines are the three Kumano mountains: Hongū, Shingū, and Nachi.

There are more than 3,000 Kumano shrines in Japan, and each has received its kami from another Kumano shrine through a process of propagation called bunrei (分霊) or kanjō (勧請).

The point of origin of the Kumano cult is the Kumano Sanzan shrine complex in Wakayama Prefecture, which comprises Kumano Hayatama Taisha (熊野速玉大社) (Shingū, Wakayama), Kumano Hongū Taisha (Tanabe, Wakayama) and Kumano Nachi Taisha (Nachikatsuura, Wakayama Prefecture).

Origins
The three Kumano Sanzan shrines are the Sōhonsha ("head shrines") of all Kumano shrines and lie between 20 and 40 km from each other. They are connected to each other by the pilgrimage route known as Kumano Kodō (熊野古道). The great Kumano Sanzan complex also includes two Buddhist temples, Seiganto-ji and Fudarakusan-ji.

Kumanokusubi, the fifth and youngest child of Amaterasu is sometimes linked to Kumano Gongen The deity's name, Kusubi (Kusuhi), is thought to mean "strange spirit" (mysterious divine spirit) or "strange fire. The current deity of Kumano-taisha is "," but there is a theory that the original deity was Kumanokusubi. There is a theory that the deity of Kumano Nachi Taisha, Kumanokusubi, is Izamiami, but this is also believed to be a reference to Kumanokusubi.

The religious significance of the Kumano region goes back to prehistoric times and therefore predates all modern religions in Japan. The area is still considered a place of physical healing. Each shrine initially had its own separate form of nature worship. In the 10th century, under the influence of Buddhism, the three came to be worshiped together as the three deities of Kumano. Because at the time Japanese kami were believed to be emanations of Buddha (honji suijaku theory), the three came to be associated with Buddhas. Kuniyasutamahime became associated with Sahasrabhūja Avalokiteśvara (Senju Kannon, "Avalokiteśvara#Thousand-armed Avalokiteśvara"), Bhaisajyaguru (Yakushi Nyōrai) and Amitābha (Amida Nyōrai).

Kumano Gongen refers to the deities of the Three Kumano Mountains, especially focusing on the main deities: Ketsumiko (Susanoo), Hayatama (Izanagi), and Musubi (also written as Fusubi or Musubi, or "Yui" for Izanami), collectively known as the Kumano Sanjo Gongen. In addition to these, other deities are also included, referred to as the Kumano Jūniso Gongen. The site became a unique example of shinbutsu-shūgō, the fusion between Buddhism and Japanese ethnic religion.

The Three Kumano Mountains consist of Kumano Hongū Taisha, Kumano Hayatama Taisha, and Kumano Nachi Taisha. Initially, they developed separately; Hongū was established during the reign of Emperor Suinin, Hayatama during Emperor Keikō's reign (according to the Fusang Jijin), and Nachi during Emperor Kōshō's reign, with the foundation involving a practice called naked pilgrimage (also "naked form"), though this is uncertain. In official histories, the names of the deities can be confirmed in documents from 806, with a record from 766 mentioning that four households were dedicated to the Hayatama and Kumano Musubi deities, indicating that these two deities were worshipped together in what is today Shingu, known as Kumano Shinson.

By the mid-9th century, the deity was simply called Kumano Imasu Kami, and the main deity of Hongū, previously unclear, began to be called Ketsumiko or Shōshō Bosatsu, along with New Musubi and Hayatama, establishing the tradition that Ketsumiko was an ancient Kumano deity ("Kumano Gongen Suijaku Engi", included in "Chōkan Kanmon" ).

The Kumano Sanzan site attracted many worshipers and became a popular pilgrimage destination. In the 11th century, pilgrims were mostly members of the emperor of Japan or aristocrats, but four centuries later they were mostly commoners. The visit was referred to as the "Kumano ant pilgrimage" (蟻の熊野参り), because they could be seen winding through the valleys like so many ants.

Moreover, the "Chūyūki" entry for October 26, 1109, not only lists these three deities but also mentions Goshodenji, Ichiman Kenzoku, Jūman Kongō Dōji, Kanjō Jūgoso, Hikō Yasha, and Meiji Kongō Dōji, and the pilgrimage records of Toba-in and Taikenmon'in (included in "Chōshūki") from February 1, Longsheng 3 year, list the twelve Gongen and their original Buddhas, showing that by this time, the Kumano Sanjo Gongen and Jūniso Gongen were established. Nachi, differing in nature from Hongū and Hayatama and known as a sacred place for waterfall asceticism, initially had Izanami as the main deity, but by the early Kamakura period, the "Kumano Gongen Kongō Zōjō Hōden Constructing Merits Diary" included tales related to the worship of the Twelve Gongen, indicating that by this time, the deities of Hongū and Hayatama were also enshrined there. Thus, by the end of the 12th century, the three mountains had unified by worshipping each other's deities.

Kumano Gongen
Each of the Three Mountains is considered to represent a different pure land: Hongū represents the Western Paradise, Shingu represents the eastern pure land of Lapis Lazuli, and Nachi represents the Southern Potalaka. From the Heian period onward, Kumano as a whole came to be regarded as a land of the Pure Land.

There is a 12 deity version, and a three deity version with Amitabha Bhaisajyaguru and Sahasrabhuja The Nachi Falls is said to be the thirteenth member.

At Kumano Hongū Taisha and Kumano Hayatama Taisha, twelve deities are enshrined as follows.

At Kumano Nachi Taisha, "Taki-miya" (deity Ōkuninushi (Takinawa Gongen), original Buddha Thousand-Armed Kannon) is considered the first pavilion, and the order descends one pavilion at a time, enshrining the eight deities of the Middle Four Shrines and the Lower Four Shrines in the sixth pavilion (Hassha-den), thus known as the "Thirteen Shrines Gongen".

title: User:Immanuelle/sandbox/Kumano Faith