ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Lords Prayer / Our Father in Old English (Anglo-Saxon), Early / Late Middle English, Early Modern English

Updated on May 28, 2013

Lord's Prayer / Our Father - an Introduction

Although we might think it, the Lords Prayer / Our Father has not always been as it is today.. Below you will find four versions from Old English through early and late Middle English to Early Modern English. The first version is pure Anglo-Saxon while the later versions show the incoming of a few alien words. Wycliff was responsible for temptation and Tyndale for trespasses and both agreed on the use of the Hebrew Amen.

The authorised version, completed in 1611, followed Tyndale closely throughout the New Testament and those parts of the Old Testament that Tyndale had completed. King James's bishops were working on this task at the peak of the English language. Their understanding of the music of words was natural in an age when transfer of information was by word of mouth in poems and verse. The result of utilising Tyndale and Wycliff was that the language was old-fashioned even at that time, but had enough merit for it to be adopted.

Many of the most familiar Bible passages are Tyndale's work. Like Cramer, who composed the English Prayer Book, he made an immeasurable contribution to the language - and both were burnt at the stake for their troubles. How heretical words can be!

As to the spellings of these versions of 'Our Father', it should be noted that Old English had some distinctive letters for a few sounds, for example 'th' that is reproduced here as 'ð'. It had no 'v', as in 'heofen '. When 'v' was introduced by the Normans it was used interchangeably with 'u' and was a bit of a hindrance for several centuries (as you will see in Wycliff's version below).

A long 'a' in Old English has over the centuries become a modern 'o' and the Old English swa is the ancestor of our 'so' (the 'w' having been suppressed to silent as it has in 'sword'). At a very early date the emphatic 'all so' was concatenated into 'also'. A further contraction produced 'as'. Interestingly these have all survived the passing of time as separate words which are used variously, our contemporary expressions 'so also', 'as also', 'so as' all springing from the old 'swa '.

Translations from different periods illustrate some of the changes in the language.

Lord's Prayer / Our Father in Anglo-Saxon

Lord's Prayer / Our Father - Old English Version

The text below is from a tenth century translation of St. Matthew's Gospel:

Fæder ūre, ðū ðē eart on heofonum,

Father our, thou that art in heaven,

Sī ðīn nama gehālgod.

be thy name hallowed.

Tō becume ðīn rice,

Come thy rule,

Gewurde ðīn willa On eorþan,

Be done thy will in earth,

swā swā on heofonum.

as also in heaven.

Urne gedægwhamlīcan hlāf syle ūs tōdæg..

Our daily loaf give us today.

And forgyf ūs ūre gyltas,

And forgive us our guilt

Swā swā wē forgyfaþ ūrum gyltendum.

as also we forgive our guilty ones.

And ne gelæd ðū ūs on costnunge,

And not lead thou us into trial,

ac alȳs ūs of yfele. Sōþlice..

but release us from evil. Soothly.

[gedæg / wham / līcan = day / each / like i.e. daily]

[costnunge = costing i.e. evaluating or testing]

Lord's Prayer / Our Father - Early Middle English Version

This version of the Lord's Prayer is from Reliquiae Antiquae of the thirteenth century:

Fader oure that art in heve

i-halged bee thi nome.

I-cume thi kinereiche,

Y-worthe thi wylle also is in hevene so be on erthe.

Oure ich-dayes bred gif us to day,

& forgif us our gultes,

also we forgifet oure gultare,

& ne led us nowth into fondingge,

auth a-les ows of harme. So be hit.

This is still close to the Old English version but you will note that the word order is changing, inflexions are weakening and the spelling is erratic.

[kinereich e = king-ric Cf bishopric.

ich = each

gultes = guilt

fondingge = foolishness ( a bad translation that did not last)

a-les (Old English a-lys ) is part of the word 'loosen', to set free]

Lord's Prayer / Our Father - Late Middle English Version

The Lord's Prayer of late Middle English is from Wycliff's New Testament of the fourteenth century:

Our fadir that art in heuenes,

halwid be thi name.

Thi kyngdom cumme to.

Be thi wille don as in heuen and in erthe.

Gif to vs this day ouer breed oure other substances,

and forgeue to vs oure dettis

as we forgeue to oure dettours,

and leede vs nat in to temptacioun,

but delyuere vs fro yuel. Amen.

Lord's Prayer - Early Modern English

This version of the Lord's Prayer in Late Middle English is from Tyndale's Teastament of 1526:

O oure father which art in heven,

halowed be thy name.

Let thy kingdom come.

Thy wyll be fulfilled, as well in eth

as hit ys in heven.

Geve vs this daye our dayly breade,

And forgeve vs oure treaspases

euen as we forgeve them which treaspas vs.

Leede vs not into temptation,

but delyvre vs from yvell. Amen.

Lord's Prayer by 2 Year Old

Lord's Prayer - Other Versions

This article is not intended as a comprehensive indulgence in the Prayer itself but rather a brief examination of how language has evolved the form of the Prayer. For a much greater examination of the Prayer there is none better than that in Wikipedia.

You will note from this article and that on Wikipedia that our current versions are not necessarily as was originally intended and that time has a major influence on the language of all subjects.

working

This website uses cookies

As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://corp.maven.io/privacy-policy

Show Details
Necessary
HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
LoginThis is necessary to sign in to the HubPages Service.
Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
AkismetThis is used to detect comment spam. (Privacy Policy)
HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
Features
Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
MavenThis supports the Maven widget and search functionality. (Privacy Policy)
Marketing
Google AdSenseThis is an ad network. (Privacy Policy)
Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
Index ExchangeThis is an ad network. (Privacy Policy)
SovrnThis is an ad network. (Privacy Policy)
Facebook AdsThis is an ad network. (Privacy Policy)
Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
AppNexusThis is an ad network. (Privacy Policy)
OpenxThis is an ad network. (Privacy Policy)
Rubicon ProjectThis is an ad network. (Privacy Policy)
TripleLiftThis is an ad network. (Privacy Policy)
Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
Statistics
Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
ClickscoThis is a data management platform studying reader behavior (Privacy Policy)