OpenLLM-France/wikimedia huggingface dataset:
# WxWidgets
## Introduction

wxWidgets formerly known as wxWindows is a framework for developing cross-platform GUI applications in C++. Julian Smart started the framework in 1992 at the Artificial Intelligence Applications Institute, University of Edinburgh. In 1995, a port to Xt was released by Markus Holzem. In May 1997, the Windows and the GTK+ ports were merged and put into a CVS repository.

## What is wxWidgets

wxWidgets gives you a single, easy-to-use API for writing GUI applications on multiple platforms. Link it with the appropriate library for your platform (Windows/Unix/Mac) and compiler (almost any popular C++ compiler), and your application will adopt the look and feel appropriate to that platform. On top of the great GUI functionality, wxWindows gives you: online help, network programming, streams, clipboard and drag and drop, multithreading, image loading and saving in a variety of popular formats, database support, HTML viewing and printing, and much more.

## Who should use wxWidgets

wxWidgets is a framework very much similar to MFC, except for a few negative points of its own. Those MFC programmers who are aware of the growing number of Linux users and who want to write cross platform GUI applications can use wxWidgets. With wxWidgets, it is very easy to use a framework based on C++ and it has a proven record of 13 years. In fact, wxWidgets is very stable and is supported on:
* Windows 3.1, Windows 95/98, Windows NT, Windows 2000/XP, Windows ME, Windows CE.
* Linux and other UNIX platforms with GTK+.
* UNIX with Motif or the free Motif clone Lesstif.
* Mac OS.
* Embedded platforms are being investigated. See the wxUniversal project.
* An OS/2 port is in progress, and you can also compile wxWidgets for GTK+ or Motif on OS/2.

## Why use wxWidgets

There are a number of options available for writing cross platform GUI development, like: JAVA, Mono.NET, Qt, etc. Java has failed to prove itself as an efficient alternative. Qt is good but commercial and nobody knows its future. Mono.NET seems to be good but is largely driven by Microsoft, it seems like a copy of the work done by Microsoft and it has not yet proved itself as a successful alternative. Also, people would not like to use an extra burden of layer for highly efficient software. As wxWidgets does not use any middle layer and uses only the native controls available on the platform, it gives a nice look and feel to the application.
# X-COM: Apocalypse Strategy Guide
## Introduction

While X-COM: Apocalypse is not exactly a hard game, it can quickly become hard if you let your position slip. This guide is intended for new players that have never played the game before, and will therefore only contain a few spoilers. Note that this guide only deals with the real time aspect of the game.

## Table of Contents
### Gameplay

* General Tips
* Equipment
* First Week

### Meta

* Spoilers
* OpenApoc
# X-COM: Apocalypse Strategy Guide/General Tips
## Agents

There are three sort of agents you can hire.

### Humans

The standard agent. Most of your staff will be human. They are average agents for all things and a jack of all trades.

### Mutants

Mutants are an interesting twist on human agents. They have more Psi energy, attack, and defense then standard human agents. However they have less health and strength then humans. As a result mutants make good psychers, but fit poorly in other agent roles.

### Androids

Androids are agents with more health, strength, and accuracy then human agents. In addition to this, they have total immunity to psy attacks. However this comes at a severe cost, Android agents are unable to make psy attacks themselves, nor can they progress. In this sense, they are much like SHIVs in other X-COM games.
# World economy

Economy of the world
The world economy or global economy is the economy of all humans of the world, referring to the global economic system, which includes all economic activities which are conducted both within and between nations, including production, consumption, economic management, work in general, exchange of financial values and trade of goods and services. In some contexts, the two terms are distinct "international" or "global economy" being measured separately and distinguished from national economies, while the "world economy" is simply an aggregate of the separate countries' measurements. Beyond the minimum standard concerning value in production, use and exchange, the definitions, representations, models and valuations of the world economy vary widely. It is inseparable from the geography and ecology of planet Earth.
# World Stamp Catalogue/Abu Dhabi
## Abu Dhabi

| Date Issued | Denom. | Paper. | Color | Perf. | Type Die/Wmk | Subject | Cat. No. Mi/Sc/Gi | Design | No. Issued | Designer/ Engraver | notes |
| 1964-3-30 | | | | | | | | | | | FDC |
| 1967 | 40f | | | | | | | | | | |
* Postage stamps and postal history of Abu Dhabi
# World Stamp Catalogue/Aden Protectorate States
## Aden

* Postage stamps and postal history of Aden

## Postage Stamps

