From Baghdad to Latin Europe: Algorism, Algebra, and the Reception of Algorithmic Reasoning

Last Updated June 23, 2026

From Baghdad to Latin Europe: Algorism, Algebra, and Reception examines how computational methods associated with Arabic mathematical traditions entered Latin scholarly, commercial, educational, and institutional worlds. This article follows the movement of procedures rather than a single heroic origin story. It traces how Hindu-Arabic numerals, place-value calculation, algorism, algebraic problem solving, astronomical tables, commercial arithmetic, and translated mathematical texts became part of Latin Europe’s technical repertoire.

The story begins before Latin Europe. Indian numerals and place-value calculation moved through Arabic mathematical culture. Al-Khwārizmī’s arithmetic and algebraic writings became associated with procedures for calculation and equation solving. Arabic astronomical, mathematical, and commercial practices developed in multiple regions and traditions. Translation movements, manuscript copying, teaching, commentary, merchant practice, and university learning then carried selected methods into Latin contexts.

The word “algorithm” itself carries a memory of this transfer through Latinized forms of al-Khwārizmī’s name. The word “algebra” carries a memory of al-jabr, one of the operations associated with al-Khwārizmī’s algebraic treatise. But reception is more than etymology. It is the process by which methods become usable, teachable, trusted, resisted, revised, and eventually normalized.

This article introduces Baghdad, Latin Europe, algorism, algebra, al-Khwārizmī, Hindu-Arabic numerals, place value, zero, arithmetic procedures, equation solving, Arabic-Latin translation, Toledo, Fibonacci, Liber Abaci, abacus culture, merchant arithmetic, university reception, manuscript transmission, terminology, resistance, standardization, and the long institutional adoption of computational methods. It argues that reception is not passive borrowing. It is a process of translation, adaptation, validation, pedagogy, and social trust.

Why Baghdad to Latin Europe Matters

The movement from Baghdad and broader Arabic scholarly worlds into Latin Europe matters because it shows how procedures become historical infrastructure. A numeral system is not useful merely because it exists. It must be taught, copied, trusted, used in examples, adapted to account books, accepted in schools, and connected to institutions that need calculation.

Algorism and algebra are especially important because they changed how calculation and problem solving could be represented. Algorism made written calculation with place-value numerals increasingly portable. Algebra organized certain problems into rule-governed transformations. Together, they helped shift computational reasoning from local practice into transmissible method.

This movement matters because algorithmic reasoning is not only created; it is received, stabilized, and institutionalized.

Back to top ↑

Algorism as Received Procedure

Algorism refers to procedures for calculation using Hindu-Arabic numerals. In Latin Europe, it became associated with written arithmetic methods that differed from older abacus and counting-board practices. The importance of algorism was not only the numerals themselves, but the procedures attached to them: addition, subtraction, multiplication, division, extraction of roots, handling of fractions, and commercial calculation.

A numeral system becomes computational only when methods are attached to it. The symbols 0 through 9 are not enough. Learners must understand place value, carrying, borrowing, digit position, and the sequence of operations. Algorism is therefore a reception history of procedures.

Algorism was not just a notation; it was a portable arithmetic operating system for written calculation.

Back to top ↑

Algebra as Rule-Governed Problem Solving

Algebra entered Latin Europe as a body of rule-governed problem-solving techniques, not initially as modern symbolic algebra. Early algebraic reasoning often used words, cases, geometric explanations, and worked examples. The key was procedural transformation: reduce a problem to a recognized form, apply a method, produce a result, and verify it.

The Arabic term al-jabr is associated with restoring or completing, while al-muqābalah is associated with balancing or comparison. These operations helped organize equation-solving practices. In Latin reception, algebra became a method for handling unknowns, quantities, debts, inheritances, commercial problems, geometry, and other practical or theoretical questions.

Algebra is a history of formalization before it is a history of symbols.

Back to top ↑

Al-Khwārizmī and the Latin Memory of Method

Al-Khwārizmī’s name became attached in Latin traditions to methods of calculation. Latinized forms such as Algoritmi and related terms eventually contributed to the vocabulary of algorism and later algorithm. This linguistic history matters because it shows how a person’s name became associated with a method, then with a broader class of procedures.

