Miscellaneous Technical Range: 2300–23FF the Unicode Standard
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Edit Bibliographic Records
OCLC Connexion Browser Guides Edit Bibliographic Records Last updated: May 2014 6565 Kilgour Place, Dublin, OH 43017-3395 www.oclc.org Revision History Date Section title Description of changes May 2014 All Updated information on how to open the diacritic window. The shortcut key is no longer available. May 2006 1. Edit record: basics Minor updates. 5. Insert diacritics Revised to update list of bar syntax character codes to reflect and special changes in character names and to add newly supported characters characters. November 2006 1. Edit record: basics Minor updates. 2. Editing Added information on guided editing for fields 541 and 583, techniques, template commonly used when cataloging archival materials. view December 2006 1. Edit record: basics Updated to add information about display of WorldCat records that contain non-Latin scripts.. May 2007 4. Validate record Revised to document change in default validation level from None to Structure. February 2012 2 Editing techniques, Series added entry fields 800, 810, 811, 830 can now be used to template view insert data from a “cited” record for a related series item. Removed “and DDC” from Control All commands. DDC numbers are no longer controlled in Connexion. April 2012 2. Editing New section on how to use the prototype OCLC Classify service. techniques, template view September 2012 All Removed all references to Pathfinder. February 2013 All Removed all references to Heritage Printed Book. April 2013 All Removed all references to Chinese Name Authority © 2014 OCLC Online Computer Library Center, Inc. 6565 Kilgour Place Dublin, OH 43017-3395 USA The following OCLC product, service and business names are trademarks or service marks of OCLC, Inc.: CatExpress, Connexion, DDC, Dewey, Dewey Decimal Classification, OCLC, WorldCat, WorldCat Resource Sharing and “The world’s libraries. -
Writing Mathematical Expressions in Plain Text – Examples and Cautions Copyright © 2009 Sally J
Writing Mathematical Expressions in Plain Text – Examples and Cautions Copyright © 2009 Sally J. Keely. All Rights Reserved. Mathematical expressions can be typed online in a number of ways including plain text, ASCII codes, HTML tags, or using an equation editor (see Writing Mathematical Notation Online for overview). If the application in which you are working does not have an equation editor built in, then a common option is to write expressions horizontally in plain text. In doing so you have to format the expressions very carefully using appropriately placed parentheses and accurate notation. This document provides examples and important cautions for writing mathematical expressions in plain text. Section 1. How to Write Exponents Just as on a graphing calculator, when writing in plain text the caret key ^ (above the 6 on a qwerty keyboard) means that an exponent follows. For example x2 would be written as x^2. Example 1a. 4xy23 would be written as 4 x^2 y^3 or with the multiplication mark as 4*x^2*y^3. Example 1b. With more than one item in the exponent you must enclose the entire exponent in parentheses to indicate exactly what is in the power. x2n must be written as x^(2n) and NOT as x^2n. Writing x^2n means xn2 . Example 1c. When using the quotient rule of exponents you often have to perform subtraction within an exponent. In such cases you must enclose the entire exponent in parentheses to indicate exactly what is in the power. x5 The middle step of ==xx52− 3 must be written as x^(5-2) and NOT as x^5-2 which means x5 − 2 . -
Assessment of Options for Handling Full Unicode Character Encodings in MARC21 a Study for the Library of Congress
1 Assessment of Options for Handling Full Unicode Character Encodings in MARC21 A Study for the Library of Congress Part 1: New Scripts Jack Cain Senior Consultant Trylus Computing, Toronto 1 Purpose This assessment intends to study the issues and make recommendations on the possible expansion of the character set repertoire for bibliographic records in MARC21 format. 1.1 “Encoding Scheme” vs. “Repertoire” An encoding scheme contains codes by which characters are represented in computer memory. These codes are organized according to a certain methodology called an encoding scheme. The list of all characters so encoded is referred to as the “repertoire” of characters in the given encoding schemes. For example, ASCII is one encoding scheme, perhaps the one best known to the average non-technical person in North America. “A”, “B”, & “C” are three characters in the repertoire of this encoding scheme. These three characters are assigned encodings 41, 42 & 43 in ASCII (expressed here in hexadecimal). 1.2 MARC8 "MARC8" is the term commonly used to refer both to the encoding scheme and its repertoire as used in MARC records up to 1998. The ‘8’ refers to the fact that, unlike Unicode which is a multi-byte per character code set, the MARC8 encoding scheme is principally made up of multiple one byte tables in which each character is encoded using a single 8 bit byte. (It also includes the EACC set which actually uses fixed length 3 bytes per character.) (For details on MARC8 and its specifications see: http://www.loc.gov/marc/.) MARC8 was introduced around 1968 and was initially limited to essentially Latin script only. -
Dictation Presentation.Pptx
Dictaon using Apple Devices Presentaon October 10, 2013 Trudy Downs Operang Systems • iOS6 • iOS7 • Mountain Lion (OS X10.8) Devices • iPad 3 or iPad mini • iPod 4 • iPhone 4s, 5 or 5c or 5s • Desktop running Mountain Lion • Laptop running Mountain Lion Dictaon Shortcut Words • Shortcut WordsDictaon includes many voice “shortcuts” that allows you to manipulate the text and insert symbols while you are speaking. Here’s a list of those shortcuts that you can use: - “new line” is like pressing Return on your keyboard - “new paragraph” creates a new paragraph - “cap” capitalizes the next spoken word - “caps on/off” capitalizes the spoken sec&on of text - “all caps” makes the next spoken word all caps - “all caps on/off” makes the spoken sec&on of text all caps - “no caps” makes the next spoken word lower case - “no caps on/off” makes the spoken sec&on of text lower case - “space bar” prevents a hyphen from appearing in a normally hyphenated word - “no space” prevents a space between words - “no space on/off” to prevent a sec&on of text from having spaces between words More Dictaon Shortcuts • - “period” or “full stop” places a period at the end of a sentence - “dot” places a period anywhere, including between words - “point” places a point between numbers, not between words - “ellipsis” or “dot dot dot” places an ellipsis in your wri&ng - “comma” places a comma - “double comma” places a double comma (,,) - “quote” or “quotaon mark” places a quote mark (“) - “quote ... end quote” places quotaon marks around the text spoken between - “apostrophe” -
The Unicode Standard 5.2 Code Charts
Miscellaneous Technical Range: 2300–23FF The Unicode Standard, Version 5.2 This file contains an excerpt from the character code tables and list of character names for The Unicode Standard, Version 5.2. Characters in this chart that are new for The Unicode Standard, Version 5.2 are shown in conjunction with any existing characters. For ease of reference, the new characters have been highlighted in the chart grid and in the names list. This file will not be updated with errata, or when additional characters are assigned to the Unicode Standard. See http://www.unicode.org/errata/ for an up-to-date list of errata. See http://www.unicode.org/charts/ for access to a complete list of the latest character code charts. See http://www.unicode.org/charts/PDF/Unicode-5.2/ for charts showing only the characters added in Unicode 5.2. See http://www.unicode.org/Public/5.2.0/charts/ for a complete archived file of character code charts for Unicode 5.2. Disclaimer These charts are provided as the online reference to the character contents of the Unicode Standard, Version 5.2 but do not provide all the information needed to fully support individual scripts using the Unicode Standard. For a complete understanding of the use of the characters contained in this file, please consult the appropriate sections of The Unicode Standard, Version 5.2, online at http://www.unicode.org/versions/Unicode5.2.0/, as well as Unicode Standard Annexes #9, #11, #14, #15, #24, #29, #31, #34, #38, #41, #42, and #44, the other Unicode Technical Reports and Standards, and the Unicode Character Database, which are available online. -
TS 126 234 V5.6.0 (2003-09) Technical Specification
ETSI TS 126 234 V5.6.0 (2003-09) Technical Specification Universal Mobile Telecommunications System (UMTS); Transparent end-to-end streaming service; Protocols and codecs (3GPP TS 26.234 version 5.6.0 Release 5) 3GPP TS 26.234 version 5.6.0 Release 5 1 ETSI TS 126 234 V5.6.0 (2003-09) Reference RTS/TSGS-0426234v560 Keywords UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, send your comment to: [email protected] Copyright Notification No part may be reproduced except as authorized by written permission. -
List of Approved Special Characters
List of Approved Special Characters The following list represents the Graduate Division's approved character list for display of dissertation titles in the Hooding Booklet. Please note these characters will not display when your dissertation is published on ProQuest's site. To insert a special character, simply hold the ALT key on your keyboard and enter in the corresponding code. This is only for entering in a special character for your title or your name. The abstract section has different requirements. See abstract for more details. Special Character Alt+ Description 0032 Space ! 0033 Exclamation mark '" 0034 Double quotes (or speech marks) # 0035 Number $ 0036 Dollar % 0037 Procenttecken & 0038 Ampersand '' 0039 Single quote ( 0040 Open parenthesis (or open bracket) ) 0041 Close parenthesis (or close bracket) * 0042 Asterisk + 0043 Plus , 0044 Comma ‐ 0045 Hyphen . 0046 Period, dot or full stop / 0047 Slash or divide 0 0048 Zero 1 0049 One 2 0050 Two 3 0051 Three 4 0052 Four 5 0053 Five 6 0054 Six 7 0055 Seven 8 0056 Eight 9 0057 Nine : 0058 Colon ; 0059 Semicolon < 0060 Less than (or open angled bracket) = 0061 Equals > 0062 Greater than (or close angled bracket) ? 0063 Question mark @ 0064 At symbol A 0065 Uppercase A B 0066 Uppercase B C 0067 Uppercase C D 0068 Uppercase D E 0069 Uppercase E List of Approved Special Characters F 0070 Uppercase F G 0071 Uppercase G H 0072 Uppercase H I 0073 Uppercase I J 0074 Uppercase J K 0075 Uppercase K L 0076 Uppercase L M 0077 Uppercase M N 0078 Uppercase N O 0079 Uppercase O P 0080 Uppercase -
Sample Chapter 3
108_GILLAM.ch03.fm Page 61 Monday, August 19, 2002 1:58 PM 3 Architecture: Not Just a Pile of Code Charts f you’re used to working with ASCII or other similar encodings designed I for European languages, you’ll find Unicode noticeably different from those other standards. You’ll also find that when you’re dealing with Unicode text, various assumptions you may have made in the past about how you deal with text don’t hold. If you’ve worked with encodings for other languages, at least some characteristics of Unicode will be familiar to you, but even then, some pieces of Unicode will be unfamiliar. Unicode is more than just a big pile of code charts. To be sure, it includes a big pile of code charts, but Unicode goes much further. It doesn’t just take a bunch of character forms and assign numbers to them; it adds a wealth of infor- mation on what those characters mean and how they are used. Unlike virtually all other character encoding standards, Unicode isn’t de- signed for the encoding of a single language or a family of closely related lan- guages. Rather, Unicode is designed for the encoding of all written languages. The current version doesn’t give you a way to encode all written languages (and in fact, this concept is such a slippery thing to define that it probably never will), but it does provide a way to encode an extremely wide variety of lan- guages. The languages vary tremendously in how they are written, so Unicode must be flexible enough to accommodate all of them. -
Symbol Meaning Example Delete Close up Delete and Close
Symbol Meaning Example delete close up delete and close up caret insert a space space evenly let stand transpose used to separate two or more marks and often as a concluding stroke at the end of an insertion set farther to the left set farther to the right set as ligature (such as ) align horizontally align vertically broken character indent or insert em quad space begin a new paragraph spell out set in CAPITALS set in SMALL CAPITALS set in lowercase set in italic set in roman set in boldface hyphen multi-colored en dash 1965–72 em (or long) dash Now—at last!—we know. superscript or superior subscript or inferior centered comma apostrophe period semicolon colon quotation marks parentheses brackets query to author: has this been set as intended? push down a work-up turn over an inverted letter wrong font insert a comma apostrophe or single quotation mark insert something use double quotation marks use a period here delete transpose elements close up this space a space needed here begin new paragraph no paragraph Common Proofreading Abbreviations (The abbreviation would appear in the margin, probably with a line or arrow pointing to the offending element.) Abbreviation Meaning Example Ab a faulty abbreviation She had earned a Phd along with her M.D. agreement problem: Agr subject/verb or The piano as well as the guitar need tuning. See also P/A and S/V The student lost their book. pronoun/antecedent awkward expression The storm had the effect of causing Awk or construction millions of dollars in damage. -
Using Lex In
Using Lex or Flex Prof. James L. Frankel Harvard University Version of 1:07 PM 26-Sep-2016 Copyright © 2016, 2015 James L. Frankel. All rights reserved. Lex Regular Expressions (1 of 4) • Special characters are: – + (plus sign) – \ (back slash) – ? (question mark) – " (double quote) – { (open brace) – . (period) – } (close brace) – ^ (caret or up arrow) – | (vertical bar) – $ (dollar sign) – / (slash) – [ (open bracket) – - (dash or hyphen) – ] (close bracket) – ( (open parenthesis) – * (asterisk) – ) (close parenthesis) Lex Regular Expressions (2 of 4) • c matches the single non-operator char c • \c matches the character c • "s" matches the string s • . matches any character except newline • ^ matches beginning of line • $ matches end of line • [s] matches any one character in s • [^s] matches any one character not in s Lex Regular Expressions (3 of 4) • r* matches zero or more strings matching r • r+ matches one or more strings matching r • r? matches zero or one strings matching r • r{m, n} matches between m and n occurrences of r • r1r2 matches r1 followed by r2 • r1|r2 matches either r1 or r2 • (r) matches r • r1/r2 matches r1 when followed by r2 • {name} matches the regex defined by name Lex Regular Expressions (4 of 4) • Within square brackets, referred to as a character class, all operators are ignored except for backslash, hyphen (dash), and caret • Within a character class, backslash will introduce an escape code • Within a character class, ranges of characters are allowed by using hyphen – a-zA-Z • Within a character class, -
Unified English Braille (UEB) General Symbols and Indicators
Unified English Braille (UEB) General Symbols and Indicators UEB Rulebook Section 3 Published by International Council on English Braille (ICEB) space (see 3.23) ⠣ opening braille grouping indicator (see 3.4) ⠹ first transcriber‐defined print symbol (see 3.26) ⠫ shape indicator (see 3.22) ⠳ arrow indicator (see 3.2) ⠳⠕ → simple right pointing arrow (east) (see 3.2) ⠳⠩ ↓ simple down pointing arrow (south) (see 3.2) ⠳⠪ ← simple left pointing arrow (west) (see 3.2) ⠳⠬ ↑ simple up pointing arrow (north) (see 3.2) ⠒ ∶ ratio (see 3.17) ⠒⠒ ∷ proportion (see 3.17) ⠢ subscript indicator (see 3.24) ⠶ ′ prime (see 3.11 and 3.15) ⠶⠶ ″ double prime (see 3.11 and 3.15) ⠔ superscript indicator (see 3.24) ⠼⠡ ♮ natural (see 3.18) ⠼⠣ ♭ flat (see 3.18) ⠼⠩ ♯ sharp (see 3.18) ⠼⠹ second transcriber‐defined print symbol (see 3.26) ⠜ closing braille grouping indicator (see 3.4) ⠈⠁ @ commercial at sign (see 3.7) ⠈⠉ ¢ cent sign (see 3.10) ⠈⠑ € euro sign (see 3.10) ⠈⠋ ₣ French franc sign (see 3.10) ⠈⠇ £ pound sign (pound sterling) (see 3.10) ⠈⠝ ₦ naira sign (see 3.10) ⠈⠎ $ dollar sign (see 3.10) ⠈⠽ ¥ yen sign (Yuan sign) (see 3.10) ⠈⠯ & ampersand (see 3.1) ⠈⠣ < less‐than sign (see 3.17) ⠈⠢ ^ caret (3.6) ⠈⠔ ~ tilde (swung dash) (see 3.25) ⠈⠼⠹ third transcriber‐defined print symbol (see 3.26) ⠈⠜ > greater‐than sign (see 3.17) ⠈⠨⠣ opening transcriber’s note indicator (see 3.27) ⠈⠨⠜ closing transcriber’s note indicator (see 3.27) ⠈⠠⠹ † dagger (see 3.3) ⠈⠠⠻ ‡ double dagger (see 3.3) ⠘⠉ © copyright sign (see 3.8) ⠘⠚ ° degree sign (see 3.11) ⠘⠏ ¶ paragraph sign (see 3.20) -
Team MARKUP Quality Control Checklist
Team MARKUP Quality Control Checklist Team MARKUP Quality Control Checklist Key Points Main Issues Specific Issues Key Points 1. Don’t just look over this checklist--it contains key points from the GoogleDoc and schema, but not all information. be sure to read over the new additions to the GoogleDoc and the SGA schema as well before finishing your quality control work. 2. If you added questions to the GoogleDoc, did you go back and make changes to these areas after your question was answered? 3. Sometimes people answered questions, but their answers were incorrect (it happens). Please also read through the chart and make sure your comments don’t have other comments correcting them. 4. Did you validate your work? For each of your XML files, go to Document > Validate > Validate while in Oxygen. Look at the bottom of the page for a list of errors the validator found. Your encoding is not correct until you can validate the file and see no errors in that list. 5. Did you push your work correctly and to the right place? If you can see your name and update text next to the file on this page, you’re golden: https://github.com/umd-mith/sg-data/tree/master/data/eng738t/tei Main Issues 1. Almost every tag should have a closing tag (e.g. <add place=”superlinear”>some text</add>). The milestone tag is one exception. 2. Do not use <p>. 3. Stuff that’s in blue font in the transcription files is in Percy’s hand! 4. For any symbol (ampersand, dash, plus mark, etc.), there’s a proper encoding (see next item for some of these).