100% found this document useful (1 vote)
31 views

Download full Beginning Functional JavaScript: Uncover the Concepts of Functional Programming with EcmaScript 8 2nd Edition Srikanth Machiraju ebook all chapters

EcmaScript

Uploaded by

snithbates91
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
31 views

Download full Beginning Functional JavaScript: Uncover the Concepts of Functional Programming with EcmaScript 8 2nd Edition Srikanth Machiraju ebook all chapters

EcmaScript

Uploaded by

snithbates91
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 65

Download the Full Version of textbook for Fast Typing at textbookfull.

com

Beginning Functional JavaScript: Uncover the


Concepts of Functional Programming with EcmaScript
8 2nd Edition Srikanth Machiraju

https://textbookfull.com/product/beginning-functional-
javascript-uncover-the-concepts-of-functional-programming-
with-ecmascript-8-2nd-edition-srikanth-machiraju/

OR CLICK BUTTON

DOWNLOAD NOW

Download More textbook Instantly Today - Get Yours Now at textbookfull.com


Recommended digital products (PDF, EPUB, MOBI) that
you can download immediately if you are interested.

Beginning Functional JavaScript. Functional Programming


with JavaScript using EcmaScript 6 1st Edition Anto
Aravinth
https://textbookfull.com/product/beginning-functional-javascript-
functional-programming-with-javascript-using-ecmascript-6-1st-edition-
anto-aravinth/
textboxfull.com

Beginning Functional JavaScript: Functional Programming


with JavaScript Using EcmaScript 6 1st Edition Anto
Aravinth
https://textbookfull.com/product/beginning-functional-javascript-
functional-programming-with-javascript-using-ecmascript-6-1st-edition-
anto-aravinth-2/
textboxfull.com

Functional Programming in JavaScript How to improve your


JavaScript programs using functional techniques First
Edition Luis Atencio
https://textbookfull.com/product/functional-programming-in-javascript-
how-to-improve-your-javascript-programs-using-functional-techniques-
first-edition-luis-atencio/
textboxfull.com

Functional Programming in JavaScript How to improve your


JavaScript programs using functional techniques 1 edition
Edition Luis Atencio
https://textbookfull.com/product/functional-programming-in-javascript-
how-to-improve-your-javascript-programs-using-functional-
techniques-1-edition-edition-luis-atencio/
textboxfull.com
Functional and Concurrent Programming Core Concepts and
Features 1st Edition Charpentier

https://textbookfull.com/product/functional-and-concurrent-
programming-core-concepts-and-features-1st-edition-charpentier/

textboxfull.com

Mathematica Functional and procedural programming 2nd


Edition V. Aladjev

https://textbookfull.com/product/mathematica-functional-and-
procedural-programming-2nd-edition-v-aladjev/

textboxfull.com

Functional Python Programming Discover the power of


functional programming generator functions lazy evaluation
the built in itertools library and monads 2nd Edition
Steven F. Lott
https://textbookfull.com/product/functional-python-programming-
discover-the-power-of-functional-programming-generator-functions-lazy-
evaluation-the-built-in-itertools-library-and-monads-2nd-edition-
steven-f-lott/
textboxfull.com

Get Programming with JavaScript Next New features of


ECMAScript 2015 2016 and beyond 1st Edition Jd Isaacks

https://textbookfull.com/product/get-programming-with-javascript-next-
new-features-of-ecmascript-2015-2016-and-beyond-1st-edition-jd-
isaacks/
textboxfull.com

Web Applications with Elm: Functional Programming for the


Web 1st Edition Wolfgang Loder

https://textbookfull.com/product/web-applications-with-elm-functional-
programming-for-the-web-1st-edition-wolfgang-loder/

textboxfull.com
Contents
1. Cover
2. Front Matter
3. 1. Functional Programming in Simple Terms
4. 2. Fundamentals of JavaScript Functions
5. 3. Higher Order Functions
6. 4. Closures and Higher Order Functions
7. 5. Being Functional on Arrays
8. 6. Currying and Partial Application
9. 7. Composition and Pipelines
10. 8. Fun with Functors
11. 9. Monads in Depth
12. 10. Pause, Resume, and Async with Generators
13. 11. Building a React-Like Library
14. 12. Testing and Closing Thoughts
15. Back Matter

Landmarks
1. Cover
2. Table of Contents
3. Body Matter
Anto Aravinth and Srikanth Machiraju

Beginning Functional JavaScript


Uncover the Concepts of Functional
Programming with EcmaScript 8
2nd ed.
Anto Aravinth
Chennai, Tamil Nadu, India

Srikanth Machiraju
Hyderabad, Andhra Pradesh, India

Any source code or other supplementary material


referenced by the author in this book is available
to readers on GitHub via the book’s product page,
located at www.apress.com/ . For more detailed
information, please visit
http://www.apress.com/source-code .
ISBN 978-1-4842-4086-1 e-ISBN 978-1-4842-4087-8
https://doi.org/10.1007/978-1-4842-4087-8

Library of Congress Control Number: 2018964615

© Anto Aravinth, Srikanth Machiraju 2018

This work is subject to copyright. All rights are reserved by the


Publisher, whether the whole or part of the material is concerned,
specifically the rights of translation, reprinting, reuse of
illustrations, recitation, broadcasting, reproduction on microfilms
or in any other physical way, and transmission or information
storage and retrieval, electronic adaptation, computer software,
or by similar or dissimilar methodology now known or hereafter
developed.
Trademarked names, logos, and images may appear in this book.
Rather than use a trademark symbol with every occurrence of a
trademarked name, logo, or image we use the names, log os, and
images only in an editorial fashion and to the benefit of the
trademark owner, with no intention of infringement of the
trademark. The use in this publication of trade names,
trademarks, service marks, and similar terms, even if they are not
identified as such, is not to be taken as an expression of opinion
as to whether or not they are subject to proprietary rights.

While the advice and information in this book are believed to be


true and accurate at the date of publication, neither the authors
nor the editors nor the publisher can accept any legal
responsibility for any errors or omissions that may be made. The
publisher makes no warranty, express or implied, with respect to
the material contained herein.

Distributed to the book trade worldwide by Springer


Science+Business Media New York, 233 Spring Street, 6th Floor,
New York, NY 10013. Phone 1-800-SPRINGER, fax (201) 348-
4505, e-mail orders-ny@springer-sbm.com, or visit
www.springeronline.com. Apress Media, LLC is a California LLC
and the sole member (owner) is Springer Science + Business
Media Finance Inc (SSBM Finance Inc). SSBM Finance Inc is a
Delaware corporation.
Introduction

The second edition of a book is always special.


When I wrote the first edition, I had about two
years of IT experience. The book received positive
as well as negative responses. I always wanted to
work on the negative responses to make the
content better and make the book worth the price.
In the meantime, JavaScript evolved a great deal.
Many ground-breaking changes were added into
the language. The Web is full of JavaScript, and
imagine a world without the Web. Hard, right?

This second edition is a much improved


version that teaches the fundamentals of
functional programming in JavaScript. We have
added much new content in this second edition;
for example, we will be building a library for
building web applications using functional
concepts, and we have added sections on testing as
well. We have rewritten the book to match the
latest ES8 syntax with many samples of async,
await patterns, and a lot more!

We assure you that you will gain a lot of


knowledge from this book and at the same time
you will have fun while running the examples.
Start reading.
Acknowledgments

I remember the first code that I wrote for Juspay


Systems in my first job as an intern. Coding was
fun for me; at times it is challenging, too. Now with
six years of software experience, I want to make
sure I pass on all the knowledge I have to the
community. I love teaching people. I love to share
my thoughts with the community to get feedback.
That’s exactly the reason I’m writing a second
edition of this book.

I have to acknowledge few people who have


been standing right next to me in all phases of my
life: my late father Belgin Rayen, mother Susila,
Kishore (brother-in-law), Ramya (sibling), and
Joshuwa (my new little nephew). They have been
supportive and pushed me harder to achieve my
goals. I want to say thanks to Divya and the
technical reviewer of this book, as they did a
wonderful job. Luckily, I have a wonderful
coauthor in Srikanth, who did an amazing job as
well.

Finally, I want to give special thanks to Bianaca,


Deepak, Vishal, Arun, Vishwapriya, and Shabala,
who have added joy to my life.

Please reach out to me at


anto.aravinth.cse@gmail.com with any
feedback.

—Anto Aravinth

I would like to thank Apress for providing me a


second opportunity to author. I would also like to
thank my family, especially my dear wife Sonia
Madan and my four-month-old son Reyansh for
supporting me throughout this stint. I’m always
reachable at
Vishwanath.srikanth@gmail.com for any
feedback or questions.