The reception of al-Khwārizmī was not a single direct copy. Texts, adaptations, translations, summaries, and teaching traditions all played a role. Latin readers often encountered Arabic mathematical knowledge through mediated forms. The “memory of method” survived through names, titles, procedures, examples, and scholastic classifications.

Al-Khwārizmī’s Latin reception shows how names, methods, and institutions become intertwined.

Back to top ↑

Numerals, Zero, and Place Value

Hindu-Arabic numerals transformed written calculation because they made position part of meaning. The same digit represents different values depending on its place. Zero preserves empty positions. This structure allows compact notation and systematic operations.

Latin reception of these numerals required more than copying shapes. Readers had to learn how digits behave. They had to trust a symbol for nothing. They had to understand that written positions could replace counters on a board. They had to learn procedures for carrying, borrowing, multiplication, division, and checking.

Place value is not only a notation. It is a computational architecture.

Back to top ↑

Toledo, Translators, and Latin Mathematical Transfer

Toledo and other Mediterranean centers became important sites of Arabic-Latin translation and intellectual transfer. The reception of mathematical and scientific knowledge involved translators, bilingual collaborators, scholars, clerics, physicians, astronomers, and teachers. Texts in astronomy, mathematics, medicine, philosophy, and related fields moved into Latin through these networks.

The importance of Toledo should not be exaggerated into a single magical origin point. Translation activity occurred across multiple places and routes. But Toledo became symbolically and practically important because it linked Arabic, Romance, Hebrew, and Latin language communities in a setting where texts and scholars could interact.

Arabic-Latin transfer made computational knowledge portable across scholarly worlds.

Back to top ↑

Fibonacci, Liber Abaci, and Merchant Calculation

Leonardo of Pisa, known as Fibonacci, is central to the Latin reception of Hindu-Arabic numerals and commercial arithmetic. His Liber Abaci, first completed in 1202, presented methods of calculation useful for merchants, exchange, weights, measures, profit, barter, partnership, and other practical problems. It did not single-handedly introduce calculation to Europe, but it became one of the most important Latin works promoting the usefulness of Hindu-Arabic numerals and algorithmic arithmetic.

The importance of Liber Abaci is procedural. It teaches through examples. It shows how numerals can solve real problems. It brings arithmetic into commerce, education, and social trust. It helps demonstrate that algorism is not only a scholarly curiosity but a practical method.

Fibonacci’s importance lies less in a famous sequence than in the practical normalization of written calculation.

Back to top ↑

Abacus Culture and the Practical Reception of Algorism

Algorism entered a world that already had calculation practices. Counting boards, abaci, finger reckoning, Roman numerals, memorized procedures, and merchant techniques were already present. New methods do not arrive into emptiness. They compete with, complement, and gradually reshape existing practices.

This is why reception matters. A superior notation does not automatically win. People must trust it. Teachers must teach it. Merchants must find it useful. Legal and administrative systems must accept it. Institutions must reproduce it. The adoption of algorism was therefore social as well as mathematical.

Algorism’s reception depended on practical usefulness, teaching, and trust.

Back to top ↑

Universities, Schools, and Institutional Learning

The reception of algorism and algebra was shaped by institutions. Universities, cathedral schools, commercial schools, private teachers, notarial offices, merchant houses, and administrative settings all created different uses for calculation. Some needed theoretical mathematics. Others needed practical arithmetic. Others needed astronomy, calendar calculation, surveying, or account keeping.

Institutional learning matters because algorithms become durable when they enter curricula and routine practice. A method taught repeatedly becomes part of cultural memory. A method copied into textbooks becomes portable. A method used in accounts becomes economically consequential. A method accepted in institutions becomes trusted.

Institutions turn imported methods into ordinary knowledge.

Back to top ↑

Terminology: From Algorizmi to Algorithm

The journey from al-Khwārizmī’s name to terms such as algorism and algorithm is a reminder that technical vocabulary preserves historical memory. A name becomes a method. A method becomes a field of procedures. A field of procedures becomes a general concept for rule-governed computation.