| Date Issued | Denom. | Subject | Cat. No. Mi/Sc/Gi |
| | | | 11 |
| | | | 16-27 |
| | | | 27 |
| | | | 30-31 |
| 1937 | ½ a | | |
| 1939 | 2 ½ a | | |
| 1942 | 2 ½ a | Kathiri Seiyun | |
| 1942 | 2 a | Quaiti Shihr Mukalla | |
| 1951 | 2 /- on 2 Rs | | |
| 1953 | 20 /- | | |
# World Stamp Catalogue/A
### Countries (A)

* Abu Dhabi
* Abyssinia (Ethiopia)
* Aden Protectorate States
* Afars and Issas
* Afghanistan
* Aitutaki
* Ãland Islands
* Alawite (Alaouites) State
* Albania
* Algeria
* Allenstein
* Andorra (French)
* Andorra (Spanish)
* Angola
* Anguilla
* Anjouan
* Annam and Tongkin
* Antigua
* Antioquia
* Argentina
* Argentine Territories
* Armenia
* Aruba
* Ascension
* Australia
* Australia State of New South Wales
* Australia State of Queensland
* Australia State of South Australia
* Australia State of Tasmania
* Australia State of Victoria
* Australia State of Western Australia
* Australian Antarctic Territory
* Austria
* Austrian Post Abroad
* Azerbaijan
* Azores
* Azores Territories
# World Stamp Catalogue/Afghanistan
## Afghanistan

* Postage stamps and postal history of Afghanistan
# World Stamp Catalogue/Africa
## A

* Afars & Issas
* Algeria
* Angola
* Anjouan
* Ascension

## B

* Basutoland
* Belgian Congo
* Benin
* Biafra
* Botswana
* British Somalia
* Burkina Fasso
* Burundi

## C

* Camerun
* Cape Verde
* Central Africa
* Chad
* Comores
* Congo (Brazzaville)
* Congo (Dem. Rep.)
* Congo (Kinshasa)

## D

* Dahomey
* Djibouti

## E

* East Africa
* Egypt
* Equatorial Africa
* Equatorial Guinea
* Eritrea
* Ethiopia — Ethiopian Postal Service

## F

* Fernando Poo
* Fezzan
* French Central Congo
* French Morocco (1912-1956)
** French Post Office In Morocco (1891-1911)
* French Somalia
* French Sudan
* French West Africa

## G

* Gabon
* Gambia
* Ghana
* Gold Coast
* Guinea (Rep.)
* Guinea Bissau

## I

* Ifni
* Inhambane
* Italian Libia
* Italian Somalia
* Ivory Coast

## K

* Kenya
* Kionga

## L

* Lesotho
* Liberia
* Libya
* Lourenço Marques

## M

* Madagascar
* Malawi
* Mali
* Mauretania
* Mauritius
* Mayotte
* Mozambique
* Mozambique Company

## N

* Namibia
* Natal
* Niger
* Nigeria
* Nyassa Company
* Nyassaland

## P

* Portuguese Congo
* Portuguese Guinea

## Q

* Quelimane

## R

* Reunion
* Rhodesia
* Rhodesia & Nyassaland
* Rhodesia, North
* Rhodesia, Southern
* Rio Muni
* Ruanda
* Ruanda Urundi

## S

* Sahara
* Saint Helena
* Sao Thome & Principe
* Senegal
* Seychelles
* Seychelles, Zil Eloigne Sesel
* Sierra Leone
* Somalia
* South Africa
** Boputhatswana
** Ciskei
** Transkei
** Venda
* South-West Africa
* Spanish Guinea
* Spanish Morocco
* Spanish Sahara
* Stellaland
* Sudan
* Swaziland

## T

* Tanzania
* Tete
* Togo
* Tristan da Cunha
* Tunisia

## U

* Uganda
* Upper Volta

## Z

* Zambia
* Zanzibar
* Zambézia
* Zimbabwe
# XSLTForms/Triggers not working

A common cause of triggers not working is that the actions in the trigger are not listening for any events.
The following trigger illustrates the problem. It is meant, when activated, to replace the value of the current element with the string "Hello <strong>World</strong>!". But nothing happens when the trigger is pressed.
The solution is to specify the event(s) which will cause the setvalue action to fire.
# XSLTForms/Naming Conventions

In its current form, this book is the product of many hands. Usage of namespace prefixes and variable names is not consistent across the pages of the book.
As a step towards beginning to make the book more consistent, however, this page lists some conventions the reader will encounter in at least some page in the book.

### Namespaces and namespace prefixes

