10646-2CD US Comment
Total Page：16
File Type：pdf, Size：1020Kb
Load more
Recommended publications
-
Chapter 6: Trademark
Trademark 6 Trademark 5 The Trade-Mark Cases ............... 5 A Subject Maer ........................ 6 1 Use as a Mark ...................... 6 Lanham Act § 45 (“trademark”) ......... 6 In re Schmidt .................... 6 Drug Stamps Problem .............. 9 2 Distinctiveness ..................... 9 a Words and Phrases ................ 9 Zatarains, Inc. v. Oak Grove Smokehouse, Inc. .. 9 Innovation Ventures, LLC v. N.V.E., Inc. ..... 15 TMEP § 1202 .................... 16 Elliot v. Google Inc. ................. 16 TMEP § 1209.03 .................. 23 b Designs ....................... 24 Star Industries, Inc. v. Bacardi & Co. Ltd. ..... 24 Melting Bad Problem ............... 26 B Ownership .......................... 27 1 Priority at Common Law . 27 Galt House Inc. v. Home Supply Company .... 27 United Drug Co. v. Theodore Rectanus Co. .... 29 Planetary Motion, Inc. v. Techsplosion, Inc. .... 32 Dudley v. HealthSource Chiropractic, Inc. ..... 34 Bilgewater Bill’s Problem ............. 36 2 Federal Registration . 36 a Registration .................... 36 Lanham Act §§ 1(a), 7 ............... 36 Burger King of Florida, Inc. v. Hoots ....... 37 Bilgewater Bill’s Problem, Redux ........ 38 b Intent-to-Use Applications . 38 Lanham Act § 1(b) ................. 38 Kelly Services, Inc. v. Creative Harbor, LLC [I] .. 39 Kelly Services, Inc. v. Creative Harbor, LLC [II] . 43 Bilgewater Bill’s Problem, Re-Redux ...... 44 3 Collaborations ..................... 44 Boogie Kings v. Guillory .............. 44 TRADEMARK 2 New Jersey Truth in Music Act -
Unicode Request for Cyrillic Modifier Letters Superscript Modifiers
Unicode request for Cyrillic modifier letters L2/21-107 Kirk Miller, [email protected] 2021 June 07 This is a request for spacing superscript and subscript Cyrillic characters. It has been favorably reviewed by Sebastian Kempgen (University of Bamberg) and others at the Commission for Computer Supported Processing of Medieval Slavonic Manuscripts and Early Printed Books. Cyrillic-based phonetic transcription uses superscript modifier letters in a manner analogous to the IPA. This convention is widespread, found in both academic publication and standard dictionaries. Transcription of pronunciations into Cyrillic is the norm for monolingual dictionaries, and Cyrillic rather than IPA is often found in linguistic descriptions as well, as seen in the illustrations below for Slavic dialectology, Yugur (Yellow Uyghur) and Evenki. The Great Russian Encyclopedia states that Cyrillic notation is more common in Russian studies than is IPA (‘Transkripcija’, Bol’šaja rossijskaja ènciplopedija, Russian Ministry of Culture, 2005–2019). Unicode currently encodes only three modifier Cyrillic letters: U+A69C ⟨ꚜ⟩ and U+A69D ⟨ꚝ⟩, intended for descriptions of Baltic languages in Latin script but ubiquitous for Slavic languages in Cyrillic script, and U+1D78 ⟨ᵸ⟩, used for nasalized vowels, for example in descriptions of Chechen. The requested spacing modifier letters cannot be substituted by the encoded combining diacritics because (a) some authors contrast them, and (b) they themselves need to be able to take combining diacritics, including diacritics that go under the modifier letter, as in ⟨ᶟ̭̈⟩BA . (See next section and e.g. Figure 18. ) In addition, some linguists make a distinction between spacing superscript letters, used for phonetic detail as in the IPA tradition, and spacing subscript letters, used to denote phonological concepts such as archiphonemes. -
Dear Supervisors- Attached Please Find Our Letter of Opposition to the SCA Ordinance for Sleepy Hollow As Drafted by Our Attorne
From: Andrea Taber To: Rice, Katie; Kinsey, Steven; Adams, Susan; Arnold, Judy; Sears, Kathrin Cc: Dan Stein; Thorsen, Suzanne; Lai, Thomas Subject: Sleepy Hollow Homeowners Association Letter of Oppostion to the SCA Ordinance Date: Wednesday, May 22, 2013 8:12:53 PM Attachments: Document4.docx Dear Supervisors- Attached please find our letter of opposition to the SCA Ordinance for Sleepy Hollow as drafted by our attorney Neil Moran of Freitas McCarthy MacMahon & Keating, LLP. Sleepy Hollow Homeowners Association May 3, 2013 Board of Supervisors of Marin County 3501 Civil Center Drive San Rafael, CA 94903-4157 Re: Stream Conservation Area (SCA) Proposed Amendments to the Development Code Honorable Members of the Board of Supervisors: INTRODUCTION The Sleepy Hollow Homes Association (SHHA) objects to the proposed changes to Chapters 22.33 (Stream Protection) and 22.63 (Stream Conservation Area Permit) as they would apply to the residents of the unincorporated portion of San Anselmo known as Sleepy Hollow. We ask that the County exempt and/or delay implementation of any changes to Chapters 22.33 and 22.63 as to the city-centered corridor streams, including Sleepy Hollow. The SHHA supports implementation of the proposed amendments to the San Geronimo Valley, to protect wildlife habitat in streams where Coho Salmon currently exist. The SHHA supports regulations to ensure the health and survival of the species in these areas. The SHHA recognizes the urgency of this matter to the San Geronimo Valley, both for the survival of the endangered and declining Coho population and for the property rights of the affected residents who are currently subject to a building moratorium. -
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. -
Handwriting Recognition in Indian Regional Scripts: a Survey of Offline Techniques
1 Handwriting Recognition in Indian Regional Scripts: A Survey of Offline Techniques UMAPADA PAL, Indian Statistical Institute RAMACHANDRAN JAYADEVAN, Pune Institute of Computer Technology NABIN SHARMA, Indian Statistical Institute Offline handwriting recognition in Indian regional scripts is an interesting area of research as almost 460 million people in India use regional scripts. The nine major Indian regional scripts are Bangla (for Bengali and Assamese languages), Gujarati, Kannada, Malayalam, Oriya, Gurumukhi (for Punjabi lan- guage), Tamil, Telugu, and Nastaliq (for Urdu language). A state-of-the-art survey about the techniques available in the area of offline handwriting recognition (OHR) in Indian regional scripts will be of a great aid to the researchers in the subcontinent and hence a sincere attempt is made in this article to discuss the advancements reported in this regard during the last few decades. The survey is organized into different sections. A brief introduction is given initially about automatic recognition of handwriting and official re- gional scripts in India. The nine regional scripts are then categorized into four subgroups based on their similarity and evolution information. The first group contains Bangla, Oriya, Gujarati and Gurumukhi scripts. The second group contains Kannada and Telugu scripts and the third group contains Tamil and Malayalam scripts. The fourth group contains only Nastaliq script (Perso-Arabic script for Urdu), which is not an Indo-Aryan script. Various feature extraction and classification techniques associated with the offline handwriting recognition of the regional scripts are discussed in this survey. As it is important to identify the script before the recognition step, a section is dedicated to handwritten script identification techniques. -
Sinitic Language and Script in East Asia: Past and Present
SINO-PLATONIC PAPERS Number 264 December, 2016 Sinitic Language and Script in East Asia: Past and Present edited by Victor H. Mair Victor H. Mair, Editor Sino-Platonic Papers Department of East Asian Languages and Civilizations University of Pennsylvania Philadelphia, PA 19104-6305 USA [email protected] www.sino-platonic.org SINO-PLATONIC PAPERS FOUNDED 1986 Editor-in-Chief VICTOR H. MAIR Associate Editors PAULA ROBERTS MARK SWOFFORD ISSN 2157-9679 (print) 2157-9687 (online) SINO-PLATONIC PAPERS is an occasional series dedicated to making available to specialists and the interested public the results of research that, because of its unconventional or controversial nature, might otherwise go unpublished. The editor-in-chief actively encourages younger, not yet well established, scholars and independent authors to submit manuscripts for consideration. Contributions in any of the major scholarly languages of the world, including romanized modern standard Mandarin (MSM) and Japanese, are acceptable. In special circumstances, papers written in one of the Sinitic topolects (fangyan) may be considered for publication. Although the chief focus of Sino-Platonic Papers is on the intercultural relations of China with other peoples, challenging and creative studies on a wide variety of philological subjects will be entertained. This series is not the place for safe, sober, and stodgy presentations. Sino- Platonic Papers prefers lively work that, while taking reasonable risks to advance the field, capitalizes on brilliant new insights into the development of civilization. Submissions are regularly sent out to be refereed, and extensive editorial suggestions for revision may be offered. Sino-Platonic Papers emphasizes substance over form. -
Old Cyrillic in Unicode*
Old Cyrillic in Unicode* Ivan A Derzhanski Institute for Mathematics and Computer Science, Bulgarian Academy of Sciences [email protected] The current version of the Unicode Standard acknowledges the existence of a pre- modern version of the Cyrillic script, but its support thereof is limited to assigning code points to several obsolete letters. Meanwhile mediæval Cyrillic manuscripts and some early printed books feature a plethora of letter shapes, ligatures, diacritic and punctuation marks that want proper representation. (In addition, contemporary editions of mediæval texts employ a variety of annotation signs.) As generally with scripts that predate printing, an obvious problem is the abundance of functional, chronological, regional and decorative variant shapes, the precise details of whose distribution are often unknown. The present contents of the block will need to be interpreted with Old Cyrillic in mind, and decisions to be made as to which remaining characters should be implemented via Unicode’s mechanism of variation selection, as ligatures in the typeface, or as code points in the Private space or the standard Cyrillic block. I discuss the initial stage of this work. The Unicode Standard (Unicode 4.0.1) makes a controversial statement: The historical form of the Cyrillic alphabet is treated as a font style variation of modern Cyrillic because the historical forms are relatively close to the modern appearance, and because some of them are still in modern use in languages other than Russian (for example, U+0406 “I” CYRILLIC CAPITAL LETTER I is used in modern Ukrainian and Byelorussian). Some of the letters in this range were used in modern typefaces in Russian and Bulgarian. -
Nets Oо Subgroups in Locally Compact Groups
ANNALES SOCIETATIS MATHEMATICAE POLONAE Series I: COMMENTATIONES MATHEMATICAE XX (1978) ROCZNIKI POLSKIEGO TOWARZYSTWA MATEMATYCZNEGO Séria I: PRACE MATEMATYCZNE XX (1978) J ose L. B u b io * (Princeton) Nets oî subgroups in locally compact groups Abstract. The approximation of the integral of a function / in a locally compact group by average functions / # defined by subgroups H of the group is studied in some detail, with other related questions and a few applications. 0. Introduction. An old well-known result, due to Kolmogorov, states that given a function f e L1 (T) =и([0,1)), the functions /«0*0 = —n J-JУ /\ р + П— I, n = 1 >2,3,..., i converge in L1 to I = J f(x)dx (see [6.]; УП.4 for a related result). More 0 precisely, if cop denotes the modulus of continuity in L P1 one finds (see [4] or [5]) (0.1) !l/„~i\\r < <opif-, -i-j (1 < P s; со). On the other hand, Jessen proved later (see [2]) that (0.2) /2n (*)->! (a.e.). This type of results also holds if we replace the torus T — [0, 1 ) by the real line B, defining for each / e Ll (B) f r(x) = r j£ f(x + hr) (r> 0) h e Z and making r->0. The convergence in L1 or Lp is local in this case. Our aim is to give a treatment of these questions in the general setting of locally compact groups. Besults of the type (0.1) are Theorems 2,3 and 4 below, and Corollary 3, while Corollary 4 provides the natural extension of Jessen’s result (0.2). -
Learning Cyrillic
LEARNING CYRILLIC Question: If there is no equivalent letter in the Cyrillic alphabet for the Roman "J" or "H" how do you transcribe good German names like Johannes, Heinrich, Wilhelm, etc. I heard one suggestion that Johann was written as Ivan and that the "h" was replaced with a "g". Can you give me a little insight into what you have found? In researching would I be looking for the name Ivan rather than Johann? One must always think phonetic, that is, think how a name is pronounced in German, and how does the Russian Cyrillic script produce that sound? JOHANNES. The Cyrillic spelling begins with the letter “I – eye”, but pronounced “eee”, so we have phonetically “eee-o-hann” which sounds like “Yo-hann”. You can see it better in typeface – Иоганн , which letter for letter reads as “I-o-h-a-n-n”. The modern Typeface script is radically different than the old hand-written Cyrillic script. Use the guide which I sent to you. Ivan is the Russian equivalent of Johann, and it pops up occasionally in Church records. JOSEPH / JOSEF. Listen to the way the name is pronounced in German – “yo-sef”, also “yo-sif”. That “yo” sound is produced by the Cyrillic script letters “I” and “o”. Again you can see it in the typeface. Иосеф and also Иосиф. And sometimes Joseph appears as , transliterated as O-s-i-p. Similar to all languages and scripts, Cyrillic spellings are not consistent. The “a” ending indicates a male name. JAKOB. There is no “Jay” sound in the German language. -
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. -
Jtc1/Sc2/Wg2 N3427 L2/08-132
JTC1/SC2/WG2 N3427 L2/08-132 2008-04-08 Universal Multiple-Octet Coded Character Set International Organization for Standardization Organisation Internationale de Normalisation Международная организация по стандартизации Doc Type: Working Group Document Title: Proposal to encode 39 Unified Canadian Aboriginal Syllabics in the UCS Source: Michael Everson and Chris Harvey Status: Individual Contribution Action: For consideration by JTC1/SC2/WG2 and UTC Date: 2008-04-08 1. Summary. This document requests 39 additional characters to be added to the UCS and contains the proposal summary form. 1. Syllabics hyphen (U+1400). Many Aboriginal Canadian languages use the character U+1428 CANADIAN SYLLABICS FINAL SHORT HORIZONTAL STROKE, which looks like the Latin script hyphen. Algonquian languages like western dialects of Cree, Oji-Cree, western and northern dialects of Ojibway employ this character to represent /tʃ/, /c/, or /j/, as in Plains Cree ᐊᓄᐦᐨ /anohc/ ‘today’. In Athabaskan languages, like Chipewyan, the sound is /d/ or an alveolar onset, as in Sayisi Dene ᐨᕦᐣᐨᕤ /t’ąt’ú/ ‘how’. To avoid ambiguity between this character and a line-breaking hyphen, a SYLLABICS HYPHEN was developed which resembles an equals sign. Depending on the typeface, the width of the syllabics hyphen can range from a short ᐀ to a much longer ᐀. This hyphen is line-breaking punctuation, and should not be confused with the Blackfoot syllable internal-w final proposed for U+167F. See Figures 1 and 2. 2. DHW- additions for Woods Cree (U+1677..U+167D). ᙷᙸᙹᙺᙻᙼᙽ/ðwē/ /ðwi/ /ðwī/ /ðwo/ /ðwō/ /ðwa/ /ðwā/. The basic syllable structure in Cree is (C)(w)V(C)(C). -
Typotheque North American Syllabics Proposed Revisions to The
Typotheque Prepared by Kevin King Typotheque [email protected] www.typotheque.com 04/06/21 North American Syllabics Proposed revisions to the representative characters of the Unified Canadian Aboriginal Syllabics code charts Typotheque Proposed representative character revisions of the Unified Canadian Aboriginal Syllabics 2 CONTENTS 1 Summary of proposed character revisions 3 2 Revisions for Carrier 9 3 Revisions for Sayisi 36 4 Revisions for Ojibway 46 Bibliography 52 Acknowledgements 54 Typotheque Proposed representative character revisions of the Unified Canadian Aboriginal Syllabics 3 1 Summary of proposed character revisions The following proposal requests 120 revisions to the representative char- acters in the official code charts of Unified Canadian Aboriginal Syllabics main and extended blocks. The proposed characters for revision have been summarized below with representative glyphs and corresponding character names with annotations where applicable. Additionally, revised code charts for UCAS main and extended has been provided in the following section with the proposed revised representative characters marked in pink, imple- mented into their corresponding code point locations. The author has prepared a style-matched font for the purpose of imple- menting into the code chart: 144B ᑋ CANADIAN SYLLABICS carrier H 160D ᘍ CANADIAN SYLLABICS carrier ma 14D1 ᓑ CANADIAN SYLLABICS carrier NG 160E ᘎ CANADIAN SYLLABICS carrier yu 1506 ᔆ CANADIAN SYLLABICS athapascan s 160F ᘏ CANADIAN SYLLABICS carrier yO 15C0 ᗀ CANADIAN SYLLABICS Sayisi