—Srikanth Machiraju
TABLE OF CONTENTS
Chapter 1: Functional Programming in Simple Terms
What Is Functional Programming? Why Does It Matter?
Referential Transparency
Imperative, Declarative, Abstraction
Functional Programming Benefits
Pure Functions
Pure Functions Lead to Testable Code
Reasonable Code
Parallel Code
Cachable
Pipelines and Composable
A Pure Function Is a Mathematical Function
What We Are Going to Build
Is JavaScript a Functional Programming Language?
Summary
Chapter 2: Fundamentals of JavaScript Functions
ECMAScript: A Bit of History
Creating and Executing Functions
First Function
Strict Mode
Return Statement Is Optional
Multiple Statement Functions
Function Arguments
ES5 Functions Are Valid in ES6 and Above
Setting Up Our Project
Initial Setup
Our First Functional Approach to the Loop Problem
Gist on Exports
Gist on Imports
Running the Code Using Babel-Node
Creating Script in Npm
Running the Source Code from Git
Summary
Chapter 3: Higher Order Functions
Understanding Data
Understanding JavaScript Data Types
Storing a Function
Passing a Function
Returning a Function
Abstraction and Higher Order Functions
Abstraction Definitions
Abstraction via Higher Order Functions
Higher Order Functions in the Real World
every Function
some Function
sort Function
Summary
Chapter 4: Closures and Higher Order Functions
Understanding Closures
What Are Closures?
Remembering Where It Is Born
Revisiting sortBy Function
Higher Order Functions in the Real World (Continued)
tap Function
unary Function
once Function
memoize Function
assign function
Summary
Chapter 5: Being Functional on Arrays
Working Functionally on Arrays
map
filter
Chaining Operations
concatAll
Reducing Function
reduce Function
Zipping Arrays
zip Function
Summary
Chapter 6: Currying and Partial Application
A Few Notes on Terminology
Unary Function
Binary Function
Variadic Functions
Currying
Currying Use Cases
A logger Function: Using Currying
Revisit Curry
Back to logger Function
Currying in Action
Finding a Number in Array Contents
Squaring an Array
Data Flow
Partial Application
Implementing partial Function
Currying vs. Partial Application
Summary
Chapter 7: Composition and Pipelines
Composition in General Terms
Unix Philosophy
Functional Composition
Revisiting map,filter
compose Function
Playing with the compose Function
curry and partial to the Rescue
compose Many Functions
Pipelines and Sequence
Implementing pipe
Odds on Composition
The Pipeline Operator
Debugging Using the tap Function
Summary
Chapter 8: Fun with Functors
What Is a Functor?
Functor Is a Container
Implementing map
MayBe
Implementing MayBe
Simple Use Cases
Real-World Use Cases
Either Functor
Implementing Either
Reddit Example Either Version
Word of Caution: Pointed Functor
Summary
Chapter 9: Monads in Depth
Getting Reddit Comments for Our Search Query
The Problem
Implementation of the First Step
Merging Reddit Calls
Problem of Nested/Many maps
Solving the Problem via join
join Implementation
chain Implementation
Summary
Chapter 10: Pause, Resume, and Async with Generators
Async Code and Its Problem
Callback Hell
Generators 101
Creating Generators
Caveats of Generators
yield Keyword
done Property of Generator
Passing Data to Generators
Using Generators to Handle Async Calls
Generators for Async: A Simple Case
Generators for Async: A Real-World Case
Async Functions in ECMAScript 2017
Promise
Await
Async
Chaining Callbacks
Error Handling in Async Calls
Async Functions Transpiled to Generators
Summary
Chapter 11: Building a React-Like Library
Immutability
Building a Simple Redux Library
Building a Framework Like HyperApp
Virtual DOM
JSX
JS Fiddle
CreateActions
Render
Patch
Update
Merge
Remove
Summary
Chapter 12: Testing and Closing Thoughts
Introduction
Types of Testing
BDD and TDD
JavaScript Test Frameworks
Testing Using Mocha
Mocking Using Sinon
Testing with Jasmine
Code Coverage
Linting
Unit Testing Library Code
Closing Thoughts
Summary
Index
ABOUT THE AUTHORS AND ABOUT THE
TECHNICAL REVIEWER

ABOUT THE AUTHORS


Anto Aravinth

has been in the software


industry for more than six
years. He has developed
many systems that are
written in the latest
technologies. Anto has
knowledge of the
fundamentals of JavaScript
and how it works and has
trained many people. Anto is also does OSS in his
free time and loves to play table tennis.

Srikanth Machiraju

has over ten years of experience as a developer,


architect, technical trainer, and community
speaker. He is currently working as Senior
Consultant with Microsoft Hyderabad, leading a
team of 100 developers and quality analysts
developing an advanced
cloud-based platform for a
tech giant in the oil
industry. With an aim to be
an enterprise architect who
can design hyperscale
modern applications with
intelligence, he constantly
learns and shares modern
application development
tactics using cutting-edge
platforms and
technologies. Prior to Microsoft, he worked with
BrainScale as Corporate Trainer and Senior
Technical Analyst on application design,
development, and migrations using Azure. He is a
tech-savvy developer who is passionate about
embracing new technologies and sharing his
learning via blog and community engagements. He
has also authored the “Learning Windows Server
Containers” and “Developing Bots with Microsoft
Bot Framework,” blogs at
https://vishwanathsrikanth.wordpress
.com . He runs his own YouTube channel called
“Tech Talk with Sriks” and is active on LinkedIn at
https://www.linkedin.com/in/vishsrik
/.
ABOUT THE TECHNICAL REVIEWER
Sakib Shaikh

has been working as a Tech


Lead with a large scientific
publisher, with more than
ten years of experience as a
full stack developer with
JavaScript technologies on
front-end and back-end
systems. He has been
reviewing technical books
and articles for the past
few years and contributes
to the developer community as a trainer, blogger,
and mentor.
© Anto Aravinth, Srikanth Machiraju 2018
Anto Aravinth and Srikanth Machiraju, Beginning Functional JavaScript
https://doi.org/10.1007/978-1-4842-4087-8_1

1. Functional Programming in
Simple Terms
Anto Aravinth1 and Srikanth Machiraju2
(1) Chennai, Tamil Nadu, India
(2) Hyderabad, Andhra Pradesh, India

The first rule of functions is that they should


be small. The second rule of functions is that
they should be smaller than that.
—Robert C. Martin
Welcome to the functional programming world,
a world that has only functions, living happily
without any outside world dependencies, without
states, and without mutations—forever. Functional
programming is a buzzword these days. You might
have heard about this term within your team or in
a local group meeting. If you’re already aware of
what that means, great. For those who don’t know
the term, don’t worry. This chapter is designed to
introduce you to functional terms in simple
English.

We are going to begin this chapter by asking a


simple question: What is a function in
mathematics? Later, we are going to create a
function in JavaScript with a simple example using
our function definition. The chapter ends by
explaining the benefits that functional
programming provides to developers.

What Is Functional Programming? Why


Does It Matter?
Before we begin to explore what functional
programming means, we have to answer another
question: What is a function in mathematics? A
function in mathematics can be written like this:
f (X) = Y
The statement can be read as “A function f, which takes X as its
argument, and returns the output Y.” X and Y can be any number,
for instance. That’s a very simple definition. There are key
takeaways in the definition, though:
A function must always take an argument.

A function must always return a value.

A function should act only on its receiving arguments (i.e., X),


not the outside world.
For a given X, there will be only one Y.
You might be wondering why we presented the
definition of function in mathematics rather than
in JavaScript. Did you? That’s a great question. The
answer is pretty simple: Functional programming
techniques are heavily based on mathematical
functions and their ideas. Hold your breath,
though; we are not going to teach you functional
programming in mathematics, but rather use
JavaScript. Throughout the book, however, we will
be seeing the ideas of mathematical functions and
how they are used to help understand functional
programming.
With that definition in place, we are going to see the examples
of functions in JavaScript. Imagine we have to write a function
that does tax calculations. How are you going to do this in
JavaScript? We can implement such a function as shown in Listing
1-1.

var percentValue = 5;
var calculateTax = (value) => { return
value/100 * (100 + percentValue) }

Listing 1-1 Calculate Tax Function

The calculateTax function does exactly


what we want to do. You can call this function with
the value, which will return the calculated tax
value in the console. It looks neat, doesn’t it? Let’s
pause for a moment and analyze this function with
respect to our mathematical definition. One of the
key points of our mathematical function term is
that the function logic shouldn’t depend on the
outside world. In our calculateTax function,
we have made the function depend on the global
variable percentValue. Thus this function we
have created can’t be called as a real function in a
mathematical sense. Let’s fix that.
The fix is very straightforward: We have to just move the
percentValue as our function argument, as shown in Listing 1-
2.