This transformation did not happen instantly. Latin terms shifted over time. Meanings broadened. “Algorism” became associated with arithmetic using Hindu-Arabic numerals. “Algorithm” eventually came to refer more generally to step-by-step procedures. The word’s history is therefore itself a reception history.

Technical words carry institutional histories of method.

Back to top ↑

Reception, Resistance, and Standardization

New computational methods often face resistance. They may seem unfamiliar, opaque, error-prone, fraudulent, or socially disruptive. Hindu-Arabic numerals were powerful, but they also required trust. Written digits could be altered. Zero could be misunderstood. Place value was unfamiliar. Existing methods already worked for many purposes.

Standardization helped resolve some of these issues. Repeated teaching, merchant use, bookkeeping practice, printed arithmetic manuals, institutional acceptance, and cross-regional trade made algorism increasingly ordinary. Reception is the movement from novelty to routine.

A method becomes powerful when people know how to trust, teach, and verify it.

Back to top ↑

Commercial Arithmetic and Public Trust

Commercial arithmetic made algorism socially consequential. Merchants needed reliable methods for exchange rates, weights, measures, partnerships, profit, interest, barter, and accounting. A computational method that helps solve practical problems becomes more than abstract knowledge. It becomes a tool of economic coordination.

Public trust matters because calculation affects obligations. A wrong conversion can change a debt. A mistaken partnership calculation can change profit distribution. A fraudulent numeral can alter a record. Algorithmic methods therefore entered Latin Europe not only as mathematics but as public techniques for managing trust, evidence, and accountability.

Commercial arithmetic helped make algorithmic calculation a public practice.

Back to top ↑

From Verbal Procedure to Symbolic Algebra

Early algebraic reception in Latin Europe remained largely verbal. Problems were described in words. Cases were classified. Solutions were explained through prose and examples. Over time, algebra moved toward more symbolic forms, but the procedural core came first.

This transition matters because it shows that algorithmic reasoning does not require modern symbolism at the beginning. A procedure can be verbal, geometric, tabular, diagrammatic, or symbolic. What makes it algorithmic is the structured sequence of operations and the conditions under which they apply.

Algebra became symbolic gradually, but it was procedural from the start.

Back to top ↑

Origin Stories and Careful Interpretation

The story from Baghdad to Latin Europe is often simplified. One version says Europe simply received superior mathematics from Arabic sources. Another version says Europe independently created modern mathematics after rediscovering ancient knowledge. Both narratives are too flat.

A careful account recognizes multiple layers. Indian numerals traveled through Arabic mathematical culture. Arabic scholars translated, created, commented, adapted, and systematized. Latin translators selected and recoded materials. Merchants, teachers, and institutions made procedures usable. European scholars then adapted and extended them further. Reception was not passive copying, but it was also not independent invention.

The strongest history is not a competition over origin. It is a map of transmission, adaptation, and use.

Back to top ↑

Back to top ↑

Mathematics, Computation, and Modeling

Place-value notation can be modeled as:

Reception can be modeled as a transfer function:

The movement from procedure to adoption can be summarized as:

Algebraic reception can be modeled as:

These formulas use modern notation to make the reception structure visible. They are interpretive models, not claims that medieval Latin authors used this symbolic notation.

Back to top ↑

Python Workflow: Algorism, Algebra, and Reception Map

The Python workflow below creates a dependency-light interpretive map of algorism, algebra, and reception. It scores themes by procedural portability, notation change, translation pathway, teaching value, practical utility, institutional adoption, trust and verification, historical significance, ethical caution, and modern resonance, then writes reproducible CSV and JSON outputs.

# baghdad_latin_europe_algorism_algebra_reception_map.py
# Dependency-light workflow for mapping algorism, algebra, and reception.

from __future__ import annotations

from dataclasses import asdict, dataclass
from pathlib import Path
from statistics import mean
import csv
import json
from datetime import datetime, timezone

ARTICLE_ROOT = Path(__file__).resolve().parents[1]
TABLES = ARTICLE_ROOT / "outputs" / "tables"
JSON_DIR = ARTICLE_ROOT / "outputs" / "json"


