OpenLLM-France/wikimedia huggingface dataset:
# Dutch Empire/Director-Generals of New Netherland

| | Name | In Office | Notes |
| 1 | Cornelis Jacobszoon May | 1624–1625 | May was the captain of the ship New Netherland who delivered the first boat load of colonists to New Netherland on Governors Island in June of 1624. Having transformed the New Netherland territory to a province, he was named the province's first director. |
| 2 | Willem Verhulst | 1625–1626 | Oversaw the decision to locate the company's main fortress and town on the tip of Manhattan Island in the colony of New Netherland. |
| 3 | Peter Minuit | 1626–1632 | Was the founder of the Swedish colony of New Sweden in 1638, and purchased the Island of Manhattan from the Canarsee Native Americans on May 24, 1626. |
| 4 | Sebastiaen Jansen Krol | 1632–1633 | Was commander of Fort Orange(present day Albany) previous to this post. |
| 5 | Wouter van Twiller | 1633–1638 | Twiller purchased 'Noten Eylant', later called Governors Island from a tribe of Native Americans. |
| 6 | Willem Kieft | 1638–1647 | Started a war with the Native Americans in 1643(which became known as Kiefts War), and was fired in 1647. |
| 7 | Peter Stuyvesant | 1647–1664 | Last, greatest, and most famous, Director-General. Expanded the size of New Netherland, settled disputes with Native Americans and the English, and ordered the construction of the protective wall on Wall Street, the canal that became Broad Street, and Broadway. He did not want to surrender the colony to the English in 1664, but under pressure from the Colonists and overwhelming odds, he was forced to. See, "place names" for places named after Stuyvesant. |
| 8 | Anthony Colve | 1673–1674 | Anthony Colve was commissioned as the Governor of New York when the Netherlands reclaimed New York City after nine years of British rule. |
# Dutch Empire/Dutch Culture During the Golden Age

The Dutch Golden Age was an age of wealth and prosperity in the Dutch Republic roughly from 1590-1715. Along with wealth, Dutch trade, science, and art were among the most acclaimed in the world.

## Wealth

During a large part of the 17th century the Dutch, traditionally able seafarers and keen mapmakers, dominated world trade, a position which before had been occupied by the Portuguese and Spaniards, and which later would be lost to England. With the VOC dominating trade in Asia, their wealth came into the Netherlands. The Dutch also dominated trade between European countries. The Low Countries were favorably positioned on a crossing of east-west and north-south trade routes and connected to a large German hinterland through the Rhine river. Dutch traders shipped wine from France and Portugal to the Baltic lands and returned with grain destined for countries around the Mediterranean Sea. The Trip brothers, arms traders, built the Trippenhuis in Amsterdam, currently the seat of the Royal Netherlands Academy of Arts and Sciences, which is a typical example of 17th century architecture.

## Social Structure and Religion

Dutch society promoted freedom of expression and religious tolerance, with a wide array of religions from atheists to Catholics. There was a large and well-established middle class, and an excellent educational system.

## Culture

As a result of their trade, the Dutch were the wealthiest and most prosperous nation. There was a vast appreciation for the arts, and some of the most famous Baroque artists were Dutch, such as Vermeer, Rembrandt, and Reubens
# Dutch Empire/German Invasion of the Netherlands
## The Invasion