var calculateTax = (value, percentValue) => {


return value/100 * (100 + percentValue) }

Rewritten calculateTax
Listing 1-2

Function

Now our calculateTax function can be


called as a real function. What have we gained,
though? We have just eliminated global variable
access inside our calculateTax function.
Removing global variable access inside a function
makes it easy for testing. (We will talk about the
functional programming benefits later in this
chapter.)
Now we have shown the relationship between
the math function and our JavaScript function.
With this simple exercise, we can define functional
programming in simple technical terms.
Functional programming is a paradigm in which
we will be creating functions that are going to
work out their logic by depending only on their
input. This ensures that a function, when called
multiple times, is going to return the same result.
The function also won’t change any data in the
outside world, leading to a cachable and testable
code base.

FUNCTIONS VS. METHODS IN JAVASCRIPT

We have talked about the word function a lot in


this text. Before we move on, we want to make
sure you understand the difference between
functions and methods in JavaScript.

Simply put, a function is a piece of code that


can be called by its name. It can be used to pass
arguments that it can operate on and return
values optionally.

A method is a piece of code that must be


called by its name that is associated with an
object.

Listing 1-3 and Listing 1-4 provide quick examples of a


function and a method.
var simple = (a) => {return a} // A simple
function
simple(5) //called by its name

Listing 1-3 A Simple Function


var obj = {simple : (a) => {return a} }
obj.simple(5) //called by its name along
with its associated object

Listing 1-4 A Simple Method

There are two more important characteristics of


functional programming that are missing in the
definition. We discuss them in detail in the
upcoming sections before we dive into the benefits
of functional programming.

Referential Transparency
With our definition of function, we have made a statement that all
the functions are going to return the same value for the same
input. This property of a function is called a referential
transparency . A simple example is shown in Listing 1-5.

var identity = (i) => { return i }

Referential Transparency
Listing 1-5

Example
In Listing 1-5, we have defined a simple function called
identity. This function is going to return whatever you’re
passing as its input; that is, if you’re passing 5, it’s going to return
the value 5 (i.e., the function just acts as a mirror or identity).
Note that our function operates only on the incoming argument i,
and there is no global reference inside our function (remember in
Listing 1-2, we removed percentValue from global access and
made it an incoming argument). This function satisfies the
conditions of a referential transparency. Now imagine this
function is used between other function calls like this:

sum(4,5) + identity(1)
With our referential transparency definition, we can convert
that statement into this:

sum(4,5) + 1

Now this process is called a substitution model


as you can directly substitute the result of the
function as is (mainly because the function doesn’t
depend on other global variables for its logic) with
its value. This leads to parallel code and caching.
Imagine that with this model, you can easily run
the given function with multiple threads without
even the need to synchronize. Why? The reason for
synchronizing comes from the fact that threads
shouldn’t act on global data when running parallel.
Functions that obey referential transparency are
going to depend only on inputs from their
argument; hence threads are free to run without
any locking mechanism.
Because the function is going to return the
same value for the given input, we can, in fact
cache it. For example, imagine there is a function
called factorial, which calculates the factorial
of the given number. Factorial takes the input
as its argument for which the factorial needs to be
calculated. We know the factorial of 5 is going to
be 120. What if the user calls the factorial of 5 a
second time? If the factorial function obeys
referential transparency, we know that the result
is going to be 120 as before (and it only depends
on the input argument). With this characteristic in
mind, we can cache the values of our factorial
function. Thus if factorial is called for a second
time with the input as 5, we can return the cached
value instead of calculating it once again.
Here you can see how a simple idea helps in
parallel code and cachable code. We will be writing
a function in our library for caching the function
results later in the chapter.

REFERENTIAL TRANSPARENCY IS A
PHILOSOPHY

Referential transparency is a term that came


from analytic philosophy (
https://en.wikipedia.org/wiki/Anal
ytical_philosophy ). This branch of
philosophy deals with natural language
semantics and its meanings. Here the word
referential or referent means the thing to which
the expression refers. A context in a sentence is
referentially transparent if replacing a term in
Exploring the Variety of Random
Documents with Different Content
in arabischer in Süd-Algerien
Botanische Definition der Teile in Aegypten
Schrift[34] (Biskra)

Blattscheide, nebst dem kurnâf ‫ كرناف‬kurnâth,


verbreiterten Basalteil des kurschéf (in
Blattstiels Tunesien)
kerânif (Plur.) ‫كرانيف‬
Blattfiedern, Fiedern des chótss, chútss ‫ خوص‬ssôf
Palmblatts
Blattfiedern, im eingeschlossenen sá'f, ‫زعف‬
Zustande, solange sie noch weiß
sind ssá'af ‫سعف‬

dornige Blattfiedern im unteren ssill ‫ سل‬ssirb


Teile des Blatts
sill ‫زيل‬
2 Blattreihen, Spiralen des dôr ‫دور‬
jährlichen Zuwachses
dorên ‫دورين‬
Blütenscheide, spatha ttala' ‫ طلع‬ttala'
ttalhh
gerâb (Ast.) ‫جراب‬
kuss (Ast.) ‫كوس‬
ghelâfa,
kuss ghlâf ‫كوس الغالف‬
(Qor.)
männlicher Blütenstand 'argûn ‫ عرجون‬ardschûn
weiblicher Blütenstand ssebâtta ‫ سباطه‬ssabâtta
ssebâett (Plur.) ‫سبايط‬
gemeinsamer Blütenstiel, Schaft gurbáhh (Ass. ‫ جرباح‬gant
des Blütenstandes Lqs.)
Einzelblüte, Blütenhülle, Perigon qahhf (C.) ‫ قحف‬getmîra
gum (Ros.) ‫جوم‬
gumba (Qor.) ‫جمبه‬
sirr (Ast. Ass.) ‫زر‬
in arabischer in Süd-Algerien
Botanische Definition der Teile in Aegypten
Schrift[34] (Biskra)
Blütenstaub, Pollen daqîq ‫دقيق‬
laqhh (Qor.) ‫لقح‬
einzelner Blütenzweig, schamrûch ‫ شمروخ‬schamrûch
Blütenähre
scharâmich
(Plur.)
Frucht im allgemeinen, Dattel bélahh ‫ بلح‬tamr
tamr ‫تمر‬
Dattel im reifentwickelten, noch bissri, bussri ‫بسري‬
knorpeligfesten Zustande, rot, (Al. Ros.)
gelb oder rotgelb gesprenkelt von
narûss, ‫نروس‬
Farbe
narûtss (Qor.)
Dattel im mürbgewordenen rattb, rottb ‫رطب‬
breiigen (pflaumenartigen)
Reifezustande, blauschwarz,
bräunlich von Farbe
Spätdatteln von Unteraegypten, bélahh-uôchri ‫بلح وخري‬
die sich nicht trocknen lassen (Ast.)
rottb (Al.)
Trockendattel, hartwerdende !tamr ‫! تمر‬tamr chálet (in
Tunesien)
Weichdattel, auch im rttôb (in
getrockneten Zustande Tunesien)
weichbleibend
Quetschdattel, in Massen 'água ‫عجوه‬
zusammengeknetete
Weichdatteln („Dattelkuchen“)
Halbweiche Dattel, mit mqamma' ‫مقمع‬
weichbleibender Spitze, aber (Lqs.)
trockenharter Basis
Dattel, die ohne abzufallen am turfân (C.)
Fruchtbündel reift
in arabischer in Süd-Algerien
Botanische Definition der Teile in Aegypten
Schrift[34] (Biskra)
Wachsreif auf den Blättern, pruina minn (Ast.) ‫من‬
(auch für Blattläuse gebr.)
bajâdd (Lqs.) ‫بياض‬
Schnitt und Schnittfläche beim termísse (C.)
Abtrennen des Basalsprosses
vom Mutterstamm
Dattel, als Frucht einer aus Samen mégahl (Qor.) ‫مجاهل‬
gezogenen Palme
megâhel (Ros.)
Unbefruchtet gebliebene fátss (Al. Ros. ‫فص‬
Frucht, mit drei Karpellen Qor.)
ssîss ‫سيس‬
tssîtss (Lqs. ‫صيص‬
Qn. Ass.)
barûk (Ast.) ‫بروك‬
abfallende Frucht, unentwickelte, níni ‫ نينى‬bessêss
kleine von Erbsengröße
unreife Frucht, von Bohnengröße râmech ‫ رامخ‬lulu
unreife Frucht, noch grün, aber narêch (Lqs.) ‫ نريخ‬blahh, bessêr
schon genießbar
Steinkern naúa ‫ ناوا‬nauaîje
nauâje, nouaîje ‫نوايه‬
fássa (Ast.)
Embryogrube am Steinkern noqtta ‫نقطه‬
Häutchen, das den Steinkern gullâfa
umhüllt, häutiges Endokarp.
(qattmîr ‫ قطمير‬des Qorân, Sure gullâfa-en-
35, V. 14) nouaîje (Al.)
[34]Bezieht sich nur auf die in Aegypten gehörten
Bezeichnungen.
B. GEGENSTÄNDE, WERKZEUGE, VERFAHRUNGSWEISEN,
DIE BEI DER KULTUR DER DATELPALME IN AEGYPTEN VERWENDUNG FINDEN

