• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!



Page history last edited by Laura Gibbs 13 years, 8 months ago

Here are some tips and guidelines on transcribing pages. To edit a page, you will need to be logged in to PBWiki (here's how to create an account - it's easy!). For a step-by-step overview of how to edit a wiki page, see these Step-by-Step Instructions (with screenshots).


On the Homepage, you will find a list of pages; as you BEGIN work on something, please put your name (or "xxx" if you wish to remain anonymous) in the box for that step of the process (Type or Format or Proof) for that page. That will let people know which work has begun, and which work needs to be done. The pages will be going through a process of transcribing as follows: 

1) Type: Typing the text as it appears on the page of the book. When you are DONE typing the page, please put the initial and final entries in the appropriate columns.

2) Format: Add bold to the head words, and italicize the sources cited.

3) Proof: We will need to come up with a series of proofreading stages; for now, we will just call it "Proof" - which means someone has compared the text of the Wiki page to the text of the book and corrected any problems or highlighted those problems for future examination. Please feel free to use the comments area of the page for remarks, observations, questions, etc.


Et. Please replace the ligature symbol ampersand with et.


V-j. Please try to follow Comenius's use of V/u and his use of the letter j. This is something we can standardize in the proofreading stage, but it would be best if you could follow his standard, even if it is different from the orthography you might be used to.


Standard Roman characters only: No digraph ligatures.  For "ae" please use two separate letters ("a" and "e") instead of using the compound digraph æ. Likewise for the "oe" digraph.


Standard Roman characters only: No diacritics. In order to make sure the dictionary pages are as search-engine-friendly as possible, please do not use the diacritical marks (accent marks, circumflexes) which are occasionally found in the book to indicate long vowels - or, if you do want to include them, please do a standard form first, THEN followed by the form with the diacritic in brackets, e.g.

maxime [maximè]. 


Greek font. The Greek font is not easy to read, so if you are not familiar with this style of Greek please just write [PROBLEM: GREEK] in the text and someone else will add the Greek later. If you are able to read the font, please include  a Unicode Greek version - doing Greek is really easy, since you can convert Beta Code (using simple Roman characters) to Unicode at TypeGreek.com. Here is an example:

Cannot read: [PROBLEM: GREEK]

in Beta Code it would be:  o( gri/fos

you can convert that to Unicode easily: ὁ γρίφος


Errors in the original. When you find something that is certainly or possibly an error in the original, you should add a Comment to that page. Depending on how certain you are about the error, you might also choose to correct it in your transcription. In either case: please make sure to add a comment to the page about the error.


Hyphenated words between pages. If your new page starts with the second part of a hyphenated word at the top of the page, please look back to the previous page so that you can supply the whole word. Likewise, when you finish a page, if the last word is hyphenated, please look to the next page and include the whole word, not just the hyphenated portion, at the bottom of the page.


Problems. Where you note a problem please write [PROBLEM] in all capital letters (the use of this English word will make it easier to search for the problems later). You can also use the "Comments" space on any page to include your questions and observations. Please make sure you can put in BRACKETS any notes you want to include about the problem, e.g.

[PROBLEM - top line missing from page scan]


Please feel free to edit this document, or to add your questions and suggestions in the Comments field below. Thank you!

Comments (6)

Johan Winge said

at 9:55 am on Jan 3, 2009

What about elementary typos in the original? For example, on p. 73 it says "Auctarium] Vid. Additamentnm." Since the goal is not to produce an exact copy of the original anyways, I have corrected it to "Additamentum", but an official policy regarding this would be welcome.

Laura Gibbs said

at 10:27 am on Jan 3, 2009

Hi Johan! I think any time you make a correction you should add a Comment on the page. I found what I am 99.99% sure is a typo (mentis for montis), but I left it as it, and put a Comment on the page: http://comlex.pbwiki.com/090 - I'll add something to that effect here on the Transcribing notes.
By the way: I am STAGGERED by all the pages you are transcribing. Thank you so much for all your efforts here! :-)

Johan Winge said

at 3:04 pm on Jan 3, 2009

Alright, I've added a comment about it. About all the pages: I believe a project such as this may benefit from a kick start, to get things rolling. I don't promise to keep up the pace. ;-)

Laura Gibbs said

at 2:20 pm on Jan 12, 2009

For the second round of proofreading, we definitely need to check on those hyphenated words between pages. Mark just called that to my attention. We need whole words rather than hyphenated words for better searching!

Johan Winge said

at 3:46 pm on Jan 12, 2009

Alright, but wouldn't we want to eventually edit, say, each letter, or the whole dictionary, into one document anyway? If so, it doesn't really matter how we handle the page breaks now. But, certainly, I'm all for consistent practice in this regard. So, just to make things crystal clear: the current guideline is to complete the hyphenated words on both sides, is that right? In that way, two consecutive transcribed pages will end and start, respectively, with the same word, when the original has the word hyphenated.

This brings me to ask something I have wondered about: how to treat the catchwords? (I.e. the final word on the bottom of the page, which shows how the next page begins, e.g. "Ablue-" on p. 3.)

While we're at it, what about simply ignoring the signature marks? (I.e., e.g., "A 2" at the bottom of p. 3.) They are hardly meaningful to us.

Laura Gibbs said

at 4:38 pm on Jan 13, 2009

Hi Johan, I can see two at least three long-term goals: (1) a good searchable online version (that's my own personal goal, and Mark's point about the hyphenated words is a good one with regard to searchability of the text), and (2) a good PDF-based version, substantially reformatted and suitable for printing and, finally, (3) there might be people have a historical interest in the actual 17th-century book of Comenius, reproducing physical features of that original text (signature marks, catchwords, respecting the pagination of the original, etc.). Luckily for us, at this stage of those project, the overlap between those three goals is very strong.

What I was guessing would happen is that after we get the first round of transcribing done, people would then step forward who want to direct these more specific projects, and we would coordinate a round of proofreading and formatting that would take into account the specific needs of those specific projects.

I am really glad that people are commenting on the issues that arise as we go through this first time, and on that basis I think we can come up with a really comprehensive proofreading/formatting strategy for the "Beta version," let's call it, when we are able to define the specific ways in which people want to use the text. Right now, this is the "Alpha version," and to some extent we are figuring it out as we go along.

Does that make sense? There is a real danger in both over-managing and under-managing this process. To be honest, I am just AMAZED by the contributions people are making and how smoothly it seems to be going! :-)

You don't have permission to comment on this page.