On the morning of May 10, 1940 the Dutch awoke to the sound of aircraft engines roaring in the sky. Nazi Germany had commenced operation Fall Gelb and attacked the Netherlands, Belgium, France and Luxembourg: in the case of the Low Countries without a declaration of war given before hostilities.
The Luftwaffe was guaranteed air superiority over the Netherlands. The Dutch Air Force, the Militaire Luchtvaartafdeling (ML), had a strength of 144 combat aircraft, half of which were destroyed within the first day of operations. The remainder was dispersed and accounted for only a handful of Luftwaffe aircraft shot down. In total the ML flew a mere 332 sorties losing 110 of its aircraft.
The German 18th Army secured all the strategically vital bridges in and toward Rotterdam, which penetrated Fortress Holland(The main area of Dutch defence) and bypassed the New Water Line from the south. However, an operation organised separately by the Luftwaffe to seize the Dutch seat of government, Battle for The Hague, ended in complete failure. The airfields surrounding the city (Ypenburg, Ockenburg, and Valkenburg) were taken with heavy casualties and transport aircraft losses, only to be lost that same day to counterattacks by the two Dutch reserve infantry divisions. The Dutch captured or killed 1,745 Fallschirmjäger, shipping 1,200 prisoners to England. The Luftwaffe's Transportgruppen also suffered heavily. Transporting the German paratroops had cost it 125 Ju 52 destroyed and 47 damaged, representing 50 percent of the fleet's strength. Most of these transports were destroyed on the ground, and some whilst trying to land under fire, as German forces had not properly secured the airfields and landing zones.
The French 7th Army failed to block German armoured reinforcements of the 9th Panzer Division; they reached Rotterdam on 13 May. That same day in the east the Dutch retreated from the Grebbe Line to the New Water Line, when a counter-offensive to contain a German breach had failed.
An attempt by the Germans to cross the Afsluitdijk in the North, a thin dike that stretches from Friesland to North-Holland, failed. The German troops were unable to pass the Dutch fortifications and had to withdraw to their original positions.
The Dutch Army, still largely intact, surrendered in the evening of 15 May after the Bombing of Rotterdam by Heinkel He 111s of Kampfgeschwader 54 on the 14th killing about 900 civilians, and threats to do the same to other major Dutch Cities. They considered their strategic situation to have become hopeless and feared a further destruction of the major Dutch cities. However, the Dutch troops in Zealand and the colonies continued the fight while Queen Wilhelmina established a government-in-exile in Britain.
# Dutch Empire/Dutch Kings and Queens

Here are the Kings and Queens of the Netherlands, since the modern government was formed in 1815.
| | Name | Reign | Notes |
| 1 | King William I | 1815–1840 | William I, born Willem Frederik Prins van Oranje-Nassau (The Hague, August 24, 1772 - Berlin, December 12, 1843), was the first King of the Netherlands. He succeeded his father as head of the House of Orange-Nassau in 1805, was named 'Sovereign Prince' of the Netherlands in 1813, proclaimed himself King in 1815, and abdicated in 1840. William I was also the Grand Duke of Luxembourg after 1815 and Duke of Limburg after 1839 until his abdication in 1840. |
| 2 | King William II | 1840–1849 | William II (William Frederick George Louis) (December 6, 1792 – March 17, 1849) was King of the Netherlands, Grand Duke of Luxembourg, and Duke of Limburg from October 7, 1840 until his death. |
| 3 | King William III | 1849–1890 | William III (Willem Alexander Paul Frederik Lodewijk van Oranje-Nassau) (February 19, 1817 – November 23, 1890) was from 1849 King of the Netherlands and Grand Duke of Luxembourg until his death and the Duke of Limburg until the abolition of the Duchy in 1866. |
| 4 | Queen Wilhelmina | 1890–1948 | Wilhelmina (Wilhelmina Helena Pauline Marie of Orange-Nassau; August 31, 1880 – November 28, 1962) was queen regnant of the Kingdom of the Netherlands from 1890 to 1948. She ruled the Netherlands for fifty-eight years, longer than any other Dutch monarch. Her reign saw many turning points in both Dutch and world history: World War I and World War II, the Great Crisis of 1933, as well as the decline of the Netherlands as a major colonial empire. Outside the Netherlands she is primarily remembered for her role in the Second World War, in which she proved to be a great inspiration to the Dutch resistance, as well as a prominent leader of the Dutch government in exile. |
| 5 | Queen Juliana | 1948–1980 | Juliana (Juliana Emma Louise Marie Wilhelmina van Oranje-Nassau; April 30, 1909 – March 20, 2004) was Queen regnant of the Kingdom of the Netherlands from her mother's abdication in 1948 to her own abdication in 1980. |
| 6 | Queen Beatrix | 1980–2013 | Beatrix (Beatrix Wilhelmina Armgard); born January 31, 1938) was the Queen regnant of the Kingdom of the Netherlands April 30, 1980 - April 30, 2013, when she abdicated. |
| 7 | King Willem-Alexander | 2013-Incumbent | Willem-Alexander (Willem-Alexander Claus George Ferdinand); born 27 April 1967) is the King of the Kingdom of the Netherlands, including the Netherlands proper (with the Caribbean Netherlands), and the countries of Curaçao, Aruba, and Sint Maarten. He is head of the Dutch royal house and the House of Amsberg. |
# ERP Internals/Modules/Investment Manager/Functions/Maintain Module Information/Modify GL Distribution