Jahresschnitt der Blätter, zum Entfernen taqlîm (Qor.) ‫تقليم‬


einer Jahresstufe oder Spirale (dôr)
Senker (Margotte), Erneuerung des Stammes tarqîd (Lqs.) ‫ترقيد‬
durch künstlich veranlaßte Wurzelbildung in
seinem oberen Teil
Beugen und Stützen der weiblichen dinaúe ‫دناوه‬
Blütenstände bei vorschreitender Fruchtreife
jochartige Gabelstütze aus zwei schêba' ‫شبع‬
zusammengebundenen Blattrippen (gerîd)
hergestellt, die man gegen den Stamm
stemmt, um den Schaft des Fruchtbündels
(gurbáhh) zu entlasten
bestäuben der weiblichen Blüte leqqhh ‫لقح‬
Bestäubungsakt talqîhh (Ass.) ‫تلقيح‬
Stab, vermittelst dessen die männlichen leqqhhaíe ‫لقحايه‬
Blütenähren zwischen die weiblichen
hineingeschoben werden
Dattelernte ttarhh (Lqs.) ‫طرحه‬
Gurt mit Schlinge aus Dattelbast zum mattla' ‫مطلع‬
Erklimmen der Palmstämme
Sockel, Schwelle aus geschlagener Erde oder tssalaía (Ros.) ‫صاليه‬
Luftziegel, um die Basis eines alten
temkîl-en-
Palmstammes herum angelegt, um den
nachle
Wurzeln neuen Halt zu gewähren
!mátss.ttaba ‫مصطبه‬
(Ast.)
matsslája ‫مصاليه‬
(Ros.)
dukkân (in
Tunesien)
Tüte, aus Palmblättern geflochten, zum qurúje (Lqs. ‫قرويه‬
Einsammeln von Datteln, die man mit der Qn.)
Hand vom Fruchtbündel ablöst
Korb, großer, aus Palmblättern geflochten, mit qóffa, qúffa ‫قفه‬
zwei Henkeln von Palmbast
qufêf (Plur.) ‫قفف‬
Korb, kleiner, wie der vorige und auch mit zwei máqttaf ‫مقطف‬
Henkeln
Korb, sehr kleiner, von der gleichen 'elláqe, 'îlláqe ‫عالقه‬
Beschaffenheit
Henkel am Korb uudn ‫ودن‬
uudên ‫ودين‬
Matte aus Dattelpalmblättern geflochten, zum birsch, bursch ‫بورش‬
Trocknen der auf ihr ausgebreiteten Datteln
Matte aus Typha (burdi) zum Schutz der mit ihr kejâb,
umhüllten jungen und neuausgepflanzten
kijâb-burdi ‫كياب بردى‬
Palmen
(Ros.)
hölzerner Klöpfel zum Zerfasern der deqâqa (Qn.) ‫دقاقه‬
Palmblätter und Fruchtzweige, behufs
madéqqa (Ast. ‫مدقه‬
Herstellung von Stricken
Lqs.)
Beil, Axt, zum Abhacken der Blattscheiden fâss (Ast.) ‫فاس‬
(kurnâf)
baltta (C.) ‫بلطه‬
Hacke zum Bearbeiten des Bodens ttória (Ast.) ‫طوريه‬
breite Hacke zum Sandausschadfeln in den máshha (Ros.) ‫مزحه‬
Dünen
Doppelhacke zum Bearbeiten des Bodens qaddûm (C.) ‫قدوم‬
scharch (Ast.) ‫شرخ‬
sichelartiges Sägemesser zum Abschneiden míngal ‫منجل‬
der Blattrippen
großes sichelförmig gekrümmtes Messer hilâl (Ast.) ‫هالل‬
mit 40 cm langer Schneide
großer Meißel, über 1 m lang, zum Abtrennen hhadîd-en- ‫حديد النقايل‬
des Basalsprosses vom Stamm (ein ähnliches neqeîel (Qor.
Instrument wird nach J. Hess in Zentralarabien C.)
verwandt und heißt dort „hîm“ ‫)هيم‬
meißelartiger Pflanzenstecher mit Holzgriff, schúqruf (Ast. ‫شقرف‬
zum Gäten des Unkrauts, 30 cm lang Lqs.)
Messer mit gekrümmter, einzuklappender mahhásch ‫محش‬
Schneide (Ast.)
langgestieltes Messer, aus einem Stück, mit messeíef (Ast.) ‫مسيف‬
horizontal gestellten Schneidenteil, 40 cm
lang, zum Abschneiden sowohl der grünen
Blattrippen (gerîd) als auch der trockenen
Blattscheiden (kurnâf). Es gleicht in seiner gedîeh (Ros.)
Gestaltung dem Huf- oder Wirkmesser der
Hufschmiede
Doppelhacke, Hackenbeil, mit 60 cm langem qésme (Ast.)
Eisenteil, zum Abtrennen und Ausgraben der
Basalsprossen
Anmerkungen zur Transkription

Das Umschlagbild wurde vom Bearbeiter gestaltet und in die Public Domain
eingebracht.

Die folgenden Druckfehler und sonstigen Fehler wurden korrigiert