@dataclass(frozen=True)
class ReceptionConfig:
    article: str = "from_baghdad_to_latin_europe_algorism_algebra_and_reception"
    core_threshold: float = 0.80
    high_portability_threshold: float = 0.86


def timestamp_utc() -> str:
    return datetime.now(timezone.utc).isoformat()


def write_csv(path: Path, rows: list[dict[str, object]]) -> None:
    path.parent.mkdir(parents=True, exist_ok=True)
    if not rows:
        path.write_text("", encoding="utf-8")
        return
    fieldnames = sorted({key for row in rows for key in row.keys()})
    with path.open("w", newline="", encoding="utf-8") as handle:
        writer = csv.DictWriter(handle, fieldnames=fieldnames, extrasaction="ignore")
        writer.writeheader()
        writer.writerows(rows)


def write_json(path: Path, payload: object) -> None:
    path.parent.mkdir(parents=True, exist_ok=True)
    path.write_text(json.dumps(payload, indent=2, sort_keys=True), encoding="utf-8")


def reception_themes() -> list[dict[str, object]]:
    return [
        {"theme_id": "algorism_written_arithmetic", "procedural_portability": 0.98, "notation_change": 0.98, "translation_pathway": 0.92, "teaching_value": 0.96, "practical_utility": 0.96, "institutional_adoption": 0.92, "trust_verification": 0.90, "historical_significance": 0.98, "ethical_caution": 0.84, "modern_resonance": 0.98},
        {"theme_id": "algebra_rule_governed_problem_solving", "procedural_portability": 0.96, "notation_change": 0.88, "translation_pathway": 0.94, "teaching_value": 0.94, "practical_utility": 0.92, "institutional_adoption": 0.90, "trust_verification": 0.92, "historical_significance": 0.98, "ethical_caution": 0.84, "modern_resonance": 0.96},
        {"theme_id": "hindu_arabic_numerals_place_value_zero", "procedural_portability": 0.98, "notation_change": 0.98, "translation_pathway": 0.94, "teaching_value": 0.94, "practical_utility": 0.98, "institutional_adoption": 0.92, "trust_verification": 0.90, "historical_significance": 0.98, "ethical_caution": 0.86, "modern_resonance": 0.98},
        {"theme_id": "toledo_and_arabic_latin_transfer", "procedural_portability": 0.92, "notation_change": 0.88, "translation_pathway": 0.98, "teaching_value": 0.88, "practical_utility": 0.88, "institutional_adoption": 0.94, "trust_verification": 0.88, "historical_significance": 0.96, "ethical_caution": 0.88, "modern_resonance": 0.94},
        {"theme_id": "fibonacci_liber_abaci_commerce", "procedural_portability": 0.96, "notation_change": 0.96, "translation_pathway": 0.90, "teaching_value": 0.98, "practical_utility": 0.98, "institutional_adoption": 0.94, "trust_verification": 0.92, "historical_significance": 0.96, "ethical_caution": 0.86, "modern_resonance": 0.96},
        {"theme_id": "abacus_culture_reception_resistance", "procedural_portability": 0.88, "notation_change": 0.92, "translation_pathway": 0.84, "teaching_value": 0.90, "practical_utility": 0.94, "institutional_adoption": 0.90, "trust_verification": 0.96, "historical_significance": 0.92, "ethical_caution": 0.88, "modern_resonance": 0.94},
        {"theme_id": "origin_story_caution", "procedural_portability": 0.86, "notation_change": 0.86, "translation_pathway": 0.92, "teaching_value": 0.86, "practical_utility": 0.84, "institutional_adoption": 0.86, "trust_verification": 0.90, "historical_significance": 0.94, "ethical_caution": 0.98, "modern_resonance": 0.94},
    ]