The GL Distribution parameters contain every General Ledger account number that the Investment Manager module can post to. This function allows the Systems Administrator or the Module Administrator to change those account numbers.
# ERP Internals/Modules/Job Costing/Reports

* Job List
* Job Summary
* Job Detail
# ERP Internals/Modules/Investment Manager/Reports

Investment Manager generates the following reports:
* Summary
* Detail
* Investment Transactions
* Trial Balance
# ERP Internals/Modules/Job Costing/Functions

Job Costing has the following functions:
* Maintain Job Information
* Find a Job
* Enter Transactions
* Print Job Summary
* Maintain Module Information
# ERP Internals/Modules/Job Costing/Functions/Maintain Module Information

Some parameters and data tables are used by every module. These are maintained by Systems Administration. But, every module has some parameters and/or data tables that it alone uses. Systems Administration can change this information but each module has a function "Maintain Module Information" that can change it as well. This allows segments of systems administration to be delegated to the senior person in charge of a particular module.
# ERP Internals/Modules/Job Costing/Functions/Find a Job

This function is used when the user doesn't know the job's number or description but does know some information about the job. They enter what they know and the ERP displays all the jobs that match the criteria. This function becomes more and more useful as the size of the enterprise increases
# ERP Internals/Modules/Job Costing/Functions/Maintain Module Information/Modify GL Distribution

The GL Distribution parameters contain every General Ledger account number that the Job Costing module can post to. This function allows the Systems Administrator or the Module Administrator to change those account numbers.
# ERP Internals/Modules/Layout

The Introduction section contains one or more paragraphs describing the major functions of the module.
The Functions link lists all the tasks that the module can do. Typically, a module has a few functions that are used very heavily and a dozen or so additional functions that are used occasionally.
The Reports link lists all the reports the module can produce. Although the word "report" implies paper, most of the reports will only be viewed on the user's screen.
The Tables section lists the major data tables that the module uses. Most tables are used by more than one module.
The Data Exchange section describes which other modules this module communicates with.
The Transactions section describes the transactions that can occur within the module. Typically there are less than a dozen types of transactions of which two or three form the bulk of the actual transactions.
# ERP Internals/Modules/Manufacturing

Some businesses build their products from parts and raw materials. These products can range from the assembly of a few standard parts to products with thousands of parts requiring weeks of engineering. Manufacturing (which is actually a group of sub-modules) controls the process by which this is done. Not every ERP package has a Manufacturing module although all the large ones do.
Manufacturing is divided into discrete and process manufacturing. Discrete manufacturers make solid items such as flashlights or cars using Bills of Material. Process manufacturers make liquids or chemicals using formulas or recipes. Manufacturing can also be divided into Make-To-Stock or Make/Engineer-To-Order.
Manufacturing has a Maintain Module Information function that handles the parameters and data tables for the sub-modules.
Here is an incomplete list of the sub-modules in Manufacturing:
* Bill of Materials
* Master Production Schedule
* Advanced Planning and Scheduling
* Shop Floor Control
* Quality
# ERP Internals/Modules/Job Costing

Sometimes, the item sold requires days or weeks to create. During the process, job costing tracks actual costs, compares them to planned costs, and displays the resulting variances in the form of reports and graphs. Costs are divided into the following categories: Direct Materials, Direct Labor, Sub-contract, and Overhead (or Burden). This allows management to keep track of costs relative to the percentage the job is complete. Every ERP package has a Job Costing module.
* Functions
* Reports

## Tables

The first table is the Job table which contains one record for every job. The second table is the Transaction table which contains one record for every transaction (labor, materials, sub-contract, adjustment). There is at least one transaction for every job and there can be many

## Data Exchange

Job Costing sends transactions to General Ledger and Payroll.
# COLOR WINDOW statement
## COLOR WINDOW
### Syntax

COLOR WINDOW {_true | _false}

### Description

This statement does nothing in modern FB, but is retained for backwards compatibility with programs written in FutureBasic II. In modern FB, all windows are opened as color windows.
# COMPILE LONG IF statement
## COMPILE LONG IF
### Statement

✔ Appearance ✔ Standard ✔ Console