S. 3 „(Gummi)“ und „(Frucht)“ Namen für Acacia arabica und Acacia Seyal
wurden wie anderswo zwischen den Spalten neu geordnet.
S. 4 Die „(Blüte)“ Name für Albizzia Lebbek wurden wie anderswo
zwischen den Spalten neu geordnet.
S. 5 Der von Andropogon Schoenanthus L. und Andropogon Nardus L.
gemeinsame Deskriptor „(Rhizom.)“ wurde am Ende beider Artnamen
platziert.
S. 9 Ballote damascena in: Ballota geändert.
S. 10 Bryonica alba in: Bryonia geändert.
S. 17 Solenostemma Arg. Dne. in: Solenostemma Arg. Hayne geändert.
S. 25 Strychnos Ignatia Berg. in: Ignatii geändert.
S. 28 Lolium rigidum Gand. in: Gaud. geändert.
S. 30 hhabbāss (Nilt. Ob. A. Ssundan-arab.) in: Ssudan-arab geändert.
S. 37 Pluchea Discoridis in: Dioscoridis geändert.
S. 40 Rhus Coriaria in: Rhus Coriaria L. geändert.
S. 42 Sempernivum arboreum in: Sempervivum geändert.
S. 48 Zollikofera spinosa in: Zollikoferia geändert.
S. 52 Bryonica alba in: Bryonia geändert.
S. 53 Solanum villosum L. in: Solanum villosum Lam. geändert.
S. 56 Amberboa tubiflora in: tubuliflora geändert.
S. 57 Convolvulus stachydiformis in: stachydifolius geändert.
S. 63 Aguillaria Agollocha in: Aquilaria Agallocha geändert.
S. 64 Sempernivum arboreum in: Sempervivum geändert.
S. 66 Asphodelus microcarpus Vin. in: Viv. geändert.
S. 67 Echium cericeum V. in: sericeum geändert.
S. 68 Doppelte Zeile: „krumb-bissahra (lib. W. Forsk.) Erucaria crassifolia
D.“ wurde entfernt.
S. 69 Forskali tenacissima in: Forskalia geändert.
S. 70 Petroselinum hortense L. in: Petroselinum hortense Hoffm. geändert.
S. 72 Cardiospermun halicacabum in: Cardiospermum geändert.
S. 72 o ' in: o '‫ ا‬geändert.
S. 74 Pityr. triradiata A. Schf. in: triradiatus geändert.
S. 75 Erythraea pulchella Tr. in: Fr. geändert.
S. 75 Solanum Gilo L. in: Solanum Gilo Raddi geändert.
S. 75 Nympaea (Wurzelstock). in: Nymphaea geändert.
S. 76 Sapindus triphylla in: trifoliatus geändert.
S. 76 Stachus aegyptiaca in: Stachys geändert.
S. 78 Cassia Fustula in: Fistula geändert.
S. 80 Plantanus orientalis in: Platanus geändert.
S. 81 Aspidium filix mas Sm. in: Aspidium filix mas Sw. geändert.
S. 81 Lolium rigidum Gand. in: Gaud. geändert.
S. 82 Imperata cylindria in: cylindrica geändert.
S. 83 Juncus maritimus L. in: Juncus maritimus Lam. geändert.
S. 83 Glyzyrrhiza glabra in: Glycyrrhiza geändert.
S. 84 Tropaeolum majus B. in: Tropaeolum majus L. geändert.
S. 85 Solanum Gilo L. in: Solanum Gilo Raddi geändert.
S. 86 Solanum arabicum Sf. in: Lycium arabicum Sf. geändert.
S. 91 Justicia e) vividis in: viridis geändert.
S. 93 Dilichos d) lubia in: Dolichos geändert.
S. 95 Acacia örfotta in: örfota geändert.
S. 97 556 Ricinus commnunis in: communis geändert.
S. 97 guzar-hendī in: gusar-hendī geändert.
S. 97 gh‫ خ‬in: gh‫ غ‬geändert.
S. 97 Die Zeile für „ghafl“ wurde entfernt und die zugehörige Datenzellen
„143 Rhamnus b) divaricatus s. CVI“ und „Zizyphus spina Christi L.“ mit
„ghassl — Ghasl — Rhamnus nabeca“ (S. 98) zusammengeführt, die als
Zeile direkt darunter eingefügt wurde.
S. 98 var. a. divariacatus in: divaricatus geändert.
S. 98 Ruelliac c) strepens in: Ruellia geändert.
S. 98 s. CVIII u. s. 51 in: u. s. 52 geändert.
S. 102 Solanum h) bahamense s. CVII u. s. 146 in: s. 46 geändert.
S. 104 Cynanchum b) arboreum s. CVIII u. s. 52 in: u. s. 53 geändert.
S. 105 Hibiscus purpurens in: purpureus geändert.
S. 106 Charachera a) terragona in: tetragona geändert.
S. 107 Momordica balsamina c. CXXII in: s. CXXII geändert.
S. 109 Cucumis öllœhie in: öllæhie geändert.
S. 109 Asclepia l) contorta? in: Asclepias geändert.
S. 113 321 Punita granatum in: Punica geändert.
S. 117 Acacia seyjal in: seyal geändert.
S. 121 sem. fulvis. s. CXXXIII in: CXXIII geändert.
S. 122 Maerua oblongifolia L. in: Maerua oblongifolia R. geändert.
S. 128 sem. fulvis. s. CXXXIII in: CXXIII geändert.
S. 132(x2) s. CVIII u. s. 51 in: u. s. 52 geändert.
S. 136 Cucumis öllœhie in: öllæhie geändert.
S. 143 In der Zeile von „hhaschfe“ wurde „Heliotropium bacciferum Forsk.“
in „Heliotropium fruticosum Forsk.“ geändert (seihen S. 100).
S. 145 Kat erraejān in: Kat erraejân geändert.
S. 145 Charachera a) terragona in: tetragona geändert.
S. 146 Cynanchum b) arboreum s. CVIII u. s. 52 in: u. s. 53 geändert.
S. 147 Momordica balsamina c. CXXII in: s. CXXII geändert.
S. 152 Ruelliac c) strepens in: Ruellia geändert.
S. 152 Asclepia l) contorta? in: Asclepias geändert.
S. 155 Solanum h) bahamense s. CVII u. s. 146 in: s. 46 geändert.
S. 157 Dilichos d) lubia in: Dolichos geändert.
S. 157 var. a. divariacatus in: divaricatus geändert.
S. 161 Blastania fimbristipeda in: fimbristipula geändert.
S. 162, 180, 182, 184 u. 185 Cadia varia W. in: Cadia varia l'Her. geändert.
S. 162 dabba-el-hind (W.) dubbe-el-hind, in: dabba-el-hind, dubbe-el-hind
(W.) geändert.
S. 169 Panicum turgidum in: Panicum turgidum Forsk. geändert.
S. 170 Rotboellia exalata in: exaltata geändert.
S. 171 Scabiosa columnaria L. in: columbaria geändert.
S. 174 Plectranthus cylindraceus L. in: Plectranthus cylindraceus H.
geändert.
S. 174 Zizyphus mucronatus in: mucronata geändert.
S. 183 Rhoicissus yemensis in: jemensis geändert.
S. 183 Asplenum praemorsum in: Asplenium geändert.
S. 184 Zizyphus mucronatus in: mucronata geändert.
S. 184 Rotboellia exalata in: exaltata geändert.
S. 185 Punica granatum in: Punica granatum L. geändert.
S. 187 Heteromorpha aborescens in: arborescens geändert.
S. 188 Rhoicissus yemensis in: jemensis geändert.
S. 188 Zizyphus micronata in: mucronata geändert.
S. 190 Scabiosa columnaria L. in: columbaria geändert.
S. 192 Echinopsilon (Kochia) muricatum L. in: Echinopsilon (Kochia)
muricatum Moq. geändert.
S. 194 Opuntia Ficus indica Han. in: Opuntia Ficus indica Haw. geändert.
S. 195 hhommēdda in: hhommēdda (D.) geändert.
S. 196 o ' in: o '‫ ا‬geändert.
S. 197 Euphorbia glebulosa in: globulosa geändert.
S. 198 Opuntia Ficus indica Han. in: Opuntia Ficus indica Haw. geändert.
S. 198 Sciopus littorali in: Scirpus littoralis geändert.
S. 199 Anabis articulata Mq. T. in: Anabasis geändert.
S. 199 In der Zeile von „karáfssa (Sch.)“ wurde „Anethum Graveolens“ in
„Apium Graveolens“ geändert (seihen S. 195).
S. 200 Centaurea omphalostricha in: omphalotricha geändert.
S. 200 Chrysanthemum fascatum in: fuscatum geändert.
S. 200 Cressia cretica in: Cressa geändert.
S. 201 Echinopsilon (Kochia) nuricatum in: muricatum geändert.
S. 201 Euphorbia glebulosa in: globulosa geändert.
S. 201 !tésselgha (I.) in: !tésselgha (Is.) geändert.
S. 203 ferrāg (Ss.) in: ferrāg (Is.) geändert.
S. 203 dhanūn (F. A. Js.) in: dhanūn (F. A. Is.) geändert.
S. 203 (Reichardtia) in: Reichardia geändert.
S. 204 Raphanus sativus Coss. in: Raphanus sativus L. geändert.
S. 206 Zollikoferia residifolia in: resedifolia geändert.
S. 207 a ' in: a '‫ ا‬geändert.
S. 211 kelch (B. H-M.) ‫ كلج‬in: ‫ كلخ‬geändert.
S. 211 Chrysanthemum Clausonis Poir. in: Chrysanthemum Clausonis Pom.
geändert.
S. 212 ‫ مرطر‬in: ‫ موطر‬geändert.
S. 214 Thymus serphyllum in: serpyllum geändert.
S. 214 Osyris alba Lois. in: Osyris alba L. geändert.
S. 216 Chrysanthemum Clausonis Poir. in: Chrysanthemum Clausonis Pom.
geändert.
S. 220 kelch (B. H-M.) ‫ كلج‬in: ‫ كلخ‬geändert.
S. 221 In der Zeile von „scherraíeq (H-M.)“ wurde „Iris Pseudacorus L.“ in
„Iris Sisyrynchium L.“ geändert (seihen S. 215).
S. 222 In der Zeile von „sebūg (B.)“ wurde „Olea europaea L.“ in „Olea
europaea L. f. oleaster“ geändert (seihen S. 214).
S. 224 ‫ بلع الرنيس‬in: ‫ بلغ الرنيس‬geändert.
S. 224 Thymus serphyllum in: serpyllum geändert.
S. 228 ‫ نقيله االوبله‬in: ‫ نقيله االويله‬geändert.

Die wenigen „langen S-Form Kāf“ ‫ ڪ‬wurden als Kāf ‫ ك‬transkribiert.

Die Schreibweise von Gattungen und Arten-Epitheton wurde gemäß dem


