OpenLLM-France/wikimedia huggingface dataset:
# Axioms of Betweenness
## Betweenness Axiom 1

If A*B*C, then A,B, and C are three distinct points all lying on the same line, and C*B*A.

### Explanation
## Betweenness Axiom 2

Given any two distinct points B and D, there exist points A,C, and E lying on line BD (needs format with LaTex) such that A*B*D, B*C*D, and B*D*E.

### Explanation

suppose that in a certain metric geometry the following distance relationship hold: AB= 2 AD=BD=CD=3 BC=4 AC=6

## Betweenness Axiom 3

If A, B, and C are three distinct points lying on the same line, then one and only one of the points is between the other two.

### Explanation
## Betweenness Axiom 4

For every line l and for any three points A, B, and C not lying on l:
* (i) If A and B are on the same side of l and if B and C are on the same side of l, then A and C are on the same side of l.
* (ii) If A and B are on opposite sides of l and if B and C are on opposite sides of l, then A and C are on the same side of l.

### Corollary

* (iii) If A and B are on opposite sides of l and if B and C are on the same side of l, then A and C are on opposite sides of l.
# Geometry/Neutral Geometry/Euclid's Fifth Postulate
## Euclidean Parallel Postulate

For every line l and P such that P does not lie on l, there exists a unique line m through P that is parallel to l

### Explanation

[To Come]

## Attempted Proofs

The Euclidean Parallel Postulate can not be proven without taking it as an axiom, which is not done in neutral geometry since it holds in Euclidean but not hyperbolic. Therefore, this is neither true nor false.
* LeGendre Proof to come.
# Geometry/Neutral Geometry/Euclid's First Four Postulates
## Euclid's Postulate I

For every point P and for every point Q not equal to P there exists a unique line that passes through P and Q

### Explanation

Informally, this postulate says that two points determine a unique line.

## Euclid's Postulate II

For every segment AB and for every segment CD there exists a unique point E on line AB (needs LaTex formatting) such that B is between A and E and segment CD is congruent to segment BE

### Explanation

[To Come]

## Euclid's Postulate III

For every point O and every point A not equal to O, there exists a circle with center O and radius OA

### Explanation

[To Come]

## Euclid's Postulate IV

All right angles are congruent to one another

### Explanation

[To Come]
# Geometry/Neutral Geometry/Incidence Geometry
## Incidence Axioms
### Incidence Axiom 1

For every point P and for every point Q not equal to P, there exists a unique line l incident with P and Q.

### Incidence Axiom 2

For every line l, there exists at least two distinct points incident with l

### Incidence Axiom 3

There exists three distinct points with the property that no line is incident with all three of them
# GNU Health/Patient Appointment and Admission Management
## Appointments
### Information stored per appointment

Each appointment can store the following information:
* Appointment ID
* Patient
* Type of Appointment
* Level of Emergency
* Date
* Specialty
* Health Professional
* Health Center

### List of all appointments

From the main menu of Health you have the possibility to get into the Appointments section. Here you see the list of all the appointments stored in the system.
* Free tab: This list reflects all available timeslots where you can create a new appointment.
* Confirmed tab: This list reflects all existing appointments.

#### Appointments Calendar

The subsection Appointments Calendar allows you to display all appointments stored in the system in a calendar view.

#### Appointments Report

The subsection Appointments Report allows you to display all appointments of a certain health professional in a certain time period.

### List of appointments for a specific patient

To access the list of all appointments for a specific patient only you typically start from the patients record. Simply click the Relate button and choose Appointments.

## Hospitalizations

From the main menu you will have access to the Hospitalizations area. From here you will manage any kind of action related to the patient’s admission to or discharge from the hospital.
When you create a new Hospitalization record there are different tabs that will help you gather more information:
* Administrative Data: In this section you can enter all the administrative information related to the patient admission.
* Nutrition: The information in this section helps the hospital center to know more about the patient’s diet, belief etc.
* Medication: All the information entered here is related to medication during the admission (indication, treatment period, dosage etc.).
* Care Plan: Here you will input all the data about nursing plan and discharge plan.
For more information about hospitalizations please refer to the Inpatient Management chapter.
← Patient Evaluations · Laboratory Management →
# GNU Health/Patient Evaluations
## Introduction to Evaluations