It's not always convenient to provide explicit namespace declarations in every example in a book. In principle, the rules of XML namespaces mean that any prefix (including the empty prefix) can be used to denote any namespace, but as a convention, the namespace prefixes listed here will sometimes be used without declaration in examples. When that is the case, they should be understood as being bound to the namespaces indicated. (Often more than one prefix for the same namespace is listed here; that is one form of inconsistency in the current state of the book.)
* xf = http://www.w3.org/2002/xforms
* ev = http://www.w3.org/2001/xml-events
* xs = http://www.w3.org/2001/XMLSchema
* xsd = http://www.w3.org/2001/XMLSchema
* xsltforms = http://www.agencexml.com/xsltforms
* rte = http://www.agencexml.com/xsltforms/rte
[Note to authors / editors: add to this list!]

### Other naming conventions

[more needed here]
# Performance and optimization
## Where does the time go?

The first step in dealing with any performance problem is to measure the form and see where the time is going.
XSLTForms includes a built-in profiler and debugger, which can be made visible by including the processing instruction <?xsltforms-options debug="yes"?> at the top of your document, or (normally) by pressing F1 in a desktop browser. At the top of the screen, the label "Debug mode" will appear, together with version information and the reminder "Press F1 to toggle mode." Below the "Debug mode" heading two buttons will appear, labeled "Profiler" and "Trace log".
Clicking on the "Profiler" button will cause a time profile for the form to be opened in a new tab or window. Among other things it will show the cumulative time spent evaluating all the XPath expressions in the form. In some cases, a very small number of expressions consume a large percentage of the evaluation time; the profiler allows optimization effort to be concentrated where it will do the most good.
[Some general advice on optimization would be useful here. Use subforms, exploit locality, etc.]

## Does running the XSLT transform in the client slow things down?

Tests and performance measurements show that the XSL transformation time is very short, whatever the browser.
The time to initialize the structures of the XPath interpreter and processing of interactions with the user depends on the performance of the browser's JavaScript engine.
Some results here: http://www.web21th.com/samples/performances.htm [No longer available, February 2017]
These tests were made in May 2009, with some modifications in XSLTForms source in order to introduce probes.
# Presentation

"dialog" element allows to show and hide controls in a popup approach.
A dialog is a container control with a mandatory @id attribute. It can be placed anywhere in the (X)HTML body element, considering that it will be transformed as a disabled (or hidden) DIV element by the XSLT step of XSLTForms.
A dialog is rendered using z-index property in a modal popup, with another DIV element covering all the main elements, with a lower z-index value, to disable interaction with controls. When changing controls values in a dialog, all other controls can be refreshed whether they are in this dialog or anywhere else. Label is not yet supported by XSLTForms and there is no X trigger.
Dialogs can be nested. Ancestor dialogs are masked automatically, changing the z-index property of the covering DIV.
Two actions are defined for dialogs management:
* "show": this action will enable the dialog identified by the @dialog attribute value
* "hide": this action will disable the dialog identified by the @dialog attribute value
Usually, for each dialog, there should be, at least, one trigger for showing (opening) it and another, in itself, for hiding (closing) it.

# References

* W3C XForms WG Wiki - Dialog candidate specifications for XForms 1.2
* AJAXForms Addons - Specific dialog addon
* Orbeon Dialog Extension
# XSLTForms/XForms 2.0/XPath 2.0 Functions
## XPath 2.0 and 3.0 functions

XPath 2.0 and 3.0 functions supported by XSLTForms (alphabetical order):
[Some description of XPath 2.0 item-type declarations possibly needed here, to explain the signatures ...]
* distinct-values($heap as xs:anyAtomicType*)
* ends-with($haystack as xs:string, $needle as xs:string)
* format-number($value as numeric?, $picture as xs:string)
* lower-case(nodeset?)
* replace($input as xs:string, $pattern as xs:string, $replacement as xs:string)
* string-join($bricks as xs:string*, $glue as xs:string)
* tokenize($input as xs:string, $pattern as xs:string)
* upper-case(nodeset?)
Also the mathematical functions abs, acos, asin, atan, atan2, cos, exp, log, power, random, sin, sqrt, and tan. [Signatures to be supplied.]
N.B. this list is complete as of version r638.
There are a number of XPath 2.0 functions that have not yet been implemented in r638.

## XForms 2.0 functions

N.B. This list does not include functions that were already defined in XForms 1.1.
XSLTForms has (as of r638) implemented these:
* serialize
These are apparently not yet implemented in XSLTForms (as of r638) (in alphabetical order): attribute, bind, case, element, eval, eval-in-context, location-param, location-uri, parse, readonly, relevant, required, seconds-from-dateTime, seconds-from-epoch, seconds-to-dateTime, uri-authority, uri-fragment, uri-host, uri-param-names, uri-param-values , uri-path, uri-port, uri-query, uri-scheme, uri-scheme-specific-part, uri-user-info.
# XSLTForms/XForms 2.0