def score_theme(row: dict[str, object], config: ReceptionConfig) -> dict[str, object]:
    reception_score = mean([
        float(row["procedural_portability"]),
        float(row["notation_change"]),
        float(row["translation_pathway"]),
        float(row["teaching_value"]),
        float(row["practical_utility"]),
        float(row["institutional_adoption"]),
        float(row["trust_verification"]),
        float(row["historical_significance"]),
        float(row["ethical_caution"]),
        float(row["modern_resonance"]),
    ])

    if reception_score >= config.core_threshold and float(row["procedural_portability"]) >= config.high_portability_threshold:
        interpretive_status = "core_algorism_algebra_reception_thread"
    elif reception_score >= config.core_threshold:
        interpretive_status = "major_algorism_algebra_reception_thread"
    else:
        interpretive_status = "supporting_algorism_algebra_reception_thread"

    return {
        "theme_id": row["theme_id"],
        "procedural_portability": round(float(row["procedural_portability"]), 6),
        "notation_change": round(float(row["notation_change"]), 6),
        "translation_pathway": round(float(row["translation_pathway"]), 6),
        "teaching_value": round(float(row["teaching_value"]), 6),
        "practical_utility": round(float(row["practical_utility"]), 6),
        "institutional_adoption": round(float(row["institutional_adoption"]), 6),
        "trust_verification": round(float(row["trust_verification"]), 6),
        "historical_significance": round(float(row["historical_significance"]), 6),
        "ethical_caution": round(float(row["ethical_caution"]), 6),
        "modern_resonance": round(float(row["modern_resonance"]), 6),
        "reception_score": round(reception_score, 6),
        "interpretive_status": interpretive_status,
    }


def interpretation_cautions() -> list[dict[str, str]]:
    return [
        {"caution": "do_not_make_borrowing_passive", "meaning": "Latin Europe received, adapted, taught, resisted, and institutionalized methods."},
        {"caution": "do_not_erase_arabic_and_indian_transmission", "meaning": "Hindu-Arabic numerals and Arabic mathematical traditions are central to the pathway."},
        {"caution": "do_not_claim_fibonacci_singlehandedly_introduced_numerals", "meaning": "Fibonacci was a major popularizer, but transmission involved broader networks."},
        {"caution": "do_not_reduce_algorithm_to_etymology", "meaning": "The word history matters, but algorithmic reasoning also depends on procedures and institutions."},
        {"caution": "do_not_treat_algebra_as_symbolic_from_the_start", "meaning": "Early algebraic reception was often verbal, case-based, geometric, and procedural."},
    ]


def main() -> None:
    config = ReceptionConfig()
    themes = reception_themes()
    scored = [score_theme(row, config) for row in themes]
    cautions = interpretation_cautions()

    summary = {
        "article": config.article,
        "timestamp_utc": timestamp_utc(),
        "themes_reviewed": len(scored),
        "core_threads": sum(1 for row in scored if row["interpretive_status"] == "core_algorism_algebra_reception_thread"),
        "major_threads": sum(1 for row in scored if row["interpretive_status"] == "major_algorism_algebra_reception_thread"),
        "supporting_threads": sum(1 for row in scored if row["interpretive_status"] == "supporting_algorism_algebra_reception_thread"),
        "mean_reception_score": round(mean(float(row["reception_score"]) for row in scored), 6),
        "cautions": len(cautions),
        "interpretation": "Algorism and algebra should be studied as received computational methods: translated, taught, practiced, trusted, resisted, adapted, and institutionalized across Latin Europe.",
    }

    write_csv(TABLES / "reception_themes.csv", themes)
    write_csv(TABLES / "reception_map.csv", scored)
    write_csv(TABLES / "interpretation_cautions.csv", cautions)
    write_csv(TABLES / "reception_summary.csv", [summary])

    write_json(JSON_DIR / "reception_config.json", asdict(config))
    write_json(JSON_DIR / "reception_map.json", scored)
    write_json(JSON_DIR / "interpretation_cautions.json", cautions)
    write_json(JSON_DIR / "reception_summary.json", summary)

    print("From Baghdad to Latin Europe algorism, algebra, and reception map complete.")
    print(TABLES / "reception_summary.csv")


if __name__ == "__main__":
    main()

This workflow turns reception into a reproducible interpretive artifact: algorism, algebra, numerals, place value, zero, translation pathways, Fibonacci, abacus culture, commercial arithmetic, trust, institutional adoption, and origin-story caution are documented together.