International Plant Names Index (2023) standardisiert. „Gracillaria“ wurde laut
AlgaeBase (2023) in „Gracilaria“ geändert. Die Spalte „botanische Bezeichnung
nach Forskål“ in Ab. II wurde nicht geändert. Die Groß- und Kleinschreibung von
Taxonnamen wurde unverändert gelassen.
Die in der Mitte des Taxonnamen enthaltenen Synonyme wurden an das
Ende des Taxonnamen verschoben. Den Synonymen, denen eines fehlte, wurde
ein „=“ vorangestellt.
Die Standardisierungsänderungen sind in den folgenden Tabellen aufgeführt.
Wenn die standardisierte Gattung auf einer anderen Seite einer alphabetischen
Tabelle platziert werden musste, wird dies in Klammern angegeben.
Gattung (od. Gattung u. Art-Epitheton)
gedruckten standardisiert Seiten
Actinopteris Actiniopteris 106, 123, 126
Agropyrum Agropyron 4, 82
Albizzia lebbek Albizia lebbeck 4, 58, 68
Aloexylon Aloexylum 5, 17
Amarantus Amaranthus 5, 69, 73, 88, 114, 115, 127
Ammania Ammannia 5, 76
Ammomum Amomum 5, 64, 73
Anarhinum Anarrhinum 120, 128
Anona Annona 6, 75, 118, 128, 160, 174, 176,
187
Arisæma Arisaema 94, 128
Balsamodendron Balsamodendrum 9
Boerhaavia Boerhavia 9, 70, 91, 92, 109, 123, 130, 161,
176, 180, 185
Borrago Borago 9, 69
Briedelia Bridelia 161, 177, 182
Buddleya Buddleja 161, 174
Calanchoe, Kalanchoe 10 (27), 131 (145), 162 (167)
Calenchoe
Caraluma Caralluma 92, 98, 132, 162, 177, 187
Cardopathium Cardopatium 213, 215, 218
Caylusia Caylusea 12, 58, 62
Cephaëlis Cephaelis 12
Cluytia Clutia 163, 177, 187
Crozophora Chrozophora 16 (12), 72, 75, 99, 136 (134),
164 (162), 188
Cyamopis Cyamopsis 164, 179
Dinæba Dinebra 18, 54
Diospyrus Diospyros 91, 135, 165, 175
Gattung (od. Gattung u. Art-Epitheton)
gedruckten standardisiert Seiten
Exogonum Exogonium 21, 26, 60
Flemmingia Flemingia 118, 141
Fleyria Fleurya 106, 141
Flueggia Flueggea 100, 141, 165, 181
Forskalea, Forskalia Forsskaolea 22, 68, 69, 100, 141, 165, 182,
195, 201
Gracillaria Gracilaria 141
Guajacum Guaiacum 23, 56
Gymnocarpum, Gymnocarpos 23, 60, 61, 83, 97, 118, 142, 194,
Gymnocarpus 201
Haloxylum Haloxylon 194, 202
Henophytum Henophyton 194, 202
Heurnia Huernia 143, 166, 177
Hypoëstes Hypoestes paniculata 166, 183, 187
panniculata
Iphione Iphiona 26, 58, 77
Jonidium Ionidium 167, 179, 188
Jussieua Jussiaea 26, 70, 71, 74
Launea Launaea 27, 99, 107, 145
Lycopersicum Lycopersicon 29, 43, 54, 75, 84, 167, 189
Mesembrianthemum Mesembryanthemum 30, 61, 71, 81, 82, 85
Nonnaea Nonea 212, 222
Onopordon Onopordum 32, 80, 213, 222
Ormocarpon Ormocarpum 168, 180
Osiris Osyris 169, 174, 189
Pedicillaria Pedicellaria 169, 176, 183
Periderea Perideraea 197, 198, 203
Phasaeolus Phaseolus 35, 50, 60, 69, 111, 112, 149,
169, 184, 185
Phytolaca Phytolacca 207, 222
Gattung (od. Gattung u. Art-Epitheton)
gedruckten standardisiert Seiten
Pirus Pyrus 36 (39), 68, 84, 169 (170), 174,
171, 188, 191, 198, 203 (204),
211, 222 (223)
Pistiia Pistia 50
Pityranthus, Pityr. Pituranthos, Pitur. 18, 36, 54, 74, 81, 83
Polycarpia Polycarpaea 37, 70
Pouzolsia Pouzolzia 108, 150
Rhantherium Rhanterium 191, 204
Rotboellia Rottboellia 170, 184
Sanseviera Sansevieria 171, 177, 180, 186
Sasafras Sassafras 41, 81
Schouvia Schouwia 90, 153
Stupa Stipa 44, 55, 215, 224
Uragoa Uragoga 12, 46, 59
Uropetalum Uropetalon 47
Zizyphus Ziziphus mehrere seiten

Art-Epitheton
gedruckten standardisiert Seiten
Acacia orfota, A. oerfota 94, 95, 109, 125, 159, 184
örfota
Adiantum capillus capillus-veneris 4, 68, 115, 126
veneris
Adonis microcarpus microcarpa 4, 77
Alhagi manniferum mannifera 4, 52
Allophylus rubiifolius rubifolius 160, 183
Aloe vaccillans vacillans 91, 127, 160, 176
Andropogon halepensis 199
halepense
Andropogon ramosus 89, 128
Art-Epitheton
gedruckten standardisiert Seiten
ramosum
Artemisia herba alba herba-alba 7, 79, 198, 199
Astragalus gomba gombo 198, 199
Astragalus gummifer gummifera 8, 67
Atriplex leucocladus leucoclada 9, 55, 76
Atriplex parvifolius parvifolia 197, 199
Blepharis boerhaviifolia 116, 130
boerhaaviaefolia
Breweria oxyacarpa oxycarpa 161, 169
Chrysanthemum deserticola 191, 200
deserticolum
Cissus digitatus, C. digitata, rotundifolia, 100, 101, 134, 162, 177, 180
rotundifolius, C. ternata
ternatus
Cistus salviaefolius salviifolius 212, 218
Clitoria ternateja ternatea 163, 179, 183
Coccinia moghad moghadd 107, 135, 163, 178, 180, 182
coerulea, caerulea, 32, 34, 55, 79, 208, 209, 214,
coerulescens, caerulescens, 215, 217, 222, 224
coeruleum caeruleum
Crepis rüppellii rueppellii 163, 178
Croton tigilium tiglium 16, 64
Crypsis schoenoïdes schoenoides 16
Dactyloctenium aegyptiacum 18, 71
ægyptiacum
Donax arundinacea arundinaceus 18
Echinopsilon muricatus 19, 192, 201
muricatum
Emex spinosus spinosa 19, 54, 59, 63, 68, 76, 79
erythræum erythraeum 18, 55
Art-Epitheton
gedruckten standardisiert Seiten
Erodium bryoniifolium 20, 57
bryoniaefolium
Euphorbia scordifolia scordiifolia 113, 140
Ferula asa foetida asafoetida 21, 63
Ficaria calthaefolia calthifolia 216, 220
filix mas filix-mas 8, 31, 81
Flacourtia catafracta cataphracta 22, 71
Helianthemum Sancti Sancti-Antoni 60, 24
Antonii
Heliotropium arbainense 76, 24
arbaïnense
Hordeum hexastichon 115, 143
hexastichum
Ipomoea caïrica cairica 26, 82
jalappa jalapa 26, 31, 66, 72, 79
Lablab vulgare vulgaris 196, 202
Lantana salviaefolia, salviifolia 167, 180, 186
L. salvifolia
Melia azederach azedarach 30, 77
Mentha silvestris sylvestris 30, 62, 168, 183
monoeca, dioeca monoica, dioica 36, 44, 53, 80
Muscari commosum comosum 208, 221
Narcissus tazzetta tazetta 31, 71
Ocimum menthifolium 168, 179, 190
menthaefolium
Onobrychis crista crista-galli 32, 82
galli
Panicum crus galli crus-galli 33, 56, 58, 71, 72
Penicillaria plukenetii 35
pluckenetii
Pennisetum rüppellii ruppellii 169, 179, 180, 186
Art-Epitheton
gedruckten standardisiert Seiten
Plantago crypsioides crypsoides 37, 58
Plumbago ceylanica zeylanica 100, 150
Polygonum bellardi bellardii 37, 70, 73, 75
polyrrhiza polyrhiza 28, 44, 51
Rapistrum linneanum linnaeanum 204
Sarcostemma forskaolianum 92, 102, 107, 109, 112, 152
forskalli, S.
forskalei, S.
forskalianum
(Non Sarcostemma) forsskalii mehrere seiten
forskalei,
forskahlei, forskalii
Scandix pecten pecten-veneris 212, 224
veneris
Scirpus littoralis litoralis 80, 198, 204
Scorpiurus muricata muricatus 215, 224
Selaginella yemense yemensis 153
Sideroxylon oxyacanthum 96, 122, 154
oxyacantha
Smyrnium olus atrum olusatrum 210, 211, 215, 224
Solanum sepicola sepicula 90, 99, 102, 106, 155
Solenostemma argel arghel 43, 64
Sporobolus coromandelianus 119, 155
coromandelinus
Statice thouini thouinii 192, 205
Strychnos nux nux-vomica 44, 62
vomica
Tagetes erectus erecta 108, 112, 155, 172, 185
Tamarix brachystilis brachystylis 198, 205
Terminalia brownei brownii 172, 184
Trianthema monogynum 172, 185
Art-Epitheton
gedruckten standardisiert Seiten
monogyna
Trianthema pentandrum 113, 156
pentandra
Trigonella foenum foenum-graecum 46, 65, 101, 156, 172, 180
graecum
Veronica anagallis anagallis-aquatica 47, 63
aquatica
Zizyphus spina christi spina-christi 48, 71, 82, 88, 95, 98, 118, 123,
157, 173, 178, 188, 198, 205,
209, 225
Um diesen Änderungen zu entsprechen, wurde die Zeile „Pirus = Pyrus“ in
„Pyrus = Pirus“ geändert (S. 36, 39).
*** END OF THE PROJECT GUTENBERG EBOOK ARABISCHE
PFLANZENNAMEN AUS AEGYPTEN, ALGERIEN UND JEMEN ***

