DOCSLIB.ORG

Primo Technical Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Technical Guide May 2016 Ex Libris Confidential 6/7 1 CONFIDENTIAL INFORMATION The information herein is the property of Ex Libris Ltd. or its affiliates and any misuse or abuse will result in economic loss. DO NOT COPY UNLESS YOU HAVE BEEN GIVEN SPECIFIC WRITTEN AUTHORIZATION FROM EX LIBRIS LTD. This document is provided for limited and restricted purposes in accordance with a binding contract with Ex Libris Ltd. or an affiliate. The information herein includes trade secrets and is confidential. DISCLAIMER The information in this document will be subject to periodic change and updating. Please confirm that you have the most current documentation. There are no warranties of any kind, express or implied, provided in this documentation, other than those expressly agreed upon in the applicable Ex Libris contract. This information is provided AS IS. Unless otherwise agreed, Ex Libris shall not be liable for any damages for use of this document, including, without limitation, consequential, punitive, indirect or direct damages. Any references in this document to third‐party material (including third‐party Web sites) are provided for convenience only and do not in any manner serve as an endorsement of that third‐ party material or those Web sites. The third‐party materials are not part of the materials for this Ex Libris product and Ex Libris has no liability for such materials. TRADEMARKS ʺEx Libris,ʺ the Ex Libris bridge , Primo, Aleph, Alephino, Voyager, SFX, MetaLib, Verde, DigiTool, Preservation, Rosetta, URM, ENCompass, Endeavor eZConnect, WebVoyáge, Citation Server, LinkFinder and LinkFinder Plus, and other marks are trademarks or registered trademarks of Ex Libris Ltd. or its affiliates. The absence of a name or logo in this list does not constitute a waiver of any and all intellectual property rights that Ex Libris Ltd. or its affiliates have established in any of its products, features, or service names or logos. Trademarks of various third‐party products, which may include the following, are referenced in this documentation. Ex Libris does not claim any rights in these trademarks. Use of these marks does not imply endorsement by Ex Libris of these third‐party products, or endorsement by these third parties of Ex Libris products. Oracle is a registered trademark of Oracle Corporation. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Ltd. Microsoft, the Microsoft logo, MS, MS‐DOS, Microsoft PowerPoint, Visual Basic, Visual C++, Win32, Microsoft Windows, the Windows logo, Microsoft Notepad, Microsoft Windows Explorer, Microsoft Internet Explorer, and Windows NT are registered trademarks and ActiveX is a trademark of the Microsoft Corporation in the United States and/or other countries. Unicode and the Unicode logo are registered trademarks of Unicode, Inc. Google is a registered trademark of Google Inc. iPhone is a registered trademark of Apple Inc. Copyright Ex Libris Limited, 2016. All rights reserved. Document released: June 7, 2016 Web address: http://www.exlibrisgroup.com Ex Libris Confidential 6/7 2 The PNX Record This section includes: Introduction PNX Record Sections Subfields in the PNX The Control Section The Display Section The Links Section The Search Section The Facets Section The Sort Section The Duplicate Record Detection Section The FRBR Section The Delivery Section The Ranking Section The Enrichment Section The Additional Data Section Example of a PNX Record Ex Libris, a ProQuest Company 6/7 3 Introduction Primo harvests data from a wide range of source databases and formats. This data must be normalized and optimized to facilitate efficient discovery and delivery. The various source formats must be mapped to the Primo normalized XML (PNX) record. For additional information about the publishing process, refer to the Primo Administration Guide. The PNX record is created and stored in XML format, using the UTF-8 character set. The data in the PNX record is organized in sections, each section containing information for a specific purpose. In some cases, the data is duplicated to provide flexibility to the system when it is processing the data. Ex Libris, a ProQuest Company 6/7 4 PNX Record Sections The following table lists the sections in the PNX record. Sections of the PNX Record Section Contains For additional information, refer to Additional Data Data elements required for a The Additional Data Section number of functions that cannot be extracted from other sections of the PNX. Browse Data that is used to create the Refer to Browse Functionality. browse lists. Control Formatted data that is used for The Control Section control purposes. Delivery and Scoping Data required for managing The Delivery Section delivery and scoping for searches. Display Data displayed in the brief and The Display Section full displays in the user interface (UI). Duplication Detection A Dedup vector, which The Duplicate Record includes all the data required Detection Section by the Duplication Detection algorithm to determine if two records are equivalent. Enrichment Data required by the The Enrichment Section enrichment process. Facets Data used to create faceted The Facets Section browsing in the UI. Grouping (FRBR) A FRBR vector, which includes The FRBR Section one or more keys that identify the group it represents. Ex Libris, a ProQuest Company 6/7 5 Links Links that can be used to The Links Section create the GetIT! functionality and/or links in the record display. Ranking Two booster fields that can be The Ranking Section used to boost the ranking of the record. Search Metadata and full-text data The Search Section that are indexed for searching purposes. Sort Sort fields used as the basis The Sort Section for sorting the results set. Each of the above sections contains various fields. Multiple and repeatable fields of the source record can be concatenated to one field in the PNX record (such as the Display section) or stored in separate fields within the PNX record (such as the Search and Facets sections). In some cases, the system will take only one of the following fields: All fields of the Control section. All fields of the Sort section. All fields of the Dedup and FRBR sections. Delivery section – the Delivery category field. All fields of the Ranking section. Ex Libris, a ProQuest Company 6/7 6 Subfields in the PNX Some fields in the PNX record have multiple values that are delimited by two dollar signs followed by a specific character or number (similar to MARC subfields). The following table lists the various subfield delimiter types used in the PNX record. Subfield Delimiter Types Type Delimiter Description Uppercase Alphabetic The character denotes the content and is persistent across PNX fields. A Algorithm used for FRBR key type. C A constant that displays before the field. This delimiter can be used only in the Display section for the following fields: identifier, relation, and description. The constant can be a code (lower case with no spaces or special characters). The code is translated to a name for display in the Front End using the Display Constants code table. If the text added has no translation in the code table, it will display as entered in the rules. D Text that displays instead of the field—for example, for URLS). I Institution code K Key for FRBR L Library code O Origin of the field used in Deduped records - the sourceid. S Status T Template code U URL Ex Libris, a ProQuest Company 6/7 7 V Value of the field (to distinguish between the value of the field and the display text or constant). Numeric Indicates the order of data elements added to the field. All text fields can be either code or text. Primo first searches for a translation of the value in the codes table. Only if it does not find the translation will Primo display the value. Ex Libris, a ProQuest Company 6/7 8 The Control Section The Control section includes formatted data used for control purposes. The following table lists the contents of the Control section. Control Section Fields Field Code Description sourceid The source ID identifies the source repository in Primo. Every source repository has a configuration file in which the sourceid and other information about the source repository are recorded. originalsourceid This ID identifies the source repository in the source system. This is not necessarily the same as the source repository's identifier in Primo—for example, USM01. sourcerecordid This ID identifies the record in the source repository (such as an ALEPH system number supplied in MARC21 tag 001). This ID must be unique and persistent within the source repository. It is derived from the OAI header. addsrcrecordid This ID identifies an additional ID of the source record. recordid The record ID is a unique identifier of the record in the Primo repository. The sourceid and sourcerecordid are concatenated to create the recordid (for example, ALEPH system number + tag 001). sourcetype Source type—not in use. sourceformat The source format identifies the original format of the source record (such as MARC21, Dublin Core, and MAB2). sourcesystem The source system identifies the system used by the source repository (such as ALEPH, ADAM, MetaLib, SFX, and Digitool). recordtype Record type—not in use. lastmodified Date last modified—not in use. Ex Libris, a ProQuest Company 6/7 9 The Display Section The Display section includes data used in the brief and full display formats of the UI. The basis for the data elements used in the Display section is the Dublin Core element set. Dublin Core was selected as a metadata standard that is intended to support a broad range of purposes and resource types. In some cases, the names of the Dublin Core elements have been modified and a number of additional fields have been added.
Recommended publications
  • Petzl Rig Compact Self- Braking Descender

    Petzl Rig Compact Self- Braking Descender

    Petzl Rig Compact Self- braking Descender Brand:Petzl Options Code Description Price C6286 Yellow $275.00 +GST C1115 Black $325.00 +GST Petzl Rig Compact Self-braking Descender Designed for rope access work (expert users only) Multi-function handle allows the user to: - unlock the rope and control the descent with the hand on the free end of the rope - position himself at the work station without having to tie off the device The automatic return system on the handle limits risks in case of an involuntary action by the user Handle storage position reduces the risk of snagging when the descender is being carried on the harness. The gate on the moving side plate helps prevent dropping the device and facilitates rope installation when passing intermediate anchors Pivoting cam facilitates taking up the slack in the rope. Can also be used to make a reversible haul system, and for short ascents (in conjunction with a FOOTAPE or FOOTCORD foot loop and an ASCENSION handled rope clamp). Lowers heavy loads up to 200 kg (only for expert users; more information on this technique in the technical advice at www.petzl.com) Available in two Colours: yellow and black Specifications Min. rope diameter: 10.5 mm Max. rope diameter: 11.5 mm Weight: 380 g Certifications: EN 341 classe A, CE EN 12841 type C, NFPA 1983 Technical Use, EAC Options D21A D21AN https://colorex.co.nz/shop/products/height-safety/ascenders-descenders/petzl-rig-compact-self -braking-descender/ Page 1 E & OE | Prices are subject to change without notice | Copyright - All Rights Reserved 1633083992 Colours yellow black Rope compatibility 10.5 to 11.5 mm 10.5 to 11.5 mm https://colorex.co.nz/shop/products/height-safety/ascenders-descenders/petzl-rig-compact-self -braking-descender/ Page 2 E & OE | Prices are subject to change without notice | Copyright - All Rights Reserved 1633083992.
  • Technical Reference Manual for the Standardization of Geographical Names United Nations Group of Experts on Geographical Names

    Technical Reference Manual for the Standardization of Geographical Names United Nations Group of Experts on Geographical Names

    ST/ESA/STAT/SER.M/87 Department of Economic and Social Affairs Statistics Division Technical reference manual for the standardization of geographical names United Nations Group of Experts on Geographical Names United Nations New York, 2007 The Department of Economic and Social Affairs of the United Nations Secretariat is a vital interface between global policies in the economic, social and environmental spheres and national action. The Department works in three main interlinked areas: (i) it compiles, generates and analyses a wide range of economic, social and environmental data and information on which Member States of the United Nations draw to review common problems and to take stock of policy options; (ii) it facilitates the negotiations of Member States in many intergovernmental bodies on joint courses of action to address ongoing or emerging global challenges; and (iii) it advises interested Governments on the ways and means of translating policy frameworks developed in United Nations conferences and summits into programmes at the country level and, through technical assistance, helps build national capacities. NOTE The designations employed and the presentation of material in the present publication do not imply the expression of any opinion whatsoever on the part of the Secretariat of the United Nations concerning the legal status of any country, territory, city or area or of its authorities, or concerning the delimitation of its frontiers or boundaries. The term “country” as used in the text of this publication also refers, as appropriate, to territories or areas. Symbols of United Nations documents are composed of capital letters combined with figures. ST/ESA/STAT/SER.M/87 UNITED NATIONS PUBLICATION Sales No.
  • 1. Introduction

    1. Introduction

    ISO/IEC JTC1/SC2/WG2 N4162 Universal Multiple-Octet Coded Character Set International Organization for Standardization Organisation Internationale de Normalisation Международная организация по стандартизации Doc Type: Working Group Document Title: Revised proposal to encode Latin letters used in the Former Soviet Union Authors: Nurlan Joomagueldinov, Karl Pentzlin, Ilya Yevlampiev Status: Expert Contribution Action: For consideration by JTC1/SC2/WG2 and UTC Date: 2012-01-29 Supersedes: L2/11-360, WG2 N4162 – Two characters were added for Komi-Permyak (LATIN CAPITAL/SMALL LETTER ZE WITH DESCENDER). – The LATIN SMALL LETTER CAUCASIAN LONG S was disunified from U+017F LATIN SMALL LETTER LONG S (see the remark in the list of proposed characters at U+AB89). – Some issues raised in L2/11-422 are addressed in the text (especially, section 2.1.1 "Descender vs. cedilla" was added). Terminology used in this document: "Descender" refers to the specially formed appendage on letters like the one in the already encoded letter U+A790 LATIN CAPITAL LETTER N WITH DESCENDER. "Typographical descender" refers to the part of a letter below the baseline, thus resembling the term "descender" as used in typography. 1. Introduction In the wake of the October Revolution of 1917 in Russia, alphabetization of the people living in the then formed Soviet Union became an important point of the political agenda. At that time, some languages spoken in the Soviet Union had no standardized orthography at all, while others (especially in areas where the Islam was the predominant religion) used the Arabic script. As most of these orthographies did not reflect the phonetics of these languages very well, and as the Arabic script was considered unnecessarily difficult by some due to its structure, for most of the non-Slavic languages it was decided to design new orthographies from scratch.
  • ISO/IEC JTC1/SC2/WG2 N2714 L2/04-089R A. Administrative B

    ISO/IEC JTC1/SC2/WG2 N2714 L2/04-089R A. Administrative B

    ISO/IEC JTC1/SC2/WG2 N2714 L2/04-089R 2004-03-04 Universal Multiple-Octet Coded Character Set International Organization for Standardization Organisation Internationale de Normalisation еждународная организация по стандартизации Doc Type: Working Group Document Title: Proposal to add two Masoretic punctuation marks to the BMP of the UCS Source: Mark Shoulson, Peter Kirk, John Hudson, Michael Everson, and Peter Constable Status: Individual Contribution Action: For consideration by JTC1/SC2/WG2 and UTC Date: 2004-03-04 This document requests an additional character to be added to the UCS and contains the proposal summary form. A. Administrative 1. Title Proposal to add two Masoretic punctuation marks to the BMP of the UCS. 2. Requester’s name Mark Shoulson, Peter Kirk, John Hudson, Michael Everson, and Peter Constable 3. Requester type (Member body/Liaison/Individual contribution) Individual contribution. 4. Submission date 2004-03-04 5. Requester’s reference (if applicable) 6. Choose one of the following: 6a. This is a complete proposal Yes. 6b. More information will be provided later No. B. Technical – General 1. Choose one of the following: 1a. This proposal is for a new script (set of characters) No. Proposed name of script 1b. The proposal is for addition of character(s) to an existing block Yes. 1b. Name of the existing block Hebrew 2. Number of characters in proposal 2 3. Proposed category (see section II, Character Categories) Category B.1 4a. Proposed Level of Implementation (1, 2 or 3) (see clause 14, ISO/IEC 10646-1: 2000) Level 1. 4b. Is a rationale provided for the choice? Yes.
  • 5892 Cisco Category: Standards Track August 2010 ISSN: 2070-1721

    5892 Cisco Category: Standards Track August 2010 ISSN: 2070-1721

    Internet Engineering Task Force (IETF) P. Faltstrom, Ed. Request for Comments: 5892 Cisco Category: Standards Track August 2010 ISSN: 2070-1721 The Unicode Code Points and Internationalized Domain Names for Applications (IDNA) Abstract This document specifies rules for deciding whether a code point, considered in isolation or in context, is a candidate for inclusion in an Internationalized Domain Name (IDN). It is part of the specification of Internationalizing Domain Names in Applications 2008 (IDNA2008). Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5892. Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
  • Encoded Representations for Distinct Positional Uses of Hebrew Meteg Peter Constable, Microsoft Corporation 2004-09-13

    Encoded Representations for Distinct Positional Uses of Hebrew Meteg Peter Constable, Microsoft Corporation 2004-09-13

    Encoded representations for distinct positional uses of Hebrew Meteg Peter Constable, Microsoft Corporation 2004-09-13 In some uses of the Hebrew script, particularly for Biblical text, a variety of combining marks are used. One of these marks is meteg, encoded as U+05BD, HEBREW POINT METEG. Meteg frequently occurs together with other combining marks. When meteg co-occurs with another mark that occupies the same general space below the base character, different relative arrangements of meteg and these other marks are possible. In some uses it is considered necessary to specify these relative arrangements of meteg and other marks in the encoded representation. A proposal1 has been submitted to UTC for how these different positionings of meteg should be specified in encoded representations. This proposal makes use of the control characters COMBINING GRAPHEME JOINER (CGJ), ZERO WIDTH JOINER (ZWJ) and ZERO WIDTH NON-JOINER (ZWNJ). This public-review issue is soliciting feedback on this proposal and, in particular, on the proposed use of ZWJ and ZWNJ for distinguishing between the different positional uses of the meteg. The details in this case are somewhat complex. Familiarity with combining marks, canonical combining classes, canonical ordering and canonical equivalence is assumed. Some background information on those topics is provided in an appendix. 1. Background: meteg in combination with below-base vowel marks Biblical Hebrew text includes a number of marks used to annotate the text, which were introduced by Masoretic scholars over a thousand years ago. These marks include vowel points and a number of accentuation marks that indicate structural units of the text, serving to guide the reader or chanter.
  • Psftx-Debian-9.4/Uni3-Terminus14.Psf Linux Console Font Codechart

    Psftx-Debian-9.4/Uni3-Terminus14.Psf Linux Console Font Codechart

    psftx-debian-9.4/Uni3-Terminus14.psf Linux console font codechart Glyphs 0x000 to 0x0FF 0 1 2 3 4 5 6 7 8 9 A B C D E F 0x00_ 0x01_ 0x02_ 0x03_ 0x04_ 0x05_ 0x06_ 0x07_ 0x08_ 0x09_ 0x0A_ 0x0B_ 0x0C_ 0x0D_ 0x0E_ 0x0F_ Page 1 Glyphs 0x100 to 0x1FF 0 1 2 3 4 5 6 7 8 9 A B C D E F 0x10_ 0x11_ 0x12_ 0x13_ 0x14_ 0x15_ 0x16_ 0x17_ 0x18_ 0x19_ 0x1A_ 0x1B_ 0x1C_ 0x1D_ 0x1E_ 0x1F_ Page 2 Font information 0x013 U+049B CYRILLIC SMALL LETTER KA WITH DESCENDER Filename: psftx-debian-9.4/Uni3-Terminus14.p sf 0x014 U+00B6 PILCROW SIGN PSF version: 1 0x015 U+00A7 SECTION SIGN Glyph size: 8 × 14 pixels Glyph count: 512 0x016 U+04A2 CYRILLIC CAPITAL LETTER Unicode font: Yes (mapping table present) EN WITH DESCENDER 0x017 U+04A3 CYRILLIC SMALL LETTER Unicode mappings EN WITH DESCENDER 0x000 U+00A9 COPYRIGHT SIGN 0x018 U+2191 UPWARDS ARROW, U+25B2 BLACK UP-POINTING 0x001 U+00AE REGISTERED SIGN TRIANGLE, U+25B4 BLACK UP-POINTING 0x002 U+2122 TRADE MARK SIGN SMALL TRIANGLE 0x003 U+0104 LATIN CAPITAL LETTER A 0x019 U+2193 DOWNWARDS ARROW, WITH OGONEK U+25BC BLACK DOWN-POINTING 0x004 U+2666 BLACK DIAMOND SUIT, TRIANGLE, U+25C8 WHITE DIAMOND U+25BE BLACK DOWN-POINTING CONTAINING BLACK SMALL SMALL TRIANGLE DIAMOND, 0x01A U+2192 RIGHTWARDS ARROW, U+FFFD REPLACEMENT U+25B6 BLACK RIGHT-POINTING CHARACTER TRIANGLE, 0x005 U+0105 LATIN SMALL LETTER A U+25B8 BLACK RIGHT-POINTING WITH OGONEK SMALL TRIANGLE 0x006 U+0111 LATIN SMALL LETTER D 0x01B U+2190 LEFTWARDS ARROW, WITH STROKE U+25C0 BLACK LEFT-POINTING TRIANGLE, 0x007 U+2022 BULLET, U+25C2 BLACK LEFT-POINTING U+25CF
  • Kyrillische Schrift Für Den Computer

    Kyrillische Schrift Für Den Computer

    Hanna-Chris Gast Kyrillische Schrift für den Computer Benennung der Buchstaben, Vergleich der Transkriptionen in Bibliotheken und Standesämtern, Auflistung der Unicodes sowie Tastaturbelegung für Windows XP Inhalt Seite Vorwort ................................................................................................................................................ 2 1 Kyrillische Schriftzeichen mit Benennung................................................................................... 3 1.1 Die Buchstaben im Russischen mit Schreibschrift und Aussprache.................................. 3 1.2 Kyrillische Schriftzeichen anderer slawischer Sprachen.................................................... 9 1.3 Veraltete kyrillische Schriftzeichen .................................................................................... 10 1.4 Die gebräuchlichen Sonderzeichen ..................................................................................... 11 2 Transliterationen und Transkriptionen (Umschriften) .......................................................... 13 2.1 Begriffe zum Thema Transkription/Transliteration/Umschrift ...................................... 13 2.2 Normen und Vorschriften für Bibliotheken und Standesämter....................................... 15 2.3 Tabellarische Übersicht der Umschriften aus dem Russischen ....................................... 21 2.4 Transliterationen veralteter kyrillischer Buchstaben ....................................................... 25 2.5 Transliterationen bei anderen slawischen
  • How Was the Dageš in Biblical Hebrew Pronounced and Why Is It There? Geoffrey Khan

    How Was the Dageš in Biblical Hebrew Pronounced and Why Is It There? Geoffrey Khan

    1 pronounced and why is it בָּתִּ ים How was the dageš in Biblical Hebrew there? Geoffrey Khan houses’ is generally presented as an enigma in‘ בָּתִּ ים The dageš in the Biblical Hebrew plural form descriptions of the language. A wide variety of opinions about it have been expressed in Biblical Hebrew textbooks, reference grammars and the scholarly literature, but many of these are speculative without any direct or comparative evidence. One of the aims of this article is to examine the evidence for the way the dageš was pronounced in this word in sources that give us direct access to the Tiberian Masoretic reading tradition. A second aim is to propose a reason why the word has a dageš on the basis of comparative evidence within Biblical Hebrew reading traditions and other Semitic languages. בָּתִּיםבָּתִּ ים The Pronunciation of the Dageš in .1.0 The Tiberian vocalization signs and accents were created by the Masoretes of Tiberias in the early Islamic period to record an oral tradition of reading. There is evidence that this reading tradition had its roots in the Second Temple period, although some features of it appear to have developed at later periods. 1 The Tiberian reading was regarded in the Middle Ages as the most prestigious and authoritative tradition. On account of the authoritative status of the reading, great efforts were made by the Tiberian Masoretes to fix the tradition in a standardized form. There remained, nevertheless, some degree of variation in reading and sign notation in the Tiberian Masoretic school. By the end of the Masoretic period in the 10 th century C.E.
  • Alphabets, Letters and Diacritics in European Languages (As They Appear in Geography)

    Alphabets, Letters and Diacritics in European Languages (As They Appear in Geography)

    1 Vigleik Leira (Norway): [email protected] Alphabets, Letters and Diacritics in European Languages (as they appear in Geography) To the best of my knowledge English seems to be the only language which makes use of a "clean" Latin alphabet, i.d. there is no use of diacritics or special letters of any kind. All the other languages based on Latin letters employ, to a larger or lesser degree, some diacritics and/or some special letters. The survey below is purely literal. It has nothing to say on the pronunciation of the different letters. Information on the phonetic/phonemic values of the graphic entities must be sought elsewhere, in language specific descriptions. The 26 letters a, b, c, d, e, f, g, h, i, j, k, l, m, n, o, p, q, r, s, t, u, v, w, x, y, z may be considered the standard European alphabet. In this article the word diacritic is used with this meaning: any sign placed above, through or below a standard letter (among the 26 given above); disregarding the cases where the resulting letter (e.g. å in Norwegian) is considered an ordinary letter in the alphabet of the language where it is used. Albanian The alphabet (36 letters): a, b, c, ç, d, dh, e, ë, f, g, gj, h, i, j, k, l, ll, m, n, nj, o, p, q, r, rr, s, sh, t, th, u, v, x, xh, y, z, zh. Missing standard letter: w. Letters with diacritics: ç, ë. Sequences treated as one letter: dh, gj, ll, rr, sh, th, xh, zh.
  • Zap-Ext-Vga09.Psftx Linux Console Font Codechart

    Zap-Ext-Vga09.Psftx Linux Console Font Codechart

    zap-ext-vga09.psftx Linux console font codechart Glyphs 0x000 to 0x0FF 0 1 2 3 4 5 6 7 8 9 A B C D E F 0x00_ 0x01_ 0x02_ 0x03_ 0x04_ 0x05_ 0x06_ 0x07_ 0x08_ 0x09_ 0x0A_ 0x0B_ 0x0C_ 0x0D_ 0x0E_ 0x0F_ Page 1 Glyphs 0x100 to 0x1FF 0 1 2 3 4 5 6 7 8 9 A B C D E F 0x10_ 0x11_ 0x12_ 0x13_ 0x14_ 0x15_ 0x16_ 0x17_ 0x18_ 0x19_ 0x1A_ 0x1B_ 0x1C_ 0x1D_ 0x1E_ 0x1F_ Page 2 Font information 0x014 U+203A SINGLE RIGHT-POINTING ANGLE QUOTATION MARK Filename: zap-ext-vga09.psftx PSF version: 1 0x015 U+201C LEFT DOUBLE QUOTATION MARK, Glyph size: 8 × 9 pixels U+201F DOUBLE HIGH-REVERSED-9 Glyph count: 512 QUOTATION MARK Unicode font: Yes (mapping table present) 0x016 U+201D RIGHT DOUBLE QUOTATION MARK, Unicode mappings U+02EE MODIFIER LETTER DOUBLE 0x000 U+FFFD REPLACEMENT APOSTROPHE CHARACTER 0x017 U+201E DOUBLE LOW-9 0x001 U+03C0 GREEK SMALL LETTER PI QUOTATION MARK 0x002 U+2260 NOT EQUAL TO 0x018 U+2E42 DOUBLE LOW-REVERSED-9 QUOTATION MARK 0x003 U+2264 LESS-THAN OR EQUAL TO 0x019 U+2E41 REVERSED COMMA, 0x004 U+2265 GREATER-THAN OR EQUAL U+02CE MODIFIER LETTER LOW TO GRAVE ACCENT 0x005 U+25A0 BLACK SQUARE, 0x01A U+011E LATIN CAPITAL LETTER G U+25AC BLACK RECTANGLE, WITH BREVE U+25AE BLACK VERTICAL 0x01B U+011F LATIN SMALL LETTER G RECTANGLE, WITH BREVE U+25FC BLACK MEDIUM SQUARE, U+25FE BLACK MEDIUM SMALL 0x01C U+0130 LATIN CAPITAL LETTER I SQUARE, WITH DOT ABOVE U+2B1B BLACK LARGE SQUARE, 0x01D U+0131 LATIN SMALL LETTER U+220E END OF PROOF DOTLESS I 0x006 U+25C6 BLACK DIAMOND, 0x01E U+015E LATIN CAPITAL LETTER S U+2666 BLACK DIAMOND SUIT, WITH CEDILLA
  • Marathon County Environmental Resources Committee Agenda

    Marathon County Environmental Resources Committee Agenda

    MARATHON COUNTY ENVIRONMENTAL RESOURCES COMMITTEE AGENDA Date & Time of Meeting: Tuesday, February 2, 2021 at 3:00 p.m. Meeting Location: 212 River Drive, Room 5 Wausau 54403 Committee Members: Jacob Langenhahn - Chair ; Sara Guild, -Vice-chair; Rick Seefeldt, Allen Drabek, Bill Conway, Randy Fifrick, Arnold Schlei, Dave Oberbeck, Eric Vogel - FSA Member, Marilyn Bhend – WI Towns & Villages Association (non-voting member) Marathon County Mission Statement: Marathon County Government serves people by leading, coordinating, and providing county, regional, and statewide initiatives. It directly or in cooperation with other public and private partners provides services and creates opportunities that make Marathon County and the surrounding area a preferred place to live, work, visit, and do business. (Last updated 12-20-05). Environmental Resources Committee Mission Statement: Provide leadership for the implementation of the County Strategic Plan, monitoring outcomes, reviewing and recommending to the County Board policies related to environmental resource initiatives of Marathon County. (Revised: 04/17/12) Strategic Plan Goals 2018 - 2022: Objective 5.2 - Promote sound land use decisions that conserve and preserve natural resources in decisions with economic development and growth. Objective 6.3 - Protect and enhance the quantity and quality of potable groundwater and potable surface water supplies. The meeting site identified above will be open to the public. However, due to the COVID-19 pandemic and associated public health directives, Marathon County encourages (Committee/Board/Commission) members and the public to attend this meeting remotely. To this end, instead of attendance in person, (Committee/Board/Commission) members and the public may attend this meeting by telephone conference.