OpenLLM-France/wikimedia huggingface dataset:
# Social Ballroom Dancing

This book is designed as an introduction to Social Ballroom Dancing.

## Introduction

* Introduction
* American vs. International
* Social vs. Competitive
* General Style Guidelines
* Rhythm, Style, and Movement
* Line of Dance

## Dances & Steps
### Standard/Smooth Dances

* Foxtrot
* Waltz
* Quickstep
* Tango
* Viennese Waltz

### Rhythm/Latin Dances

* Cha Cha Cha
* Mambo
* Samba
* Rumba
* Bolero
* East Coast Swing

### Nightclub Dances

* Nightclub Two-step
* West Coast Swing
* Hustle
* Jive
* Lindy Hop

### Latin Nightclub Dances

* Salsa
* Merengue
* Cumbia
* Bachata

## Useful Resources

* Wikipedia's entry on ballroom dance
# Snakes of Europe/Species/Eryx jaculus

Template:Italic title Template:Taxobox
Eryx jaculus, known commonly as the Javelin sand boa, is a species of snake in the Boidae family. First described by Linnaeus in 1758, it is the type species of the genus Eryx.

## Geographic range

Eryx jaculus is found in eastern and south eastern Europe, the Caucasus, the Middle East, and Africa.

## Description

The javelin sand boa may grow to 80 cm (31½ inches) in total length. Coloring varies greatly. Dorsally it may be grayish, tan, brownish, or reddish, with darker blotches or bars in an irregular network. It usually has a dark streak from the eye to the corner of the mouth. Ventrally it is whitish or yellowish. It is heavy-bodied and has a short blunt tail. The ventrals are very narrow, less than ⅓ of the width of the body. The rostral is large and broad with an angular horizontal edge. The eye is separated from the labials by one or two rows of small scales. There are 10-14 upper labials. The dorsal scales are in 40-50 rows, smooth anteriorly, but weakly keeled posteriorly. There are 165-200 ventrals, and 15-34 subcaudals.

## References

* ↑ Template:ITIS
* ↑ McDiarmid, Roy W., Jonathan A. Campbell, and T'Shaka A. Touré, 1999. Snake Species of the World: A Taxonomic and Geographic Reference, vol. 1
* ↑ Arnold, E.N. and J.A. Burton. 1978. A Field Guide to the Reptiles and Amphibians of Britain and Europe. Collins. London. ISBN 0-00-219318-3.
* ↑ Boulenger, G.A. 1893. Catalogue of the Snakes in the British Museum (Natural History), Volume I. London.
# Snakes of Europe/Species/Typhlops vermicularis

Typhlops vermicularis, the European blind snake or European worm snake, is a species of snake in the genus Typhlops, first described by Merrem in 1820. Despite its common name, the range of the European blind snake is from the Balkan Peninsula, the Aegean Islands, and Cyprus to Afghanistan. The common names refer to how it is the only blindsnake of the genus Typhlops naturally found in Europe.

## Biology

Decsribed as growing to 20-35cm in size and being 1cm in diameter. Unlike most relatives, which are oviparous, this species lays 4-8 eggs. It feeds on insect larvae and ants.

## Identification

The rostral scale overhangs the mouth to form a shovel-like burrowing structure. They live underground in burrows, and since they have no use for vision, their eyes are mostly vestigial. They have light-detecting black eye spots, and teeth occur in the upper jaw. The tail ends with a horn-like scale. They can often be confused with earthworms as they are both often seen in leaf litter and detritus on the ground, and in the soil.

## Venom and toxicity

Described as being willing to try to sting with a small spine at the end of its tail.

## Alien species

The only other blindsnake found in Europe is the Brahminy blindsnake, or "flowerpot snake," Ramphotyphlops braminus, where specimens have been discovered lurking in the soil at the Kew Gardens, London.

## References

* ↑ O'Shea, Mark (2007). Boas and Pythons of the World. New Holland Publishers. p. 68. ISBN 9781845375447.
* ↑ http://www.bayramgocmen.com/hc_snakes.html
* ↑ O'Shea, Mark (2007). Boas and Pythons of the World. New Holland Publishers. p. 67. ISBN 9781845375447.
# Snakes of Europe/Preface

