Lesson plan

Prince (software)

Prince (formerly Prince XML) is a computer program that converts XML and HTML documents into PDF files by applying Cascading Style Sheets (CSS). Prince is a commercial product, which is free to download and use for non-commercial purposes. Prince supports all common web standards, including HTML, CSS and JavaScript, through its own code. That is, Prince is not based on a browser engine, but implements its own engine. Prince can generate accessible PDFs conforming to the PDF/UA profile (ISO 14289, the International Standard for accessible PDF technology) that can be used by people with assistive technologies. Prince supports many languages, including Thai, Indic scripts (Hindi, Bengali, Tamil, etc.) and right-to-left scripts like Arabic and Hebrew. Prince is developed by YesLogic, a small company based in Melbourne, Australia. Since 2004, Håkon Wium Lie, the co-creator of CSS, has been chairman of the board.

Back to article

Article summary

Prince (formerly Prince XML) is a computer program that converts XML and HTML documents into PDF files by applying Cascading Style Sheets (CSS). Prince is a commercial product, which is free to download and use for non-commercial purposes. Prince supports all common web standards, including HTML, CSS and JavaScript, through its own code. That is, Prince is not based on a browser engine, but implements its own engine. Prince can generate accessible PDFs conforming to the PDF/UA profile (ISO 14289, the International Standard for accessible PDF technology) that can be used by people with assistive technologies. Prince supports many languages, including Thai, Indic scripts (Hindi, Bengali, Tamil, etc.) and right-to-left scripts like Arabic and Hebrew. Prince is developed by YesLogic, a small company based in Melbourne, Australia. Since 2004, Håkon Wium Lie, the co-creator of CSS, has been chairman of the board.

Key claims

  1. publication date: 2007-11-15 — source: Wikipedia, revision 1369296328, retrieved 2026-10-20 · confidence 0.95

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. The record states that the publication date is "2007-11-15". What evidence would count against this claim?
  3. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  4. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.