DOCSLIB.ORG

User Guide Legend

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
User Guide Legend uide G ser Software Version 4.0 U Document updated July 22, 2017 1 Table of Contents Software License Agreement ................................................................................................................... 6 Author ................................................................................................................................................................ 13 Legend .............................................................................................................................................................. 14 Helpdesk ........................................................................................................................................................... 14 Part I – Getting Started Software Installation & Updating Installing the main application on Windows PC and Mac OS .................................................. 17 Installing the mobile app on your smart-phone or tablet.......................................................... 17 Software Editions .......................................................................................................................................... 18 Purchasing the User License .................................................................................................................... 19 About page ..................................................................................................................................................... 19 Software Updates and Software Revisions ....................................................................................... 20 Transferring the application to another PC / Mac ......................................................................... 21 Application Run Time Errors / Bugs .................................................................................................... 22 Part II – General Logic General Getting Started ............................................................................................................................................. 24 Data input, output and monitoring ..................................................................................................... 24 Application Settings .................................................................................................................................... 25 Understanding Time Zones and Time Modes ................................................................................. 31 Running 2 logbooks ................................................................................................................................... 32 mccCLOUD Cloud data synchronization .................................................................................................................... 33 Adding another PC/Mac to mccCLOUD ........................................................................................... 36 Adding a mobile device to mccCLOUD ............................................................................................ 36 Part III –Main Desktop Program Database Tables Airfields............................................................................................................................................................. 39 Pilots .................................................................................................................................................................. 42 Aircraft .............................................................................................................................................................. 45 Start-Over ....................................................................................................................................................... 49 Exporting data to CSV or XLS ................................................................................................................ 49 2 Previous Experience Log grand totals per aircraft model ..................................................................................................... 51 Import flight records from another electronic logbook application ..................................... 52 Import your self-made Excel Logbook............................................................................................... 52 Flight Logging General ............................................................................................................................................................. 53 Crew .................................................................................................................................................................. 58 Flightnumber & Pairing ............................................................................................................................. 58 Departure and arrival airfields ............................................................................................................... 60 Block Hours .................................................................................................................................................... 62 Sign-In/Out - Duty Time .......................................................................................................................... 64 Pilot Function time ...................................................................................................................................... 65 Condition time .............................................................................................................................................. 68 Autoloading Function and Condition time ...................................................................................... 69 Other Time and Data fields ...................................................................................................................... 71 Aircraft time ................................................................................................................................................... 72 Task Distribution PF / PM (PNF) ............................................................................................................ 73 Type of Approach & Autoland .............................................................................................................. 74 Type of Glider Launch ............................................................................................................................... 74 Takeoff Day/Night, Landing Day/Night ............................................................................................. 75 Fuel .................................................................................................................................................................... 76 Passengers ...................................................................................................................................................... 77 Delay ................................................................................................................................................................. 77 De-Icing ........................................................................................................................................................... 78 Remarks, Instruction, Flight Log Report ............................................................................................. 78 Track and distance ...................................................................................................................................... 79 Endorsements Endorsement Sheet .................................................................................................................................... 80 Electronic Signatures .................................................................................................................................. 82 Mass Editing Editing multiple Flight Records .............................................................................................................. 84 Editing multiple Airfields ........................................................................................................................... 86 Editing multiple Pilots ................................................................................................................................ 86 Editing multiple Aircraft ............................................................................................................................ 87 Airline Interface Configuration ................................................................................................................................................ 88 General Notes ................................................................................................................................................ 91 Autoloading function and condition time ........................................................................................ 93 Importing Crew Members ....................................................................................................................... 94 Roster Changes ............................................................................................................................................ 96 Special notes for your airline .................................................................................................................. 97 Trouble Shooting ........................................................................................................................................
Load more