THERE is no work in the English language dealing with the Reptiles of Europe. I have therefore endeavoured to supply this desideratum, so far as the Snakes are concerned, by drawing up in a concise form an account of what is known of their characters, their distribution, and their life-histories. Professor Sordelli, of Milan, having kindly acceded to my request to reproduce some of the beautiful figures drawn by him for the work published in collaboration with the late Professor Jan under the title of "Iconographie Generale des Ophidiens". I have been able to supplement my descriptions with illus- trations which leave nothing to be desired from the point of view of accuracy. A few drawings have been made specially for this book by Mr. J. Green. I have further to acknowledge the permission given by the Trustees of the British Museum, the India Office, and the Zoological Society, to reproduce a few figures from previous publications of which I am the author.
In order to render this little book more useful, the account of the Snakes of Europe has been preceded by an Introduction summarizing what is known of Snakes generally.
I have purposely avoided overburdening a work of this kind, which aims at concision, with bibliographical references and synonymic lists. I am sure my readers will be thankful for being spared this display of erudition. Whenever I have had to compile, and to trespass on ground that is not my own, I have been careful to draw only from the writings of the most trustworthy authorities. The descriptions of the species are based on the collection in the British Museum, which has been considerably increased since the publication of the Catalogue of Snakes (1893-1896). I have also had access to Monsieur F. Lataste's rich private collection, now under my care, and Dr. R. Gestro has kindly entrusted to me for study the collection of Italian Snakes in the Genoa Museum. I am indebted to Dr. L. W. Sambon for the chapter on Parasites, which he has written at my request.
To all who have helped me I beg to tender my
hearty thanks.
G.A. Boulenger
1913 edition,
The Snakes of Europe
# Programming Mac OS X with Cocoa for Beginners/Installing the developer tools

Previous Page: What is Cocoa? | Next Page: Getting around in Xcode and Interface Builder
Before you can begin, you need to install the developer tools. These are supplied on a separate CD or DVD with your OS X install discs. Find the CD and insert it. Because Apple works on the principle that developers need less hand-holding than the average user, the installer will not run automatically. Instead, you need to find the "devtools.mpkg" icon, and double-click it to run the installer.
Follow the on-screen instructions carefully. Make sure you have enough disk space available. At this stage, do not be tempted to customise the installation, just do a standard install which will give you everything you need (and more, but you may need it later).
Once the installer has run its course, you will find a new folder at the top level of your machine's disk, called Developer. Note — this is at the root level of the hard disk, not in your Home folder. To find it, you may need to open a Finder window and navigate to the disk itself, depending on how your Finder is configured.
Within Developer→Applications you will find a variety of folders, plus two applications, called Xcode and Interface Builder. These are the two main applications you will be working with throughout this text. You can ignore any others for now.
Double-click Xcode to launch it.
When Xcode starts, it defaults to multi-window mode which is not how this tutorial expects you to use it. In general, single-window mode is easier to use and avoids a confusing proliferation of windows as you work. To change it, before doing anything else, open the Preferences. Under General, choose "All-in-One" layout. In the same place, check the four boxes on the right - "Open counterparts in same editor", "Automatically open/close attached editor", "Automatically Clear Log", "Save Window State". Click OK.
It's also a good idea to make a folder for all the coding work you will do. This should be somewhere in your own Home area — you could make it directly under the Home folder, or perhaps within "Documents". It's up to you. Create the folder in the Finder wherever you want it, and name it "Projects". Xcode will make new folders inside this one for each new application we build.
Now we are ready to begin.
If you plan to work through this text, a good idea is to add the Xcode icon to the Dock for easy access. To do this, simply drag the Xcode icon in the Finder to the Dock.
Previous Page: What is Cocoa? | Next Page: Getting around in Xcode and Interface Builder
# Programming Mac OS X with Cocoa for Beginners 2nd Edition

This book aims to provide beginners with an introduction to the programming of Mac OS X Apps using Cocoa, and XCode, the free developer tools provided by Apple, Inc. Examples of Mac apps are: iTunes, Safari, Mail, iCal, Address Book, Microsoft Word, Microsoft Excel, etc. Using Objective-C, Cocoa and XCode as taught in this wikibook will start your education in how to develop Mac apps.
Many of the skills that you learn in this wikibook can be used to build apps for iOS but there are some differences between Mac OS X apps and iOS apps. This book focuses on Mac OS X apps.
Some knowledge of another programming language, preferably Objective-C. The following link is a link to a wikibook that covers Objective C Programming.
Apple has a Mac App Store where it can sell your Mac apps for you and they will pay you 70% of the proceeds. The Mac App Store is available for users of Mac OS X, 10.6 and later by choosing from the Apple menu "App Store...".
In general, this text is written to be followed in order from start to finish except that if you have experience in C, C++, Java or Python, you are encouraged to look at the relevant section of the Appendix to orient you to developing for Mac OS X and Cocoa.
As each topic develops, it builds on the code written previously to add complexity and functionality, so you are advised to read this wikibook from start to finish in the order that it was written.