By using GNU Health, the physicians have the possibility to open and make an Evaluation from the Patient window. This evaluation can be linked to an existing Appointment or just creating a new one.

## Evaluations History

From the Patients form you can switch to the Evaluations history of a given patient by clicking on the Relate button in the toolbar. The system allows to print the report with all the patient information, which is very important when a doctor needs to see the overall situation of the patient.

## Evaluations Form

The doctor has different tabs that will help him collect information during the evaluation process. The idea is to gather as much information as possible, this will allow the physician to have a better idea about the patient and to give a presumptive diagnosis in order to get to a final one and start the right treatment.

### Main Info Tab

In this section we can link the evaluation to an existing previous appointment or just start a new one. The doctor can input the patient complaints and/or present/existing symptoms or illness.

### Clinical Tab

The doctor will gather all the vital signs (temperature, blood pressure …), anthropometry info and signs and symptoms encountered during the evaluation.

### Mental Status Tab

The physician can make a quick Glasgow Coma Scale when it's necessary.

### Diagnosis Tab

Finally the physician can make a presumptive diagnosis and input more info about it as well as treatment plan.
← Patient Management · Patient Appointment and Admission Management →
# GNU Health/Plugins
## Introduction

The GNU Health Plugins are client-side programs that provide extra functionality. They are installed locally.

## Initialize the plugin directory

The GNU Health plugins are installed in your $HOME directory, under "gnuhealth_plugins".
In order to keep the GNU Health plugins compatible with the latest client, you need to create a link to the GNU Health plugins directory

## The GNU Health Camera

The GNU Health camera plugin allows to visualize, transfer and store media from a webcam device ( camera, microscope, ... ).
There are many contexts where the camera is useful, some of them :
* Person or patient registration
* Domiciliary units surveys
* Histological studies
* EKG strips
* Telemedicine
* Dx Imaging
The information captured by the device will be transferred and stored in the GNU Health server.

### Installing OpenCV

The GNU Health camera uses the excellent Open Computer Vision library ("OpenCV"). You need to install the opencv package for your operating system.
Install the Python bindings for OpenCV of your distribution. In openSUSE, the package is python3-opencv . In Archlinux, python-opencv
How to check the correct installation of OpenCV: import the module CV2 in the python interpreter
If no errors, the installation is successful!

### Installing the GNU Health Camera

Download and uncompress the latest version from GNU into your home directory
Restart the client

### Invoking the GNU Health Camera

From the client, click on the Launch action icon, and select "GNU Health Camera"

### Using the Camera

"a" : attach any media taken from the camera device into the current model.
[SPACE] : store the media as a binary field, for instance, as the person / patient picture. To store the media as a picture, press the SPACE bar. Currently GNU Health has the party model person picture predefined.
"h" : Show the help menu
"q" : Quit the camera
After you transfer the media, you need to refresh the current view [CONTROL + R]

## GNU Health Crypto plugin