### Syntax

COMPILE LONG IF condition  [statementBlock1] [COMPILE XELSE  [statementBlock2]] COMPILE END IF

### Description

You can use the COMPILE LONG IF statement to conditionally include or exclude selected lines of code from the compiled version of your program. This is useful if you need to maintain two (or more) slightly different versions of your program; COMPILE LONG IF allows you to maintain them both within the same source file.
If the condition following COMPILE LONG IF is evaluated as "true" or non-zero, then the statements in statementBlock1 are included in the compilation and the statements (if any) in statementBlock2 are ignored by the compiler. If the condition is evaluated as "false" or zero, then the statements in statementBlock1 are ignored by the compiler, and the statements (if any) in statementBlock2 are included in the compilation.
condition must be in one of the following forms:
* constExpr
* {DEF | NDEF} _symbolicConstant
* TRON [= _false]
* cpu68K
* cpuPPC
* carbonLib
* A list of any of the above separated by "AND" or "OR". You may also optionally surround any valid sub-condition with parentheses.
constExpr is a "static integer expression." A static integer expression is any valid expression which consists of only:
* integer literal constants;
* previously-defined symbolic constant names;
* operators (like +, -, *, /, >, =);
* parentheses
(In particular, it can't contain variables, nor function references.) If you use this form of COMPILE LONG IF, then the condition will be evaluated as "true" if the expression's value is nonzero.
_symbolicConstant stands for a symbolic constant name. DEF_symbolicConstant is evaluated as "true" if the indicated constant was previously defined. NDEF_symbolicConstant is evaluated as "true" if the indicated constant was not previously defined.
The condition TRON is evaluated as "true" if debugging has been activated for the current section of code. The condition TRON = _false is evaluated as "true" if debugging has not been activated for the current section of code. (See the <a href="tron.html">TRON</a> statement for more details.)
If you use the keyword cpu68K as the condition, it's evaluated as "true" if the current compilation is being compiled into Motorola 680x0 ("68k") machine code. If you use the keyword cpuPPC as the condition, it's evaluated as "true" if the current compilation is being compiled into PowerPC machine code.

### Example

Because COMPILE LONG IF can cause lines (including non-executable lines) to be completely ignored by the compiler, you can use it to control such things as the declaration of variables, program labels, constants, and even entire functions. For example:
COMPILE LONG IF _needBigArray  DIM myArray&(3000) COMPILE XELSE  DIM myArray&(30) COMPILE END IF
COMPILE LONG IF _dimensions = 3  DEF FN Diagonal!(a!, b!, c!) = SQR(a!*a! + b!*b! + c!*c!) COMPILE XELSE  DEF FN Diagonal!(a!, b!) = SQR(a!*a! + b!*b!) COMPILE END IF
Note: COMPILE LONG IF blocks can be nested to a depth of 16 levels.

### See Also

Beginassem; Tron
Language Reference
# COMPILE SHUTDOWN statement
## COMPILE SHUTDOWN
### Statement

✔ Appearance ✔ Standard ✔ Console

### Syntax

COMPILE SHUTDOWN "Optional Quoted Remark"

### Description

You may have some code that is specifically designed for one platform or another. For instance, 68K assembly cannot be compiled into a PPC application. In such cases, COMPILE SHUTDOWN would abort the compile process with an error and show the offending line complete with the optional quoted remark.

### Example

COMPILE LONG IF cpuPPC  COMPILE SHUTDOWN "This won't work in PPC." COMPILE XELSE  ` move.l d0,-(SP) COMPILE END IF
# CLOSE LPRINT statement
## Syntax

CLOSE LPRINT

## Revised

November, 2006 (FB 4, Revision 4)

## Description

After output has been routed to the printer, CLOSE LPRINT informs the Print Manager that the print job is complete. The current page is printed and the print job closed. You should execute a ROUTE _toScreen statement immediately before or after calling CLOSE LPRINT.

## Notes

Before using CLEAR LPRINT or CLOSE LPRINT, you must route printing to the screen. Closing the printer while output is pointing to the printed page is equivalent to cutting off a limb while you are sitting on it. The following fragment shows how this might be done.
ROUTE _toScreen CLOSE LPRINT

## Example

NEED IMG!!! <img src="res/cd.gif" alt="" height="19" width="20" border="0"> CD Example: Printer.BAS

## See Also

CLEAR LPRINT DEF LPRINT
DEF PAGE ROUTE_toPRINTER ROUTE toSCREEN
# COLOR statement
## COLOR
### Statement

✔ Appearance ✔ Standard ✔ Console

### Syntax

COLOR [=] colorExpr

### Description

The COLOR statement sets the current window's foreground color to one of eight old-style "Basic QuickDraw" colors. colorExpr should equal one of the following:
0 (_zWhite) 1 (_zYellow) 2 (_zGreen) 3 (_zCyan) 4 (_zBlue) 5 (_zMagenta) 6 (_zRed) 7 (_zBlack)
"FB Lite" behavior: When you use the "FB Lite" runtime, COLOR switches to the Graphics Window before executing; you can't use it to change the foreground color in the Text Window nor on the printer. To change the color of printed output while running FB Lite, use the Toolbox procedure <a href="http://developer.apple.com/documentation/mac/QuickDraw/QuickDraw-221.html">RGBFORECOLOR</a>.
Note: The COLOR statement does not change the appearance of anything that's already in the window; the new color will appear the next time you draw text or a QuickDraw shape in the window.
For greater control over the foreground color, use the LONG COLOR statement.

### See Also

Language Reference
LONG COLOR
# COMPILEFLAGS function
## COMPILEFLAGS
### Function

| (+) | Appearance | (+) | Standard | (+) | Console |

### Syntax

flag& = COMPILEFLAGS(_compileConstant)

### Description

Compile statements are directives to the compiler to change the way it evaluates and compiles code. (See <a href="compile.html">COMPILE</a> for a complete list of compiler directives.) Compile flags do not literally exist as accessible variables in the application but are used to set internal flags during compilation.
You can use this function to check specific flags which may be required by your application or to provide notes to another programmer about how to improve or streamline their code.
LONG IF COMPILEFLAGS(_dimmedVarsOnly) = _false PRINT "It is much better to check "Use only ¬ DIMensioned variables" in the preferences window."
END IF
In addition to all of the standard compiler flags, this function can return additional information.
_FB3CpuCode = 0x00020000 '0=68K/1=-PPC _FB3ErrorCount = 0x00040000 '# of errors so far _FB3WarningCount = 0x00080000 '# of warnings so far _FB3FloatDivChar = 0x00100000 '"/" or "\" _FB3HideWarnings = 0x00200000 'show/hide warnings

### See Also

COMPILE COMPILE LONG IF COMPILE SHUTDOWN
# COMPILERVERSION function
## COMPILERVERSION
### Function

✔ Appearance ✔ Standard ✔ Console

### Syntax

versionNum& = COMPILERVERSION

### Description

This function returns the current version of the compiler. The number is internally set before each compiler is shipped. The purpose of this function is to determine whether or not a specific functionality is present before a particular command is executed.
If, for example, you wanted to invoke a routine that was not added to the compiler until version 3 release 2, you would check the version as follows:
LONG IF COMPILERVERSION < 0x03020000  PRINT "You need a newer compiler to run this." XELSE  REM new operation goes here. END IF
The COMPILERVERSION function always returns a long word which is formatted as follows:
Byte 1 = Version number Byte 2 = Release number Byte 3 = Revision Number Byte 4 = Fix
# CLOSE FOLDER statement
## CLOSE FOLDER
### Statement

| (+) | Appearance | (+) | Standard | (+) | Console |

### Syntax

CLOSE FOLDER wdRefNum%

### Description

This statement causes the specified working directory reference number to be removed from the System's list of current working directories.
A working directory reference number is a temporary number which is used to uniquely identify a certain directory (folder) on a certain currently-mounted volume. These numbers are generated by the System software on request; several FB functions (such as the FILES$ function) generate and return working directory reference numbers. A folder is considered to be "open" once a working directory reference number has been generated for it.
The System's list of current working directories has a limited amount of space available; executing CLOSE FOLDER may in some cases help prevent the list from becoming full. In addition, a folder cannot be deleted from disk while it remains on the list: you may therefore find it necessary to execute CLOSE FOLDER if you intend to delete a folder.
After CLOSE FOLDER has been executed, the working directory reference number is no longer valid, and can no longer be used to identify that folder.

### See Also

FILES$