### Contents
## What Is Cocoa?

* What Is Cocoa?

## Building a Simple Mac App

* Installing Apple's Developer Tools
* First Cocoa Application - Hello World
* Learning From Hello World

## Building Blocks of Mac OS X Apps

* The Objective C, the Language and Its Advantages
* Frameworks
*** The Foundation Framework
*** The Cocoa Framework
*** The Appkit Framework
*** Other Frameworks

## Building More Complex Mac Apps

* Color Hello World

## More About the Cocoa Framework

* Some Cocoa Essential Principles

## Model-View-Controller (MVC) Design Pattern

* What MVC Is For
* The Model
* The View
** Windows
** Menus
** Other Standard Views
** Custom Views
*** Nib Files for Custom Views
*** Objective-C Code for Custom Views
* The Controller

## More Cocoa Classes

* Containers: Arrays, and Dictionaries

## Other Application Types

* Document-based applications
* Core Data Applications

## Managing Source Code

* Using Git

## The Wikidraw App

* A Simple Drawing App
* Implementing Wikidraw
** Wikidraw's View Class
** More Shapes
** Inspector Calls
** Archiving
** Adding Finesse

## Where to Go Next

* Selling a Mac App on Apple's Mac App Store
* Porting a Mac App to iOS

## Appendix

* Orientation For C Programmers
* Orientation For C++ Programmers
* Orientation For Java Programmers
* Orientation For Python Programmers
# Programming Mac OS X with Cocoa for Beginners/What is Cocoa?

Next Page: Installing the developer tools
Cocoa is possibly one of the most rewarding, fun and productive ways to program a modern computer yet devised. If you own a Mac running Mac OS X, you already have Cocoa, and all the tools needed to program your Mac are available for free from Apple. Anyone who has an interest in programming can use Cocoa to write Mac applications, yet it is not just for beginners; many of the best OS X software titles available are written using Cocoa. You are able to harness the full power of the machine from Cocoa.
Programming using Cocoa involves both using a graphical user interface (GUI -- pronounced "gooey") tool to build your user interfaces, and an integrated development environment (IDE). Cocoa consists of hundreds of ready-built classes, which are pre-programmed modules of reusable code, that you can simply include in your own work. Since these classes are well designed, powerful and fully debugged, using them saves you hundreds of hours in building in complex functionality.
Cocoa is the name given to the complete set of classes, functions and constants, grouped together into an Application Programming Interface, or API. For building Mac applications Cocoa is the only API that is really used anymore. (The other APIs that used to be provided by Apple, the Classic API and the Carbon API have been deprecated.)
To get the most out of this text, you will need to be running Mac OS X 10.3 or later. If you have 10.2, most of what is here will work OK, but the tools as described will be different, and a little harder to use. The coding examples avoid Cocoa features that only exist on 10.3 or 10.4, but later chapters will explain them.
Significant parts of this text describe older versions of Interface Builder. Some of what is described will not work with version 3.0.
Above all, this text aims to get you started in the smoothest way possible, so that you can begin to see not just how powerful Cocoa can be, but also how much fun it is to work with.
Next Page: Installing the developer tools
# ProLaw/Front Office
## Front Office

Front Office is the case management portion of Prolaw. It is comprised of four major tools. They can be found on the toolbar:
* Contacts. Tools for managing contact information for all of the individuals related to a case.
* Matters. Customizable tools for managing the data in the cases themselves.
* Events. The Tasks, Reminders, Hearings, and Documents related to a case.
* Files. Tools for tracking physical case-related material.
# ProLaw
## About ProLaw