XSLTForms is supporting extensions of XForms 1.1 World Wide Web Consortium recommendation which are planned to be specified in the next specifications of XForms.

# Details

* "show" attribute
* The xf:dialog, xf:show, and xf:hide elements
* XPath 2.0 Functions
The function element of XForms 2.0 appears not yet to be supported in XSLTForms as of February 2017 (but XSLTForms does have support for user-defined functions, which can be defined in Javascript and added to the registry of XPath functions so they can be called from within XPath expressions.)

# References

* Draft spec of XForms 2.0
* XPath Expressions Module for XForms 2.0
* XForms community group main page (links to all modules currently under development)
# 3D Printing/Applications
## Rapid Prototyping

When making prototypes, having quick tangible feedback is of great importance for spotting facets of a work which are not immediately clear on paper or in computer models.

## One off production

When producing just one or a few items, the inherent inefficiencies of 3D printing matter much less, especially if the properties of 3D printed materials are adequate or if the time to begin production is limited (Taking just a few hours or days assuming the model is ready).

## Accessibility

3D printing can be used to create tactile versions of visual media like artwork or maps for the blind.

## Logistic stopgap

When supply chains are disrupted in an emergency, local 3D printer owners are able to produce low quantities of vital materials and parts, ensuring a constant, if very small stream of new supplies, while logistical challenges are fixed. This very scenario was seen in the early days of the COVID-19 pandemic, when 3D printer operators made PPE and ventilator parts for hospital staff. It is also a strategy employed by some disaster preparedness strategies.

## References

* ↑ "Please Touch the Art: 3D Printed Masterworks for the Blind". www.vice.com. Retrieved 29 November 2020.
* ↑ Karbowski, Caroline (24 February 2020). "See3D: 3D Printing for People Who Are Blind". Journal of Science Education for Students with Disabilities. doi:10.14448/jsesd.12.0006. Retrieved 29 November 2020.
* ↑ "One Way to Help Strapped Hospitals? Print PPE Using 3D Printers". NPR.org. Retrieved 7 November 2020.
* ↑ Fracassi, Cristian; Romaioli, Alessandro (22 March 2020). "Opinion We Made Copies of Ventilator Parts to Help Hospitals Fight Coronavirus". The New York Times. Retrieved 29 November 2020.
* ↑ "Doomsday Preppers Are Planning to 3D Print Their Way Through the Apocalypse". www.vice.com. Retrieved 29 November 2020.
# 360 Assembly/Comments

A comment in 360 Assembly is a portion of text that is not processed by the assembler and is used by the programmer to add a description to the code. There are three forms of comments, line comments, code comments and macro comments.

## Line Comments

If a line begins with one (or more) asterisks ("*), the rest of the line is treated as a comment
Caution: The assembler uses a line beginning with *PROCESS to optionally set certain options if a *PROCESS line appears as the first line in the source file.

## Code Comments

After a valid 360 instruction, after a single blank, everything else on the line is treated as a comment. For the purpose of this example it is assumed that R14 is equated to 14, R15 is equated to 15 etc., to provide cross reference - see EQU Assembler pseudo-instruction)
A comment - line or code - is not printed when it appears in a macro if PRINT NOGEN has been used. It is also not printed if it appears after a PRINT OFF statement has been issued.
Note: If a code comment is to be specified on a macro instruction where no arguments are to be passed to the macro, it is recommended that a space, a comma, and another space precede the comment to prevent the first word from being interpreted as an argument to the macro.

## Macro Comments

Macro comments are used for commenting macros (but can be used outside of macros in mainline program code), and are not listed on the program listing. They are the same as code comments, only they begin with ".*" instead of "*".
360 Assembler Pseudo Instructions :
| Address Related | ADATA • CNOP • DROP • EQU • LOCTR • LTORG • ORG • USING |
| Code Related | ALIAS • AMODE • CATTR • COM • CSECT • CXD • DSECT • DXD • END • ENTRY • EXTRN • OPSYN • RMODE • RSECT • START • WXTRN • XATTR |
| Data Related | CCW • CCW0 • CCW1 • DC • DS |
| Conditional Assembly and Macro related | ACTR • AGO • AIF • AINSERT • ANOP • AREAD • COPY • GBLA / GBLB / GBLC • LCLA / LCLB / LCLC • MACRO • MEND • MEXIT • MNOTE • SETA / SETB / SETC |
| Listing, output and source related | Comments • *PROCESS • ACONTROL • EJECT • END • EXITCTL •ICTL • ISEQ • POP • PRINT • PUNCH • PUSH • REPRO • SPACE • TITLE |
360 Assembly Language :
| 360 Family | Introduction · Basic FAQ · 360 Family · 360 Architecture |
| 360 Instruction Set | 360 Instructions · Branch Instructions · Data Transfer Instructions · Control Flow Instructions · Arithmetic Instructions · Logic Instructions · Shift and Rotate Instructions · Priveleged Instructions · Other Instructions |
| Syntaxes and Assemblers | 360 Assemblers· Pseudo Instructions |
| Instruction Extensions | Floating Point · High-Level Languages |
# Other Instructions