Recommended publications
  • 8 December 2004 (Revised 10 January 2005) Topic: Unicode Technical Meeting #101, 15 -18 November 2004, Cupertino, California
    To: LSA and UC Berkeley Communities From: Deborah Anderson, UCB representative and LSA liaison Date: 8 December 2004 (revised 10 January 2005) Topic: Unicode Technical Meeting #101, 15 -18 November 2004, Cupertino, California As the UC Berkeley representative and LSA liaison, I am most interested in the proposals for new characters and scripts that were discussed at the UTC, so these topics are the focus of this report. For the full minutes, readers should consult the "Unicode Technical Committee Minutes" web page (http://www.unicode.org/consortum/utc-minutes.html), where the minutes from this meeting will be posted several weeks hence. I. Proposals for New Scripts and Additional Characters A summary of the proposals and the UTC's decisions are listed below. As the proposals discussed below are made public, I will post the URLs on the SEI web page (www.linguistics.berkeley.edu/sei). A. Linguistics Characters Lorna Priest of SIL International submitted three proposals for additional linguistics characters. Most of the characters proposed are used in the orthographies of languages from Africa, Asia, Mexico, Central and South America. (For details on the proposed characters, with a description of their use and an image, see the appendix to this document.) Two characters from these proposals were not approved by the UTC because there are already characters encoded that are very similar. The evidence did not adequately demonstrate that the proposed characters are used distinctively. The two problematical proposed characters were: the modifier straight letter apostrophe (used for a glottal stop, similar to ' APOSTROPHE U+0027) and the Latin small "at" sign (used for Arabic loanwords in an orthography for the Koalib language from the Sudan, similar to @ COMMERCIAL AT U+0040).
    [Show full text]
  • 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.
    [Show full text]
  • Unicode Alphabets for L ATEX
    Unicode Alphabets for LATEX Specimen Mikkel Eide Eriksen March 11, 2020 2 Contents MUFI 5 SIL 21 TITUS 29 UNZ 117 3 4 CONTENTS MUFI Using the font PalemonasMUFI(0) from http://mufi.info/. Code MUFI Point Glyph Entity Name Unicode Name E262 � OEligogon LATIN CAPITAL LIGATURE OE WITH OGONEK E268 � Pdblac LATIN CAPITAL LETTER P WITH DOUBLE ACUTE E34E � Vvertline LATIN CAPITAL LETTER V WITH VERTICAL LINE ABOVE E662 � oeligogon LATIN SMALL LIGATURE OE WITH OGONEK E668 � pdblac LATIN SMALL LETTER P WITH DOUBLE ACUTE E74F � vvertline LATIN SMALL LETTER V WITH VERTICAL LINE ABOVE E8A1 � idblstrok LATIN SMALL LETTER I WITH TWO STROKES E8A2 � jdblstrok LATIN SMALL LETTER J WITH TWO STROKES E8A3 � autem LATIN ABBREVIATION SIGN AUTEM E8BB � vslashura LATIN SMALL LETTER V WITH SHORT SLASH ABOVE RIGHT E8BC � vslashuradbl LATIN SMALL LETTER V WITH TWO SHORT SLASHES ABOVE RIGHT E8C1 � thornrarmlig LATIN SMALL LETTER THORN LIGATED WITH ARM OF LATIN SMALL LETTER R E8C2 � Hrarmlig LATIN CAPITAL LETTER H LIGATED WITH ARM OF LATIN SMALL LETTER R E8C3 � hrarmlig LATIN SMALL LETTER H LIGATED WITH ARM OF LATIN SMALL LETTER R E8C5 � krarmlig LATIN SMALL LETTER K LIGATED WITH ARM OF LATIN SMALL LETTER R E8C6 UU UUlig LATIN CAPITAL LIGATURE UU E8C7 uu uulig LATIN SMALL LIGATURE UU E8C8 UE UElig LATIN CAPITAL LIGATURE UE E8C9 ue uelig LATIN SMALL LIGATURE UE E8CE � xslashlradbl LATIN SMALL LETTER X WITH TWO SHORT SLASHES BELOW RIGHT E8D1 æ̊ aeligring LATIN SMALL LETTER AE WITH RING ABOVE E8D3 ǽ̨ aeligogonacute LATIN SMALL LETTER AE WITH OGONEK AND ACUTE 5 6 CONTENTS
    [Show full text]
  • MUFI Character Recommendation V. 3.0: Alphabetical Order
    MUFI character recommendation Characters in the official Unicode Standard and in the Private Use Area for Medieval texts written in the Latin alphabet ⁋ ※ ð ƿ ᵹ ᴆ ※ ¶ ※ Part 1: Alphabetical order ※ Version 3.0 (5 July 2009) ※ Compliant with the Unicode Standard version 5.1 ____________________________________________________________________________________________________________________ ※ Medieval Unicode Font Initiative (MUFI) ※ www.mufi.info ISBN 978-82-8088-402-2 ※ Characters on shaded background belong to the Private Use Area. Please read the introduction p. 11 carefully before using any of these characters. MUFI character recommendation ※ Part 1: alphabetical order version 3.0 p. 2 / 165 Editor Odd Einar Haugen, University of Bergen, Norway. Background Version 1.0 of the MUFI recommendation was published electronically and in hard copy on 8 December 2003. It was the result of an almost two-year-long electronic discussion within the Medieval Unicode Font Initiative (http://www.mufi.info), which was established in July 2001 at the International Medi- eval Congress in Leeds. Version 1.0 contained a total of 828 characters, of which 473 characters were selected from various charts in the official part of the Unicode Standard and 355 were located in the Private Use Area. Version 1.0 of the recommendation is compliant with the Unicode Standard version 4.0. Version 2.0 is a major update, published electronically on 22 December 2006. It contains a few corrections of misprints in version 1.0 and 516 additional char- acters (of which 123 are from charts in the official part of the Unicode Standard and 393 are additions to the Private Use Area).
    [Show full text]
  • The Unicode Standard, Version 7.0
    Latin Extended-A Range: 0100–017F This file contains an excerpt from the character code tables and list of character names for The Unicode Standard, Version 7.0 This file may be changed at any time without notice to reflect errata or other updates 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-7.0/ for charts showing only the characters added in Unicode 7.0. See http://www.unicode.org/Public/7.0.0/charts/ for a complete archived file of character code charts for Unicode 7.0. Disclaimer These charts are provided as the online reference to the character contents of the Unicode Standard, Version 7.0 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 7.0, online at http://www.unicode.org/versions/Unicode7.0.0/, as well as Unicode Standard Annexes #9, #11, #14, #15, #24, #29, #31, #34, #38, #41, #42, #44, and #45, the other Unicode Technical Reports and Standards, and the Unicode Character Database, which are available online. See http://www.unicode.org/ucd/ and http://www.unicode.org/reports/ A thorough understanding of the information contained in these additional sources is required for a successful implementation.
    [Show full text]
  • 1 Symbols (2286)
    1 Symbols (2286) USV Symbol Macro(s) Description 0009 \textHT <control> 000A \textLF <control> 000D \textCR <control> 0022 ” \textquotedbl QUOTATION MARK 0023 # \texthash NUMBER SIGN \textnumbersign 0024 $ \textdollar DOLLAR SIGN 0025 % \textpercent PERCENT SIGN 0026 & \textampersand AMPERSAND 0027 ’ \textquotesingle APOSTROPHE 0028 ( \textparenleft LEFT PARENTHESIS 0029 ) \textparenright RIGHT PARENTHESIS 002A * \textasteriskcentered ASTERISK 002B + \textMVPlus PLUS SIGN 002C , \textMVComma COMMA 002D - \textMVMinus HYPHEN-MINUS 002E . \textMVPeriod FULL STOP 002F / \textMVDivision SOLIDUS 0030 0 \textMVZero DIGIT ZERO 0031 1 \textMVOne DIGIT ONE 0032 2 \textMVTwo DIGIT TWO 0033 3 \textMVThree DIGIT THREE 0034 4 \textMVFour DIGIT FOUR 0035 5 \textMVFive DIGIT FIVE 0036 6 \textMVSix DIGIT SIX 0037 7 \textMVSeven DIGIT SEVEN 0038 8 \textMVEight DIGIT EIGHT 0039 9 \textMVNine DIGIT NINE 003C < \textless LESS-THAN SIGN 003D = \textequals EQUALS SIGN 003E > \textgreater GREATER-THAN SIGN 0040 @ \textMVAt COMMERCIAL AT 005C \ \textbackslash REVERSE SOLIDUS 005E ^ \textasciicircum CIRCUMFLEX ACCENT 005F _ \textunderscore LOW LINE 0060 ‘ \textasciigrave GRAVE ACCENT 0067 g \textg LATIN SMALL LETTER G 007B { \textbraceleft LEFT CURLY BRACKET 007C | \textbar VERTICAL LINE 007D } \textbraceright RIGHT CURLY BRACKET 007E ~ \textasciitilde TILDE 00A0 \nobreakspace NO-BREAK SPACE 00A1 ¡ \textexclamdown INVERTED EXCLAMATION MARK 00A2 ¢ \textcent CENT SIGN 00A3 £ \textsterling POUND SIGN 00A4 ¤ \textcurrency CURRENCY SIGN 00A5 ¥ \textyen YEN SIGN 00A6
    [Show full text]
  • Proposal to Add Four SENĆOŦEN Latin Charaters
    Proposal to Add Four SENĆOŦEN Latin Charaters by: John Elliot, Peter Brand, and Chris Harvey of: Saanich Native Heritage Society and First Peoples' Cultural Foundation Date: May 5, 2004 The SENĆOŦEN language is spoken on the southern tip of Vancouver Island. It’s orthography was created by the the late Dave Elliott, a respected member of the Saanich First Nation. The script is at once identifiable by the fact that it employs only majuscules (except for “s”). The community is actively using this writing system, especially in the field of language education. The majority of the letters in the orthography are already either: encoded by Unicode; or accessible by character + combining diacritic. The four proposed additions here are not present in the current Unicode standard, nor can they be created with floating diacritics. Although they could be made up of Letter + overlay diacritic, it is my understanding that the Unicode Consortium would prefer to create unique code points for these types of letters (e.g. recent acceptance of LATIN LETTER SMALL C WITH STROKE). The four letters are: LATIN CAPITAL LETTER A WITH STROKE LATIN CAPITAL LETTER C WITH STROKE LATIN CAPITAL LETTER L WITH BAR LATIN CAPITAL LETTER T WITH SLASH Figures 1 and 2 show excerpts from a SENĆOŦEN language text book and dictionary. The Saanich Tribal School SENCOTEN language education materials were prepared by Lindy Elliott, SENCOTEN language teacher, Saanich Indian School Board, 1998. Arrows point to the characters in this proposal. Figure 1: showing and Figure 2: showing and A. Administrative 1. Title: Proposal to Add Four SENĆOŦEN Latin Charaters 2.
    [Show full text]
  • Latin Extended-B Range: 0180–024F
    Latin Extended-B Range: 0180–024F This file contains an excerpt from the character code tables and list of character names for The Unicode Standard, Version 14.0 This file may be changed at any time without notice to reflect errata or other updates to the Unicode Standard. See https://www.unicode.org/errata/ for an up-to-date list of errata. See https://www.unicode.org/charts/ for access to a complete list of the latest character code charts. See https://www.unicode.org/charts/PDF/Unicode-14.0/ for charts showing only the characters added in Unicode 14.0. See https://www.unicode.org/Public/14.0.0/charts/ for a complete archived file of character code charts for Unicode 14.0. Disclaimer These charts are provided as the online reference to the character contents of the Unicode Standard, Version 14.0 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 14.0, online at https://www.unicode.org/versions/Unicode14.0.0/, as well as Unicode Standard Annexes #9, #11, #14, #15, #24, #29, #31, #34, #38, #41, #42, #44, #45, and #50, the other Unicode Technical Reports and Standards, and the Unicode Character Database, which are available online. See https://www.unicode.org/ucd/ and https://www.unicode.org/reports/ A thorough understanding of the information contained in these additional sources is required for a successful implementation.
    [Show full text]
  • Proposed Mapping of Extipa and Modifier Phonetic Characters Kirk Miller, [email protected] 2020 April 14
    Proposed mapping of extIPA and modifier phonetic characters Kirk Miller, [email protected] 2020 April 14 Per Script Ad Hoc Committee, 10780–107BF could be allocated to Latin. Mike Everson would like to draw characters. We will need to send a font to Unicode. Latin Extended-D U+A7C0, C1 still available? ...0 ...1 ...2 ...3 ...4 ...5 ...6 ...7 ...8 ...9 ...A ...B ...C ...D ...E ...F Latin D block U+A7Cx U+A7Dx U+A7Ex U+A7Fx Latin E block U+AB6x Combining Diacritical Marks Extended U+1ACx ◌ ◌ ◌ ◌ U+1ADx U+1AEx U+1AFx Supplementary plain U+1078x U+1079x U+107Ax U+107Bx U+A7C0? LATIN LETTER SMALL CAPITAL TURNED L U+A7C1? or sup plane so turned U could join it? LATIN LETTER SMALL CAPITAL TURNED K LATIN SMALL LETTER O WITH RETROFLEX HOOK. Figure 15. LATIN SMALL LETTER I WITH STROKE AND RETROFLEX HOOK. Figure 16. LATIN SMALL LETTER TESH DIGRAPH WITH RETROFLEX HOOK. Figure 14. LATIN SMALL LETTER L WITH BELT AND PALATAL HOOK. Figure 23. LATIN SMALL LETTER ENG WITH PALATAL HOOK. Figure 24. LATIN SMALL LETTER TURNED R WITH PALATAL HOOK. Figures 17–19. ... LATIN SMALL LETTER R WITH FISHHOOK AND PALATAL HOOK. Figure 19. LATIN SMALL LETTER EZH WITH PALATAL HOOK. Figures 20–21. LATIN SMALL LETTER DEZH DIGRAPH WITH PALATAL HOOK. Figure 22. LATIN SMALL LETTER TESH DIGRAPH WITH PALATAL HOOK. Figure 22. LEFT SQUARE BRACKET WITH STROKE. Figures 11, 13. RIGHT SQUARE BRACKET WITH STROKE. Figures 11, 13. LEFT SQUARE BRACKET WITH DOUBLE STROKE. Figures 11, 14. RIGHT SQUARE BRACKET WITH DOUBLE STROKE.
    [Show full text]
  • Road Work, Transportation Hinge on Vote Parents Mobilize to Halt
    w at Volume 18 Number 49 Monday. December 13.1982 Westland, Michigan. Twenty-five cents iiPfem>mm Road work, % transportation hinge on vote The demise of a comprehensive 'TIS THE season to be jolly, transportation package in the state leg­ and persons who attended the islature this year could create hard­ For a related story, see Westland City Council regular ships for residents and hinder cities in page 7A. meeting last Monday night were maintaining services, officials from certainly in toe holiday spirit. Westland and Garden City said last Owners of Amarillo Slim's week. possible loss of Nankin Transit, a five- Restaurant, a new business Late last week the House approved city bus system. The Westland City proposed for the former Das the legislation, which the state Senate Council recently passed a special reso­ Haufbrauhaus site, told the council is expected to begin debating at 7 p.m. lution urging the state to pass a trans­ they hoped to attract customers in Monday. portation package that would continue the 25- to 45-year-old age range. Officials have feared that SEMTA funding for bus systems in Michigan. A This prompted Council President and Nankin Transit services would be similar resolution was approved by the Thomas Artley to inquire, "Could reduced or discontinued, and that city council In Garden City. Mrs. Barns get in?" referring to planned road improvements and major "(Loss of Nankin Transit) Is going to former Council President Pro-Tem repairs would be delayed or dropped, if create a hardship for the senior citizens Justine Barns. "We may have to , the package doesn't pass this year.
    [Show full text]
  • Unicode Request for Modifier-Letter Support Background
    Unicode request for modifier-letter support Kirk Miller, [email protected] 2020 April 14 Background This request expands on Peter Constable’s 2003 ‘Proposal to Encode Additional Phonetic Modifier Letters in the UCS’ (https://www.unicode.org/L2/L2003/03180-add-mod-ltr.pdf), and illustrates characters that were requested in that proposal, but not illustrated and therefore not accepted at the time. Constable’s notes (Section F of his proposal) included a good summary: In general, modifier letters are used in phonetic transcription to represent secondary aspects of articulation. Secondary articulations may involve aspects of simultaneous articulation that are considered to be in some sense less dominant to the basic sound (for instance, nasalized vowels are typically conceived in terms of their oral counterparts but with the additional secondary articulation of nasalization); or they may involve a transitional articulation of a type that might otherwise be considered a complete speech sound in its own right but for various reasons is interpreted by the linguist as a secondary element in a complex speech sound (for instance, diphthongs, or nasal onset of oral stop consonants). In some situations, the recommended transcription [by the International Phonetic Association] would not involve a modifier letter; thus, many of the proposed characters are not officially approved IPA notation. Nevertheless, the use of these modifier letters if fairly commonplace among linguists, even those that advocate the use of IPA. It’s notable that one of Constable’s illustrations, of ⟨ᶿ⟩, came from the IPA Handbook despite not being officially part of the alphabet. Such usage goes back over a century, with ⟨ʃᶜ̧⟩ given as an example in the IPA chart of 1900, and that among the linguists such usage is ‘commonplace among’ is Peter Ladefoged, president of the IPA from 1986 to 1991, organizer of the 1989 Kiel convention that overhauled the alphabet, and long-time editor of the IPA Journal (JIPA).
    [Show full text]
  • Considerations in the Use of the Latin Script in Variant Internationalized Top-Level Domains
    Considerations in the use of the Latin script in variant internationalized top-level domains Final report of the ICANN VIP Study Group for the Latin script Executive summary The study group examined all the characters in the Unicode Character Code Chart version 6.1.0 that are associated with the Latin script and valid under the IDNA2008 protocol. It identified several forms of “confusability” that might require careful consideration in the collation of a subset of the broader repertoire for local use. The resolution of such issues is, however, highly dependent on local orthographic conventions. These frequently treat the same characters in different manners. Strings that are confusingly similar in the context of one language may have no such connotations in another. Noting that the Latin script is used by a larger number of separate language communities than is any other single script, attempting to provide a comprehensive overview of the needs of all of them is an unrealistic endeavor. A summary attempt at doing so nonetheless would be culturally insensitive to communities that have yet to join the IDN discussion. The study group therefore finds no basis for the categorical treatment of any code point assigned to an element of the Latin script as being equivalent to any other such code point. Nor does it believe that any such basis exists beyond what is already incorporated in the IDNA2008 protocol. The ICANN TLD application process should not permit requests for multiple Latin strings under the premise that they are variants of each other. Careful scrutiny is required when evaluating proposed TLD labels for confusability but that does not make them variants in the focused sense of the VIP study.
    [Show full text]