ProLaw is a case law management and Accounting software package designed for law firms... but also quite usable by government agencies! ProLaw stores data in a Microsoft SQL Server database and is a Thomson Elite product.
The latest versions (v2018 & v2017) are quite stable and are used by a majority of ProLaw firms. There are still firms running v11, which was released in roughly 2008.
ProLaw is also very customizable. Although it doesn't have an API--and having worked at ProLaw/Thomson-Elite for 8 years, the word was always that they would never create an API--ProLaw allows a wide variety of automation and customization. Examples of ProLaw automation and ProLaw tools demonstrate the types of ProLaw automation and ProLaw customization possible.

## Contents

* Front Office
** Contacts
** Matters
** Events
* Back Office
* Reports

## External Links

* ProLaw Homepage
* Thomson Elite Homepage
# Pro Engineer/Create Features

Models in Pro/Engineer are constructed from a series of features. The features are represented in a model tree that can be displayed on screen. The basic workflow changed between Pro/Engineer version 2001 and the Pro/Engineer Wildfire releases. The procedures here are written for Pro/Engineer Wildfire releases, as generically as possible. Where there is a difference between Wildfire releases, Wildfire 2.0 has been used.

## Feature Creation

* Typical feature creation processes

## Feature types
### Solid features

* Extrude
* Revolve
* Hole
* Chamfer
* Round (Fillet)

### Datum features

* Datum planes
* Datum curves
* Datum points
* Datum coordinate systems
# Private International Law/International Development

International law puts up regulations for the smooth running of international development projects.
Doktorsavhandlingens koncept och uppgifter daInternational civil process.
# Private International Law/Multinational Corporations
## Structure

Multinational corporations may be structured in a number of ways.

### Pyramid

In a pyramid structure, one parent company controls a number of subsidiary companies, each of which specializes in a particular type of business or a particular region of the world. Most MNCs headquartered in the US and Europe are organized around a pyramid structure.
Some pyramids may have more than one company at the top. Shell and Unilever are two well-known examples: both have two parent companies, one in the UK and one in the Netherlands.

### Consortium

A consortium is a group of independent companies who collaborate on major business projects. One well-known consortium is Airbus Industrie, which existed for many years as a consortium of four European aerospace companies before it was incorporated as a French company in 2001.

### Keiretsu

The keiretsu structure originated in Japan and is still unique to Japanese MNCs. In a keiretsu, a number of nominally independent companies coordinate operations, and exercise control over each other through extensive cross-shareholding. During the Cold War era, major keiretsu such as Mitsubishi, Mitsui and Sumitomo were organized around major commercial banks; today, this system has weakened somewhat.

## Unitary nature

Most multinationals are treated as a single company for accounting purposes, but each company is treated separately for tax purposes.

## Domicile

Corporations have a form of "citizenship," in that they are formed and headquartered in a particular state. This concept is called domicile. A company's internal affairs are generally governed by the laws of the jurisdiction in which it is domiciled.
In the United States, as in the Netherlands, domicile is based upon the state in which the company is incorporated. Most large companies are incorporated in the state of Delaware, but headquartered in New York or another location; their domicile is considered to be Delaware even if they engage in no business there.
In large parts of Europe, but excluding the Netherlands and other countries, domicile is based upon the company's place of management (called siège in French and Sitz in German). A company may be managed in a different location from its principal place of business, and still keep domicile in the place of management; see Centros v. Erhvervs-og Selkabsstyrelsen, [1999] ECR 1-1459.
Domicile generally determines which laws will apply to the internal affairs of a company. In the U.S. Supreme Court case of Sumitomo Shoji v. Avagliano, 457 U.S. 176 (1982), a New York-domiciled subsidiary of a Japanese company was found to be a New York company; it was therefore subject to U.S. discrimination laws, not to contrary treaty provisions that applied to Japanese companies doing business in the U.S.
# Pro Engineer/Convert String to Number using Relations

Create parameters:
* digitlist, type string
* value, type real
* digit_found, type integer
# Pro Engineer

Pro/Engineer or Pro E is the software product of PTC (Parametric Technology corporation) its initial versions were Pro/E 1, 2... up to 19. Later Pro/E launched sequentially versions as Pro/Engineer 2000; 2000i, 2000i$^2$;2001, Wildfire 1.0; Wildfire 2.0, Wildfire 3.0; Wildfire 4.0; and Wildfire 5.0. In 2011, PTC rebranded Pro/Engineer as Creo Parametric. The current version of the software is 5.0. This book will explore the various philosophies and methodologies employed by professionals who use the Computer Aided Design (CAD) package Pro/Engineer. Additional topics include how to acquire the software and optimal support.
Notes to Contributors:
Please write Pro/Engineer and Pro/Intralink fully not pro/e, pro/engineer or any other variation. Conventions:
* RMB - Right Mouse Button
* LMB - Left Mouse Button
* MMB - Middle Mouse Button
* BMB - Both Mouse Buttons
* ICON - Link to image
All items assumed to be from top menu unless left menu is mentioned