There are a number of specialized instructions for the IBM 360/370/390/Z-System which don't fit neatly into the rest of the groups of instructions.
* Program Return - PR
* Set Addressing Mode (to 24 bits) - SAM24
* Set Addressing Mode (to 31 bits) - SAM31
* Set Addressing Mode (to 64 bits) - SAM64
* Set Clock Programmable Field - SCKPF
* Supervisor Call - SVC - Used to request services from the operating system.
* Test Addressing Mode - TAM
* Trap - TRAP2
* Update Tree - UPT
360 Assembly Language :
| 360 Family | Introduction · Basic FAQ · 360 Family · 360 Architecture |
| 360 Instruction Set | 360 Instructions · Branch Instructions · Data Transfer Instructions · Control Flow Instructions · Arithmetic Instructions · Logic Instructions · Shift and Rotate Instructions · Priveleged Instructions · Other Instructions |
| Syntaxes and Assemblers | 360 Assemblers· Pseudo Instructions |
| Instruction Extensions | Floating Point · High-Level Languages |
# 360 Assembly/Introduction
## Why Learn Assembly?

Assembly is the most primitive tool in the programmers toolbox. Entire software projects can be written without ever once looking at a single line of assembly code. So the question arises: why learn assembly? Assembly language is the closest form of communication that humans can engage in with a computer. Using assembly, the programmer can precisely track the flow of data and execution in a program. Also, another benefit to learning assembly, is that once a program has been compiled, it is difficult—if not impossible—to decompile the code. That means that if you want to examine a program that is already compiled, you will need to examine it in assembly language. Debuggers also will frequently only show the program code in assembly language. If nothing else, it can be beneficial to learn to read assembly language, if not write it.
On mainframe computers it is usual that most programs are written in C, Cobol, Fortran , PL/I or other high level languages. There are a small number of reasons for learning a mainframe assembly language.
* Work on compilers for high-level languages
* Work on operating system exits
* Maintenance of existing assembly language applications
* Work on security applications
* Updating screen maps for CICS or other applications which were written as Assembler macros.

## Who is This Book For?

This book will serve as an introduction to mainframe assembly language, but it will also serve as a good resource for people who already know the topic, but need some more information on 360 system architecture, and advanced uses of 360 assembly language. All readers are encouraged to read (and contribute to) this book, although a prior knowledge of programming fundamentals would be a definite benefit.
Next: 360 Assembly/Basic FAQ
360 Assembly Language :
| 360 Family | Introduction · Basic FAQ · 360 Family · 360 Architecture |
| 360 Instruction Set | 360 Instructions · Branch Instructions · Data Transfer Instructions · Control Flow Instructions · Arithmetic Instructions · Logic Instructions · Shift and Rotate Instructions · Priveleged Instructions · Other Instructions |
| Syntaxes and Assemblers | 360 Assemblers· Pseudo Instructions |
| Instruction Extensions | Floating Point · High-Level Languages |
# A Guide to Discord/Emojis

Emojis are icons that are used to convey emojis through text. Along with standard emojis, Discord allows users to create custom emojis exclusive to their servers.

## Emoji Picker

Access the Emoji Picker by clicking the grayed-out emoji in the right corner of the text box. The user can then select an emoji, or filter an emoji by category using the buttons at the bottom of the picker. Custom emojis will be sorted by server. Hold shift and left click to add multiple emojis. Alt+Click an emoji to add it to your "Favorites".

## Custom Emoji

Go to "Server Settings" and use the "Emoji" tab to upload a maximum of 50 custom emoji to the server. You must have "manage emoji" permissions enabled to due so.
Emoji names must be at least two characters long and contain only alphanumeric characters and underscores. Emojis can be uploaded in sizes up to 128x128 pixels, although they will be resized to 32x32 pixels. The emoji file size must be smaller than 256kb. Custom emojis can only be used on the server they have been uploaded too, unless you have a Nitro subscription.