Updated editions will replace the previous one—the old editions will
be renamed.

Creating the works from print editions not protected by U.S.


copyright law means that no one owns a United States copyright in
these works, so the Foundation (and you!) can copy and distribute it
in the United States without permission and without paying
copyright royalties. Special rules, set forth in the General Terms of
Use part of this license, apply to copying and distributing Project
Gutenberg™ electronic works to protect the PROJECT GUTENBERG™
concept and trademark. Project Gutenberg is a registered trademark,
and may not be used if you charge for an eBook, except by following
the terms of the trademark license, including paying royalties for use
of the Project Gutenberg trademark. If you do not charge anything
for copies of this eBook, complying with the trademark license is
very easy. You may use this eBook for nearly any purpose such as
creation of derivative works, reports, performances and research.
Project Gutenberg eBooks may be modified and printed and given
away—you may do practically ANYTHING in the United States with
eBooks not protected by U.S. copyright law. Redistribution is subject
to the trademark license, especially commercial redistribution.

START: FULL LICENSE


THE FULL PROJECT GUTENBERG LICENSE
PLEASE READ THIS BEFORE YOU DISTRIBUTE OR USE THIS WORK

To protect the Project Gutenberg™ mission of promoting the free


distribution of electronic works, by using or distributing this work (or
any other work associated in any way with the phrase “Project
Gutenberg”), you agree to comply with all the terms of the Full
Project Gutenberg™ License available with this file or online at
www.gutenberg.org/license.

Section 1. General Terms of Use and


Redistributing Project Gutenberg™
electronic works
1.A. By reading or using any part of this Project Gutenberg™
electronic work, you indicate that you have read, understand, agree
to and accept all the terms of this license and intellectual property
(trademark/copyright) agreement. If you do not agree to abide by all
the terms of this agreement, you must cease using and return or
destroy all copies of Project Gutenberg™ electronic works in your
possession. If you paid a fee for obtaining a copy of or access to a
Project Gutenberg™ electronic work and you do not agree to be
bound by the terms of this agreement, you may obtain a refund
from the person or entity to whom you paid the fee as set forth in
paragraph 1.E.8.

1.B. “Project Gutenberg” is a registered trademark. It may only be


used on or associated in any way with an electronic work by people
who agree to be bound by the terms of this agreement. There are a
few things that you can do with most Project Gutenberg™ electronic
works even without complying with the full terms of this agreement.
See paragraph 1.C below. There are a lot of things you can do with
Project Gutenberg™ electronic works if you follow the terms of this
agreement and help preserve free future access to Project
Gutenberg™ electronic works. See paragraph 1.E below.
1.C. The Project Gutenberg Literary Archive Foundation (“the
Foundation” or PGLAF), owns a compilation copyright in the
collection of Project Gutenberg™ electronic works. Nearly all the
individual works in the collection are in the public domain in the
United States. If an individual work is unprotected by copyright law
in the United States and you are located in the United States, we do
not claim a right to prevent you from copying, distributing,
performing, displaying or creating derivative works based on the
work as long as all references to Project Gutenberg are removed. Of
course, we hope that you will support the Project Gutenberg™
mission of promoting free access to electronic works by freely
sharing Project Gutenberg™ works in compliance with the terms of
this agreement for keeping the Project Gutenberg™ name associated
with the work. You can easily comply with the terms of this
agreement by keeping this work in the same format with its attached
full Project Gutenberg™ License when you share it without charge
with others.

1.D. The copyright laws of the place where you are located also
govern what you can do with this work. Copyright laws in most
countries are in a constant state of change. If you are outside the
United States, check the laws of your country in addition to the
terms of this agreement before downloading, copying, displaying,
performing, distributing or creating derivative works based on this
work or any other Project Gutenberg™ work. The Foundation makes
no representations concerning the copyright status of any work in
any country other than the United States.

1.E. Unless you have removed all references to Project Gutenberg:

1.E.1. The following sentence, with active links to, or other


immediate access to, the full Project Gutenberg™ License must
appear prominently whenever any copy of a Project Gutenberg™
work (any work on which the phrase “Project Gutenberg” appears,
or with which the phrase “Project Gutenberg” is associated) is
accessed, displayed, performed, viewed, copied or distributed:
This eBook is for the use of anyone anywhere in the United
States and most other parts of the world at no cost and with
almost no restrictions whatsoever. You may copy it, give it away
or re-use it under the terms of the Project Gutenberg License
included with this eBook or online at www.gutenberg.org. If you
are not located in the United States, you will have to check the
laws of the country where you are located before using this
eBook.

1.E.2. If an individual Project Gutenberg™ electronic work is derived


from texts not protected by U.S. copyright law (does not contain a
notice indicating that it is posted with permission of the copyright
holder), the work can be copied and distributed to anyone in the
United States without paying any fees or charges. If you are
redistributing or providing access to a work with the phrase “Project
Gutenberg” associated with or appearing on the work, you must
comply either with the requirements of paragraphs 1.E.1 through
1.E.7 or obtain permission for the use of the work and the Project
Gutenberg™ trademark as set forth in paragraphs 1.E.8 or 1.E.9.

1.E.3. If an individual Project Gutenberg™ electronic work is posted


with the permission of the copyright holder, your use and distribution
must comply with both paragraphs 1.E.1 through 1.E.7 and any
additional terms imposed by the copyright holder. Additional terms
will be linked to the Project Gutenberg™ License for all works posted
with the permission of the copyright holder found at the beginning
of this work.

1.E.4. Do not unlink or detach or remove the full Project


Gutenberg™ License terms from this work, or any files containing a
part of this work or any other work associated with Project
Gutenberg™.

1.E.5. Do not copy, display, perform, distribute or redistribute this


electronic work, or any part of this electronic work, without
prominently displaying the sentence set forth in paragraph 1.E.1
with active links or immediate access to the full terms of the Project
Gutenberg™ License.

1.E.6. You may convert to and distribute this work in any binary,
compressed, marked up, nonproprietary or proprietary form,
including any word processing or hypertext form. However, if you
provide access to or distribute copies of a Project Gutenberg™ work
in a format other than “Plain Vanilla ASCII” or other format used in
the official version posted on the official Project Gutenberg™ website
(www.gutenberg.org), you must, at no additional cost, fee or
expense to the user, provide a copy, a means of exporting a copy, or
a means of obtaining a copy upon request, of the work in its original
“Plain Vanilla ASCII” or other form. Any alternate format must
include the full Project Gutenberg™ License as specified in
paragraph 1.E.1.

1.E.7. Do not charge a fee for access to, viewing, displaying,


performing, copying or distributing any Project Gutenberg™ works
unless you comply with paragraph 1.E.8 or 1.E.9.

1.E.8. You may charge a reasonable fee for copies of or providing


access to or distributing Project Gutenberg™ electronic works
provided that:

• You pay a royalty fee of 20% of the gross profits you derive
from the use of Project Gutenberg™ works calculated using the
method you already use to calculate your applicable taxes. The
fee is owed to the owner of the Project Gutenberg™ trademark,
but he has agreed to donate royalties under this paragraph to
the Project Gutenberg Literary Archive Foundation. Royalty
payments must be paid within 60 days following each date on
which you prepare (or are legally required to prepare) your
periodic tax returns. Royalty payments should be clearly marked
as such and sent to the Project Gutenberg Literary Archive
Foundation at the address specified in Section 4, “Information
about donations to the Project Gutenberg Literary Archive
Foundation.”

• You provide a full refund of any money paid by a user who