Back to top ↑

R Workflow: Reception Diagnostics

The R workflow reads the generated CSV outputs, summarizes reception themes, visualizes theme dimensions, and writes an additional diagnostic table.

# baghdad_latin_europe_algorism_algebra_reception_summary.R
args <- commandArgs(trailingOnly = FALSE)
file_arg <- grep("^--file=", args, value = TRUE)

if (length(file_arg) > 0) {
  script_path <- normalizePath(sub("^--file=", "", file_arg[1]), mustWork = TRUE)
  article_root <- normalizePath(file.path(dirname(script_path), ".."), mustWork = TRUE)
} else {
  article_root <- getwd()
}

setwd(article_root)

tables_dir <- file.path(article_root, "outputs", "tables")
figures_dir <- file.path(article_root, "outputs", "figures")
dir.create(tables_dir, recursive = TRUE, showWarnings = FALSE)
dir.create(figures_dir, recursive = TRUE, showWarnings = FALSE)

map_path <- file.path(tables_dir, "reception_map.csv")
summary_path <- file.path(tables_dir, "reception_summary.csv")

if (!file.exists(map_path)) {
  stop(paste("Missing", map_path, "Run the Python workflow first."))
}

reception_map <- read.csv(map_path, stringsAsFactors = FALSE)
summary <- read.csv(summary_path, stringsAsFactors = FALSE)

png(file.path(figures_dir, "reception_dimensions.png"), width = 1200, height = 850)
score_matrix <- t(as.matrix(reception_map[, c("procedural_portability", "notation_change", "translation_pathway", "teaching_value", "practical_utility", "institutional_adoption", "trust_verification", "historical_significance", "ethical_caution", "modern_resonance")]))
barplot(score_matrix,
        beside = TRUE,
        names.arg = reception_map$theme_id,
        las = 2,
        ylim = c(0, 1),
        ylab = "Interpretive Score",
        main = "From Baghdad to Latin Europe: Algorism, Algebra, and Reception Dimensions")
legend("bottomright",
       legend = rownames(score_matrix),
       cex = 0.68,
       bty = "n")
grid()
dev.off()

png(file.path(figures_dir, "reception_score_by_theme.png"), width = 1000, height = 750)
barplot(reception_map$reception_score,
        names.arg = reception_map$theme_id,
        las = 2,
        ylab = "Reception Score",
        main = "Algorism, Algebra, and Reception Score by Theme")
grid()
dev.off()

r_summary <- data.frame(
  themes_reviewed = summary$themes_reviewed[1],
  core_threads = summary$core_threads[1],
  major_threads = summary$major_threads[1],
  supporting_threads = summary$supporting_threads[1],
  mean_reception_score = summary$mean_reception_score[1],
  cautions = summary$cautions[1],
  diagnostic_note = "Algorism and algebra should be studied as received computational methods: translated, taught, practiced, trusted, resisted, adapted, and institutionalized across Latin Europe."
)

write.csv(r_summary, file.path(tables_dir, "r_reception_diagnostic_summary.csv"), row.names = FALSE)
print(r_summary)

The R layer makes the interpretive structure visible: written arithmetic, algebraic problem solving, numerals, place value, zero, translation pathways, Fibonacci, abacus culture, commercial trust, institutional adoption, and origin-story caution can be examined as related but distinct dimensions of reception.

Back to top ↑

GitHub Repository

The companion repository contains reproducible workflows, synthetic interpretive data, outputs, calculators, documentation, and multilingual examples for this article.

Back to top ↑

A Practical Method for Studying Mathematical Reception

A careful study of mathematical reception asks how a method becomes usable in a new environment.

This method treats reception as active transformation, not passive borrowing.

Back to top ↑

Common Pitfalls

The first pitfall is treating Latin Europe as a passive receiver. The second is treating Europe as an isolated inventor. The third is reducing algorithm to etymology. The fourth is imagining immediate replacement of older calculation practices.

Reception history becomes stronger when it avoids both erasure and exaggeration.

Back to top ↑

Why Reception Belongs in Algorithmic Reasoning