## Section One: How to...

* Understand the Pro/Engineer operating environment
* Spin, pan, and zoom the model view
* Select and query select for features
* Use memory, save parts, and copy parts
* Use Sketcher
* Create Features
* Resolve regeneration failures
* Measure and analyze
* Create assemblies
* Create drawings
* Control model color and appearance
* Use Find

## Section Two: Data Management

* Pro/Intralink
* Windchill
* Non-PTC
** Metaphase, Teamcentre
** Matrix One
** SAP

## Section Three: Hardware and OS

* Configuring plotters
* Graphics Cards
** Issues
* Windows / Unix

## Section Four: Customization

* Start parts, start assemblies, and drawing templates
* User Interface, including config.win
* Mapkeys
* Configuration file, including config.pro and config.sup
* Drawing setup files, including .dtl settings.
* Web/Link
* J/Link

## Section Five: Philosophy

* Design Intent
* Top Down Design Methodology
* Shown vs Created Dimensions

## Section Six: Dealing with PTC

* Getting the best deal
* Getting the best from support
* Getting the best from consultancy

## Section Seven: Reference

* Definitions
* Detail FAQ
* Surface FAQ
* Surface Tips
* Family Table Tips
* Pro/Intralink Tips
* ↑ http://www.ptc.com/appserver/wcms/standards/textsub.jsp?&im_dbkey=161796&icg_dbkey=21
# Private International Law

* Foundations of international law - from Grotius onwards
* Multinational Corporations
* International Taxation
* International Sales
* International Licensing
* International Investment
* International Development
# Radiation Oncology/Toxicity/Otalgia

* Front Page: Radiation Oncology | RTOG Trials | Randomized Trials
Otalgia
Sensory innervation of the ear:
* Auriculotemporal branch of the trigeminal nerve (CV V)
* Ramsey-Hunt branch of facial nerve (CV VII)
* Arnold branch of the vagus nerve (CN X)
* First and second cervical nerves
Noxious stimulation of any above-mentioned branches may be interpreted as otalgia
# Radiation Oncology/Toxicity/Pituitary

* Front Page: Radiation Oncology | RTOG Trials | Randomized Trials
Hypothalamus-Pituitary Axis RT Tolerance
# Radiation Oncology/Toxicity/Pregnancy

* Front Page: Radiation Oncology | RTOG Trials | Randomized Trials
Pregnancy and Radiation Therapy
Literature Review
# Radiation Oncology/Toxicity/Pelvis
## Pelvic Organ Toxicity

This page contains papers dealing with pelvic radiotherapy toxicity in general.
Please also see more specific topics:
* Rectum
* Bladder
* Small bowel
* Erectile dysfunction
* Fertility - Ovary, Testis
* Bone (Femoral heads)
* Bone marrow

## Reviews

* 2009 PMID 19765845 -- "Dose-volume effects for normal tissues in external radiotherapy: pelvis." (Fiorino C, Radiother Oncol. 2009 Nov;93(2):153-67.)
** Literature review: Rectum, Bladder, Bowel, Sexual function (erectile dysfunction, fertility, ovary, testis), Femoral heads (and pelvic bones), Bone marrow.
# Radiation Oncology/Toxicity/Ovary

* Front Page: Radiation Oncology | RTOG Trials | Randomized Trials
Ovarian Tolerance
* Ovary contains a fixed pool of primordial oocytes, maximal at 5 months gestational age
* Oocytes decrease in a biexponential fashion, culminating in menopause (average age 50-51)
* Rate of decrease accelerates ~ age 37 years, when ~25,000 primordial oocytes remain
* At menopause, ~1,000 oocytes remain
* Radiosensitivity of the human oocyte is <2 Gy
* Estimated sterilizing dose decreases with increasing age, because the remaining oocyte population is becoming depleted with age
* Time-dependency
** Acute ovarian failure (AOF): loss of ovarian function during or shortly after cancer therapy
** Premature menopause: retention of ovarian function after cancer therapy, but development of menopause <40