GNU Health allows signing and encrypting documents with the GNU Privacy Guard plugin.
The Crypto plugin works along with the GNU Health Crypto Module .
In order to use it, you need the following in your client:
* The GNU Health crypto plugin for the Tryton client, shipped with the main tarball (under the backend/plugins directory). Since 2.8.0, the GNU Health Tryton crypto plugin will be a separate package.
* The GPG package (comes with most modern operating systems).
* The python-gnupg library (https://pypi.python.org/pypi/python-gnupg).

### Installation of the Crypto plugin

We assume you have installed the GNU Health client using the sources.
Place the "crypto" directory containing the plugin under the "gnuhealth_plugins" of your client.
# GNU Health/Operating System-Specific Notes

* This chapter applies to version 3.6 of GNU Health.

# openSUSE
## Download and install the Operating System

* Download the openSUSE Leap Network CD image
* Check the partitioning and FS options (we use ext4 filesystem)
* Select SERVER (text only) installation
* Enable SSHD server
* Create the user "gnuhealth" when prompted at installation time.

## Install the requirements

Initialize the PostgreSQL environment. The next systemctl start command will generate the initial pg cluster.

## Update locally pip3

Continue with the GNU Health Installation

# Debian

* This chapter applies to version 3.6 of GNU Health.

## Download and install the Operating System

* Download the Debian OS image
* Check the partitioning and FS options (we use ext4 filesystem)
* Deselect the "Debian desktop environment" if you just want a server (no graphical interface)
* Enable SSHD server
* Create the user "gnuhealth" when prompted at installation time.

## Install the requirements

Continue with the GNU Health Installation

# FreeBSD

* This chapter applies to version 3.8 of GNU Health.

## At Operating System installation

* Select SSHD
* Create the gnuhealth user at installation time

## Install requirements
### Change /bin/bash to /usr/local/bin/bash

The first line of script that starts gnuhealth (start_gnuhealth.sh) is pointing to /bin/bash. On FreeBSD you have to change that to /usr/local/bin/bash.
Continue with the GNU Health Installation

# CentOS
### Install PostgreSQL 12

Continue with the GNU Health Installation

# Ubuntu

* These instructions apply to Ubuntu 20.04 and Armbian 20.05 version
* Create the gnuhealth user at installation time

## Install requirements

Continue with the GNU Health Installation

# Armbian

* These instructions apply to Armbian 20.05 version
* Create the gnuhealth user at installation time

## Install requirements

Continue with the GNU Health Installation
← Installation
# GNU Health/Packaging Guidelines

In order to make the GNU Health installation and documentation process valid for the vast number of operating systems available, we need to specify some basic guidelines. These guidelines should be taken into account if you want to create a package for your operating system or distribution. Please note that the package is not required to install GNU Health. The GNU Health installer, detects most operating systems and installs the system and requirements as explained in the installation guide.
If want to create and/or maintain a package for your operating system, please follow these (partial) general guidelines. Note that these guidelines will change from time to time in order to adapt to the new releases.
* Operating System user : The operating system user is "gnuhealth"
* Installation directory : Installation directory is the $HOME directory of the operating system
* RC file : GNU Health comes with a set of pre-defined environment variables and aliases. These are stored in the $HOME/.gnuhealthrc file. It's important that this file is always loaded at login time. The documentation and control programs heavily make use these variables and aliases.
* Shell : The default shell, used by the installation script is BASH
* GNU Health installer : This is the main installer, since GNU Health 3.0 the name is gnuhealth-setup, and is included in the main GNU Health tarball. Invoking this script would probably be the easiest way.
* Directory Structure : Please follow the directory structure and links that are set during the standard installation.
* Tryton configuration file : GNU Health comes with a basic Tryton server configuration file, tailored for the general use.
* GNU Health control center : This program is the base for controlling the GNU Health instance (status, backup, updates, language packs ... ). Since GNU Health 3.0 resides in the "util" directory.
In addition to these basic guidelines, there are a list of per-requisites as per Operating System that must be included. Please check the installation section for your particular Operating System.

## Desktop Entry

The GNU Health client contains the ".desktop" file, called gnuhealth-client.desktop. For system-wide installation, it can be installed on "/usr/local/share/applications/gnuhealth-client.desktop" in FreeBSD or under "/usr/share/applications/gnuhealth-client.desktop"
When installing the package locally, the gnuhealth-client desktop file can be installed under $HOME/.local/applications.

### Icon

The icon we recommend using for the application menu is the scalable "gnuhealth.svg" file (under gnuhealth/data/pixmaps/gnuhealth), that can go on the generic /usr/local/share/icons/hicolor/scalable/apps/gnuhealth.svg (FreeBSD) or /usr/share/icons/hicolor/scalable/apps/gnuhealth.svg on many GNU/Linux distros.
← Preface · Resources →
# French/Texts/National anthems/La Brabançonne

* L'Aube Nouvelle
* La Brabançonne
* Le Cantique suisse
* La Marseillaise
* O Canada
Lessons · Vocabulary · Grammar · Appendices · Texts

## About

La Brabançonne is the national anthem of Belgium.

## The Anthem

| French lyrics | |
| O Belgique, ô mère chérie, À toi nos coeurs, à toi nos bras, À toi notre sang, ô Patrie ! Nous le jurons tous, tu vivras ! Tu vivras toujours grande et belle Et ton invincible unité Aura pour devise immortelle : Le Roi, la Loi, la Liberté ! Aura pour devise immortelle : Le Roi, la Loi, la Liberté ! Le Roi, la Loi, la Liberté ! Le Roi, la Loi, la Liberté ! | English Translation Noble Belgium - for ever a dear land - We give you our hearts and our arms. By the pure blood spilt for you, our Fatherland, We swear with one cry - You will live! You will live, always great and beautiful, And your invincible unity Will have as your immortal emblem - For King, Justice and Liberty! Will have as your immortal emblem - For King, Justice and Liberty! For King, Justice and Liberty! For King, Justice and Liberty! |

## Questions

1. What are the last 3 lines in English?
2. What is the blood spilt for Belgium described as in the third line?
L'Aube Nouvelle (Benin) · La Brabançonne (Belgium) · Le Cantique suisse (Switzerland) · La Marseillaise (France) · O Canada (Canada)
French :
Lessons · Vocabulary · Grammar · Appendices · Texts
# French/Project/Authors

Lessons · Vocabulary · Grammar · Appendices · Texts

## Major authors

| Name | Background/Qualifications | Contributions | Signature |
| italienmoose | Someone who wants some more complete wikibooks for languages (and everything else) and would like to lead with example. Starting with French. | All work in progress | Italienmoose (talk) 19:24, 6 June 2010 (UTC) |
| Lord Emsworth | Early major contributor, grammar, various content |
| Traroth | Early major contributor |
| Tommciver | Advanced content |
| hagindaz | Learner | Formatting; incorporating content from Wiktionary and Wikipedia |
| Youssefsan | Vocabulary |
| Merrheim | Native speaker | Recordings, corrections, various content |
| Gringoleblanc_(french) | Native speaker | Recordings, corrections, various content |
| Recent_Runes | Learner | Grammar and core vocabulary, book organisation. | Recent Runes (talk) 20:36, 17 December 2010 (UTC) |
| Qwert1 | Learner with basic French understanding | Filling in missing dialogs, fixing little typos | Qwerty number1 (talk) 20:36, 17 December 2010 (UTC) |

## Sources and references

* English Wikipedia
* French Wikipedia
* English Wiktionary
* French Wiktionary
Authors · Example tasks for contributors · Book overview · Discussion · Templates
French :
Lessons · Vocabulary · Grammar · Appendices · Texts
# French/Project/Example tasks for contributors

Lessons · Vocabulary · Grammar · Appendices · Texts

## Native speakers

* Write dialogues, texts, and culture sections for lessons
* Create speech recordings of vocabulary, dialogues, and texts (for example with https://lingualibre.fr/wiki/Special:RecordWizard which uploads the words pronunciations on Commons:)

## Professional educators

* Create lesson plans
* Rewrite and reorganise existing lessons

## General contributors

* Incorporate definitions, pronunciation, usage, and example sentences from Wiktionary
* Incorporate text excerpts from Wikipedia, Wikinews, and Wikisource
* Incorporate grammar content from Wikipedia and public-domain sources
* Copy-edit, fix formatting, proof-read, improve usability and user experience

## Lessons with sections needing content

Authors · Example tasks for contributors · Book overview · Discussion · Templates
French :
Lessons · Vocabulary · Grammar · Appendices · Texts
# French/Texts

Lessons · Vocabulary · Grammar · Appendices · Texts

## Contents

Simple texts :
News story · Déclaration des Droits · La Cigale et la Fourmi · Le Corbeau et le Renard · Les Deux Mulets
National anthems :
L'Aube Nouvelle (Benin) · La Brabançonne (Belgium) · Le Cantique suisse (Switzerland) · La Marseillaise (France) · O Canada (Canada)
Advanced texts :
Excerpts from Les Misérables · Excerpts from Candide · Excerpts from Le Comte de Monte-Cristo
# French/Texts/National anthems/O Canada

* L'Aube Nouvelle
* La Brabançonne
* Le Cantique suisse
* La Marseillaise
* O Canada
Lessons · Vocabulary · Grammar · Appendices · Texts

## The Anthem

| French lyrics | English translation O Canada! Land of our forefathers your front is wreathed with a glorious garland of flowers. Because your arm can wield the sword, it is ready to carry the cross. your history is an epic Of the most brilliant exploits. your valour steeped in faith Will protect our homes and our rights Will protect our homes and our rights. |
| O Canada! Terre de nos aïeux, Ton front est ceint de fleurons glorieux. Car ton bras sait porter l'épée, Il sait porter la croix. Ton histoire est une épopée, Des plus brillants exploits. Et ta valeur, de foi trempée, Protégera nos foyers et nos droits. Protégera nos foyers et nos droits. | English translation O Canada! Land of our forefathers your front is wreathed with a glorious garland of flowers. Because your arm can wield the sword, it is ready to carry the cross. your history is an epic Of the most brilliant exploits. your valour steeped in faith Will protect our homes and our rights Will protect our homes and our rights. |

## Questions

L'Aube Nouvelle (Benin) · La Brabançonne (Belgium) · Le Cantique suisse (Switzerland) · La Marseillaise (France) · O Canada (Canada)
French :
Lessons · Vocabulary · Grammar · Appendices · Texts
# Futurebasic/Language/Reference/on edit
## ON EDIT
### Statement

(+) Appearance (+) Standard Console

### Syntax

ON EDIT {FN userFunction|GOSUB{lineNumber|"stmtLabel"}}

### Description

This statement designates a particular function or subroutine as an edit-event handling routine. An edit-event handling routine is called in response to a keypress, if there is an active editable edit field in the current output window. After such a keypress event occurs, FB does not call your designated routine immediately. Instead, your program continues executing until the next HANDLEEVENTS statement is reached; at that time, FB calls your designated routine once for each keypress event that occurred. FB calls your routine without displaying the new character in the edit field. Your edit-event handling routine should examine the TEKEY$ function to determine which key was pressed. To apply that character (or some other character of your choice) to the edit field, your routine should execute the TEKEY$ statement. If you have not designated any edit-event handling routine, then HANDLEEVENTS applies the keypress directly to the current edit field. The most common use for an edit-event handling routine is to inhibit or alter the display of certain kinds of characters in the edit field. In most cases, you will want the following keys to be processed normally:
* CHR$(8) (delete)
* CHR$(28) (left arrow)
* CHR$(29) (right arrow)
* CHR$(30) (up arrow)
* CHR$(31) (down arrow)
* CHR$(13) (Return (if edit field type allows Return's))

## Example

This program limits the entered contents of the edit field to a number of not more than four digits. DEF FN DoEdit '(prototype)
Note: If you use the ON EDIT FN userFunction syntax, then userFunction must refer to a function which was defined or prototyped at an earlier location in the source code. Your edit-event handling function should not take any parameters, nor return a result. The following kinds of keypresses do not trigger a call to your edit-event handling routine:
* Menu Command-key equivalents;
* -period;
* Arrow keys in a direction that the insertion point can't move (these generate DIALOG events instead);
* Modifier keys (e.g. Shift, Control, etc.) by themselves.
If there is no active editable edit field in the current window or if you are running under the Appearance Compliant runtime, keypresses are treated as DIALOG events (see the _evKey event in the DIALOG function).
# Futurebasic/Language/Reference/on error return

ON ERROR RETURN
Statement
Appearance
Standard
Console
Syntax
ON ERROR RETURN
Description
Use this statement to reinstate FB's standard error checking routines. After this statement is invoked, FB will display an error dialog and halt the program when a file error is encountered. If your program has established its own ON ERROR FN vector, it will be ignored. If you wish to return control to your internal routine or turn off FB's error checking, use ON ERROR END. :
# Futurebasic/Language/Reference/on error end
## ON ERROR END
### Statement

| (+) | Appearance | (+) | Standard | Console |
Syntax:

### Revised

June, 2001 (Release 5)

### Description

There are two possible outcomes when using this statement and they depend on other factors in your program. If you have not established any other error handling routine, then you may use this routine to turn off all error checking. Errors such as file errors will be ignored. It will be your responsibility to track them manually after each file access statement by checking the function ERROR. This concept is demonstrated in the example below.
A second use involves programs where you have set up your own error handling routines. You may toggle between FB's error handling and your program's built-in error handlers by using ON ERROR END to turn off FB's handlers and use the ones in your program. Alternatively, you may use ON ERROR RETURN to reinstate FB's handlers.
Example:
Note: If you turn off error checking (ON ERROR END) and you get an error with x = ERROR, then your program must clear the error variable with ERROR = _noErr