From Baghdad to Latin Europe, algorism, algebra, and reception show that computational methods do not become powerful simply by existing. They must be transmitted, translated, taught, tested, trusted, resisted, adapted, and institutionalized. A method must work in classrooms, account books, manuscripts, commercial settings, and scholarly traditions.

This history expands the meaning of algorithmic reasoning. Algorithms are not only formal procedures. They are also cultural artifacts that require representation, pedagogy, infrastructure, and legitimacy. A calculation method becomes durable when it can travel across language, notation, institution, and use.

The lesson for modern systems is direct. New computational tools are adopted through trust, documentation, training, standards, integration, and public accountability. The history of algorism and algebra reminds us that technical superiority alone is never enough. Procedures live only when communities know how to use them. AI belongs in the toolkit, not in control.

Back to top ↑

Related Articles

• Translation Movements and Computational Knowledge Transfer
• Islamic Mathematical Philosophy and the Nature of Procedure
• Al-Khwārizmī, Algorism, and the Procedural Imagination
• Al-Jabr wa’l-Muqābalah: Algebra as Rule-Governed Problem Solving
• Hindu-Arabic Numerals and the Transmission of Positional Calculation

Back to top ↑

Further Reading

• Allard, A. (1992) Muhammad ibn Mūsā al-Khwārizmī: Le calcul indien (Algorismus). Paris: Blanchard.
• Burnett, C. (2009) Arabic into Latin in the Middle Ages: The Translators and Their Intellectual and Social Context. Farnham: Ashgate.
• Burnett, C. (2001) ‘The Coherence of the Arabic-Latin Translation Program in Toledo in the Twelfth Century’. Science in Context, 14(1–2), pp. 249–288.
• Fibonacci (2002) Fibonacci’s Liber Abaci: A Translation into Modern English of Leonardo Pisano’s Book of Calculation. Translated by L.E. Sigler. New York: Springer.
• Hasse, D.N. (2008) ‘Influence of Arabic and Islamic Philosophy on the Latin West’. Stanford Encyclopedia of Philosophy.
• Høyrup, J. (1994) In Measure, Number, and Weight: Studies in Mathematics and Culture. Albany: SUNY Press.
• Menninger, K. (1992) Number Words and Number Symbols: A Cultural History of Numbers. New York: Dover.
• Smith, D.E. and Karpinski, L.C. (1911) The Hindu-Arabic Numerals. Boston: Ginn and Company.

Back to top ↑

References

• Allard, A. (1991) ‘The Arabic Origins and Development of Latin Algorisms in the Twelfth Century’. Arabic Sciences and Philosophy, 1(2), pp. 233–283.
• Britannica (2026) ‘Fibonacci’. Available at: https://www.britannica.com/biography/Fibonacci.
• Britannica (n.d.) ‘Liber abaci’. Available at: https://www.britannica.com/topic/Liber-abaci.
• Burnett, C. (2001) ‘The Coherence of the Arabic-Latin Translation Program in Toledo in the Twelfth Century’. Science in Context, 14(1–2), pp. 249–288. Available at: https://sidoli.w.waseda.jp/Burnett_2001.pdf.
• Burnett, C. (2009) Arabic into Latin in the Middle Ages: The Translators and Their Intellectual and Social Context. Farnham: Ashgate.
• Fibonacci (2002) Fibonacci’s Liber Abaci: A Translation into Modern English of Leonardo Pisano’s Book of Calculation. Translated by L.E. Sigler. New York: Springer.
• Hasse, D.N. (2008) ‘Influence of Arabic and Islamic Philosophy on the Latin West’. Stanford Encyclopedia of Philosophy. Available at: https://plato.stanford.edu/entries/arabic-islamic-influence/.
• Høyrup, J. (1994) In Measure, Number, and Weight: Studies in Mathematics and Culture. Albany: SUNY Press.
• Menninger, K. (1992) Number Words and Number Symbols: A Cultural History of Numbers. New York: Dover.
• Smith, D.E. and Karpinski, L.C. (1911) The Hindu-Arabic Numerals. Boston: Ginn and Company.

Back to top ↑