This interface will soon cease to be publicly available. Use the new interface instead. Click here to switch over now.
In editing fields where formatting is required, there are two ways of entering the formatted text, depending on what your browser supports.
type 1: WYSIWYG formatting
On some browsers, when you click in the text box it will change the formatting code into formatted text. This should happen in Internet Explorer for Windows, versions later than 5.5; and in recent Mozilla-based browsers (Netscape 6, Firebird, Mozilla, etc.).
If this occurs, you can use keyboard commands to add and remove formatting, as you would in a word processor. Common commands are:
Note that the commands use the [ctrl] (control) key in both Windows and on Macs (rather than the usual Apple key for commands on Macs).
You should not normally require any other formatting, apart from paragraphs, which will automatically be added when you press enter (as in a word processor). Headings for the fields themselves (such as 'prose context' or 'introduction') will be added automatically. You should only add sub-headings if required by the context (e.g. sometimes this is necessary in poem and saga introductions). Some fields, such as skald biographies and prose context information, should only be one paragraph.
type 2: html tagging
This less-friendly way of adding formatting is required if your browser does not support the above method. Consider upgrading to the latest version of Netscape (in Mac or Windows) or Internet Explorer (in Windows) to take advantage of the above features.
When you click in the text box, if the html tags (such as '<span>' or '<i>') remain, you will have to edit them yourself. For italics, you must place the html italics start tag (<i>) where the italics start and the end tag (</i>) where the italics end. You must include the end tag, even if the italics continue to the end of the text. So, the following text: 'the opening verse in Hkr' should be entered as 'the opening verse in <i>Hkr<i>'.
Other tags are as follows:
As with the WYSIWYG interface, you should not normally require any other formatting.
Material produced in Word can be copied and pasted with formatting in some browsers. The filters below allow you to convert Word files into the appropriate format - instructions are included with these links:
The following should be checked and done before exporting the edition for publication:
These are older and might need some revision:
WHERE note LIKE '<span style="font-family: ReykholtTimes;">%'
AND note LIKE '%</span>'
WHERE biography LIKE '<span style="font-family: ReykholtTimes;">%'
AND biography LIKE '%</span>'
WHERE intro LIKE '<span style="font-family: ReykholtTimes;">%'
AND intro LIKE '%</span>'
WHERE editions LIKE '<span style="font-family: ReykholtTimes;">%'
AND editions LIKE '%</span>'
WHERE context LIKE '<span style="font-family: ReykholtTimes;">%'
AND context LIKE '%</span>'
To produce a version of the edition suitable for printing in book form:
Page size: (A4 297 x 210)
Margins: top: 58.5, bottom: 57.5, inside: 45, outside: 45, gutter: 0, header: 48.5
Text size: 120 x 180
Verse text tables cell widths: 8mm (number), 56, 56 for each helmingr (or 112 for eddic metres)
Windows: Open the Control Panel and click on the fonts folder. You should be able to drag the four font files into the folder, which will install them. Alternatively, click on the menu File > Install New Font... and add the fonts this way.
Mac: Open the folder Libarary > Fonts and drag the fonts into the folder. This installs the fonts.
Fonts will be available the next time you open a program (close and reopen any running programs if you want to use the fonts). If you are having difficulty, try rebooting the system.
Using Unicode characters in Windows
Use the 'Character Map' to select, copy and paste characters.
Using Unicode characters on a Mac
On a Mac, open System Preferences > Language & Text > Input Sources (tab); mark the checkbox next to Keyboard & Character Viewer (at the top). This is a useful tool which shows you all the characters available in all the fonts. You launch the character viewer in the keyboard menu at the top of the screen. There will be a little flag depending on your keyboard set up - under that there is 'Character Viewer'.
The Character Viewer organises the 100,000-odd characters now in Unicode in various ways. The easiest is to change View: to 'Code Tables'. You can then scroll down to the relevant section, e.g. F708 is under 0000E000 Private Use Area, then scroll down in the lower box to F700, and then your character will appear under 8. The Private Use Area is tricky, because the characters are not standardised. In most cases the character will just appear as a square, but when you click on it, you'll get the character under the 'Font Variation' section.
Click on 'Insert' at the bottom and it will appear in the active program.
Alternatively, there is a keyboard 'Unicode Hex Input' under System Preferences > Language & Text > Input Sources (tab); Select this 'keyboard' from under the keyboard menu. You can then enter any Unicode character by holding down the [alt] key and pressing the four-digit hexadecimal code: in the above case [alt]+F708.
You will need to switch between keyboard layouts if you use this method, so often the first method is preferable as it gives a visual way of navigating all the characters and without the different keyboard layout problems.
Collation chart for utf8_icelandic_ci (MySQL 6.0.4)
|© Skaldic Project Academic Body, unless otherwise noted. Database structure and interface developed by Tarrin Wills. All users of material on this database are reminded that its content may be either subject to copyright restrictions or is the property of the custodians of linked databases that have given permission for members of the skaldic project to use their material for research purposes. Those users who have been given access to as yet unpublished material are further reminded that they may not use, publish or otherwise manipulate such material except with the express permission of the individual editor of the material in question and the General Editor of the volume in which the material is to be published. Applications for permission to use such material should be made in the first instance to the General Editor of the volume in question. All information that appears in the published volumes has been thoroughly reviewed. If you believe some information here is incorrect please contact Tarrin Wills with full details.|