notifies you in writing (or by e-mail) within 30 days of receipt
that s/he does not agree to the terms of the full Project
Gutenberg™ License. You must require such a user to return or
destroy all copies of the works possessed in a physical medium
and discontinue all use of and all access to other copies of
Project Gutenberg™ works.

• You provide, in accordance with paragraph 1.F.3, a full refund of


any money paid for a work or a replacement copy, if a defect in
the electronic work is discovered and reported to you within 90
days of receipt of the work.

• You comply with all other terms of this agreement for free
distribution of Project Gutenberg™ works.

1.E.9. If you wish to charge a fee or distribute a Project Gutenberg™


electronic work or group of works on different terms than are set
forth in this agreement, you must obtain permission in writing from
the Project Gutenberg Literary Archive Foundation, the manager of
the Project Gutenberg™ trademark. Contact the Foundation as set
forth in Section 3 below.

1.F.

1.F.1. Project Gutenberg volunteers and employees expend


considerable effort to identify, do copyright research on, transcribe
and proofread works not protected by U.S. copyright law in creating
the Project Gutenberg™ collection. Despite these efforts, Project
Gutenberg™ electronic works, and the medium on which they may
be stored, may contain “Defects,” such as, but not limited to,
incomplete, inaccurate or corrupt data, transcription errors, a
copyright or other intellectual property infringement, a defective or
damaged disk or other medium, a computer virus, or computer
codes that damage or cannot be read by your equipment.

1.F.2. LIMITED WARRANTY, DISCLAIMER OF DAMAGES - Except for


the “Right of Replacement or Refund” described in paragraph 1.F.3,
the Project Gutenberg Literary Archive Foundation, the owner of the
Project Gutenberg™ trademark, and any other party distributing a
Project Gutenberg™ electronic work under this agreement, disclaim
all liability to you for damages, costs and expenses, including legal
fees. YOU AGREE THAT YOU HAVE NO REMEDIES FOR
NEGLIGENCE, STRICT LIABILITY, BREACH OF WARRANTY OR
BREACH OF CONTRACT EXCEPT THOSE PROVIDED IN PARAGRAPH
1.F.3. YOU AGREE THAT THE FOUNDATION, THE TRADEMARK
OWNER, AND ANY DISTRIBUTOR UNDER THIS AGREEMENT WILL
NOT BE LIABLE TO YOU FOR ACTUAL, DIRECT, INDIRECT,
CONSEQUENTIAL, PUNITIVE OR INCIDENTAL DAMAGES EVEN IF
YOU GIVE NOTICE OF THE POSSIBILITY OF SUCH DAMAGE.

1.F.3. LIMITED RIGHT OF REPLACEMENT OR REFUND - If you


discover a defect in this electronic work within 90 days of receiving
it, you can receive a refund of the money (if any) you paid for it by
sending a written explanation to the person you received the work
from. If you received the work on a physical medium, you must
return the medium with your written explanation. The person or
entity that provided you with the defective work may elect to provide
a replacement copy in lieu of a refund. If you received the work
electronically, the person or entity providing it to you may choose to
give you a second opportunity to receive the work electronically in
lieu of a refund. If the second copy is also defective, you may
demand a refund in writing without further opportunities to fix the
problem.

1.F.4. Except for the limited right of replacement or refund set forth
in paragraph 1.F.3, this work is provided to you ‘AS-IS’, WITH NO
OTHER WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR ANY PURPOSE.

1.F.5. Some states do not allow disclaimers of certain implied


warranties or the exclusion or limitation of certain types of damages.
If any disclaimer or limitation set forth in this agreement violates the
law of the state applicable to this agreement, the agreement shall be
interpreted to make the maximum disclaimer or limitation permitted
by the applicable state law. The invalidity or unenforceability of any
provision of this agreement shall not void the remaining provisions.

1.F.6. INDEMNITY - You agree to indemnify and hold the Foundation,


the trademark owner, any agent or employee of the Foundation,
anyone providing copies of Project Gutenberg™ electronic works in
accordance with this agreement, and any volunteers associated with
the production, promotion and distribution of Project Gutenberg™
electronic works, harmless from all liability, costs and expenses,
including legal fees, that arise directly or indirectly from any of the
following which you do or cause to occur: (a) distribution of this or
any Project Gutenberg™ work, (b) alteration, modification, or
additions or deletions to any Project Gutenberg™ work, and (c) any
Defect you cause.

Section 2. Information about the Mission


of Project Gutenberg™
Project Gutenberg™ is synonymous with the free distribution of
electronic works in formats readable by the widest variety of
computers including obsolete, old, middle-aged and new computers.
It exists because of the efforts of hundreds of volunteers and
donations from people in all walks of life.

Volunteers and financial support to provide volunteers with the


assistance they need are critical to reaching Project Gutenberg™’s
goals and ensuring that the Project Gutenberg™ collection will
remain freely available for generations to come. In 2001, the Project
Gutenberg Literary Archive Foundation was created to provide a
secure and permanent future for Project Gutenberg™ and future
generations. To learn more about the Project Gutenberg Literary
Archive Foundation and how your efforts and donations can help,
see Sections 3 and 4 and the Foundation information page at
www.gutenberg.org.

Section 3. Information about the Project


Gutenberg Literary Archive Foundation
The Project Gutenberg Literary Archive Foundation is a non-profit
501(c)(3) educational corporation organized under the laws of the
state of Mississippi and granted tax exempt status by the Internal
Revenue Service. The Foundation’s EIN or federal tax identification
number is 64-6221541. Contributions to the Project Gutenberg
Literary Archive Foundation are tax deductible to the full extent
permitted by U.S. federal laws and your state’s laws.

The Foundation’s business office is located at 809 North 1500 West,


Salt Lake City, UT 84116, (801) 596-1887. Email contact links and up
to date contact information can be found at the Foundation’s website
and official page at www.gutenberg.org/contact

Section 4. Information about Donations to


the Project Gutenberg Literary Archive
Foundation
Project Gutenberg™ depends upon and cannot survive without
widespread public support and donations to carry out its mission of
increasing the number of public domain and licensed works that can
be freely distributed in machine-readable form accessible by the
widest array of equipment including outdated equipment. Many
small donations ($1 to $5,000) are particularly important to
maintaining tax exempt status with the IRS.

The Foundation is committed to complying with the laws regulating


charities and charitable donations in all 50 states of the United
States. Compliance requirements are not uniform and it takes a
considerable effort, much paperwork and many fees to meet and
keep up with these requirements. We do not solicit donations in
locations where we have not received written confirmation of
compliance. To SEND DONATIONS or determine the status of
compliance for any particular state visit www.gutenberg.org/donate.

While we cannot and do not solicit contributions from states where


we have not met the solicitation requirements, we know of no
prohibition against accepting unsolicited donations from donors in
such states who approach us with offers to donate.

International donations are gratefully accepted, but we cannot make


any statements concerning tax treatment of donations received from
outside the United States. U.S. laws alone swamp our small staff.

Please check the Project Gutenberg web pages for current donation
methods and addresses. Donations are accepted in a number of
other ways including checks, online payments and credit card
donations. To donate, please visit: www.gutenberg.org/donate.

Section 5. General Information About


Project Gutenberg™ electronic works
Professor Michael S. Hart was the originator of the Project
Gutenberg™ concept of a library of electronic works that could be
freely shared with anyone. For forty years, he produced and
distributed Project Gutenberg™ eBooks with only a loose network of
volunteer support.
Project Gutenberg™ eBooks are often created from several printed
editions, all of which are confirmed as not protected by copyright in
the U.S. unless a copyright notice is included. Thus, we do not
necessarily keep eBooks in compliance with any particular paper
edition.

Most people start at our website which has the main PG search
facility: www.gutenberg.org.

This website includes information about Project Gutenberg™,


including how to make donations to the Project Gutenberg Literary
Archive Foundation, how to help produce our new eBooks, and how
to subscribe to our email newsletter to hear about new eBooks.
Welcome to our website – the ideal destination for book lovers and
knowledge seekers. With a mission to inspire endlessly, we offer a
vast collection of books, ranging from classic literary works to
specialized publications, self-development books, and children's
literature. Each book is a new journey of discovery, expanding
knowledge and enriching the soul of the reade

Our website is not just a platform for buying books, but a bridge
connecting readers to the timeless values of culture and wisdom. With
an elegant, user-friendly interface and an intelligent search system,
we are committed to providing a quick and convenient shopping
experience. Additionally, our special promotions and home delivery
services ensure that you save time and fully enjoy the joy of reading.

Let us accompany you on the journey of exploring knowledge and


personal growth!

textbookfull.com

You might also like