Input: [No.] 7 [Preference] content.switch.threshold [Value] 750000 [Description] as previous [Type]

Output: integer


Input: [No.] 8 [Preference] nglayout.initialpaint.delay [Value] 0 [Description] set time delay from initial page loading to the first page that is rendered [Type]

Output: integer


Input: [No.] 9 [Preference] browser.cache.memory.capacity [Value] 65536 [Description] memory size used for storing pages for instant recall [Type]

Output: integer


Input: [Term] Activity [Explanation]

Output: A step in the translation workflow for a job, as described by the activity type


Input: [Term] Activity type [Explanation]

Output: A task in GlobalSight. For example translation, review, PM review, engineering and so on. It is defined within GlobalSight to facilitate the building of workflows


Input: [Term] Alignment [Explanation]

Output: The process by which segments in previously translated files are matched with one another to create translation memory


Input: [Term] Attribute [Explanation]

Output: Additional set of metadata that users can add to a job. Text fields, dropdown lists, integers, dates and so on


Input: [Term] API [Explanation]

Output: Application Programming Interface


Input: [Term] CMS [Explanation]

Output: Content Management System


Input: [Term] Desktop Icon [Explanation]

Output: Application downloaded to your computer to create jobs. An alternative to creating jobs online


Input: [Term] DI [Explanation]

Output: Desktop Icon


Input: [Term] DTP [Explanation]

Output: Desktop Publishing


Input: [Term] Export [Explanation]

Output: The process of writing localized (or in‐progress) content out from GlobalSight


Input: [Term] File Profile [Explanation]

Output: Tells the system how to handle specific file types, for example xml, html, doc and so on. Sets rules on how these files are handled at job creation and while moving through the system


Input: [Term] Glossary [Explanation]

Output: See Terminology


Input: [Term] GMS [Explanation]

Output: Globalization Management System


Input: [Term] GXML [Explanation]

Output: GlobalSight XML. All content is converted to GXML when jobs are created


Input: [Term] ICE [Explanation]

Output: In-Context Exact. An exact match in the same context as the source


Input: [Term] IDE [Explanation]

Output: Integrated Development Environment


Input: [Term] Import [Explanation]

Output: The process of bringing content into GlobalSight for localization processing from an external system


Input: [Term] Job [Explanation]

Output: Translation from one language to another, as defined by the file profile.


Input: [Term] Locale pairs [Explanation]

Output: A pairing of a source and a target language for the translation process


Input: [Term] Localization Profile [Explanation]

Output: Defines how data will be routed through the system. Specifies when jobs are started, who does them, and in what order users work on them


Input: [Term] LPU [Explanation]

Output: Language Project files in SDL Passolo


Input: [Term] LSO [Explanation]

Output: Language Sign-off


Input: [Term] LSP [Explanation]

Output: Language Service Provider


Input: [Term] MT [Explanation]

Output: Machine Translation


Input: [Term] My Activities [Explanation]

Output: Home page where team members (translators, reviewers, DTP engineers) manage their activities


Input: [Term] My Jobs [Explanation]

Output: Home page where Project Managers manage their job


Input: [Term] Passolo [Explanation]

Output: Software localization application by SDL


Input: [Term] PM [Explanation]

Output: Project Manager


Input: [Term] PO [Explanation]

Output: Portable Object


Input: [Term] Project [Explanation]

Output: A project groups associated work together in a logical manner for enhanced reporting and greater flexibility. Jobs are created and assigned as part of these larger groups, for example, Marketing or Legal translations


Input: [Term] RC [Explanation]

Output: Resource Compiler


Input: [Term] RESX [Explanation]

Output: Resource file for .NET applications


Input: [Term] Role [Explanation]

Output: The locale pair and activity type assigned to a user. For example, English (United States) [en_US] -> German (Germany) [de_DE] and Translation1


Input: [Term] RTF [Explanation]

Output: Rich Text Format


Input: [Term] Segment [Explanation]

Output: A piece of localizable text, usually no bigger than a sentence


Input: [Term] SID [Explanation]

Output: Segment Identifier


Input: [Term] SID-based matching [Explanation]

Output: This checks whether the source text and the unique identifier of the string being translated are exactly the same as the match found in TMs


Input: [Term] SOAP [Explanation]

Output: Simple Object Access Protocol. A remote procedure protocol based upon XML over HTTP


Input: [Term] SRX [Explanation]

Output: Segmentation Rules eXchange


Input: [Term] TB [Explanation]

Output: Term Base


Input: [Term] TBX [Explanation]

Output: TermBase eXchange


Input: [Term] TD [Explanation]

Output: Terminology Database


Input: [Term] TDA [Explanation]

Output: TAUS Data Association


Input: [Term] TER [Explanation]

Output: Translations Edit Report


Input: [Term] Terminology [Explanation]

Output: A shared glossary of approved translations for particular words or phrases. Often used with product names or core concepts to ensure consistent translations across multiple jobs


Input: [Term] TM [Explanation]

Output: A Translation Memory is a database of stored translations that is used for leveraging future translations and re-using previous ones


Input: [Term] TM Profile [Explanation]

Output: Defines how multiple TMs should apply to translations. Determines the order in which multiple TMs should be accessed for leverage and defines the rules for leveraging from these TMs and how it is presented to the translation team


Input: [Term] TMS [Explanation]

Output: Translation Management System. Generic name for this kind of system, as opposed to a particular product


Input: [Term] TMX [Explanation]

Output: Translation Memory eXchange


Input: [Term] Workflow [Explanation]

Output: A sequence of activities assigned to particular users in a predefined sequence. Dispatches tasks to the correct users for processing and provides an accurate tracking of the process


Input: [Term] WSDL [Explanation]

Output: Web Services Description Language. An XML document that fully describes all input to the Web service methods


Input: [Paramater] last= [Set to] author= or last= [Notes]

Output: If author= and last= are set the value of last= is used.

फलकम्:Cite EB1911 - विकिपीडिया

Paramaters passed into {{cite encyclopedia}}


Input: [Paramater] first= [Set to] first= [Notes]

Output: Set to the value of first= or not set

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] authorlink= [Set to] authorlink= [Notes]

Output: Set to the value of authorlink= or not set

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] coauthors= [Set to] coauthors= [Notes]

Output: Unlikely to be needed but can be set

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] editor-first= [Set to] Hugh [Notes]

Output: Automatically set within the template unless short is set

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] editor-last= [Set to] Chisholm [Notes]

Output: Automatically set within the template unless short is set

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] encyclopedia= [Set to] Encyclopædia Britannica [Notes]

Output: Automatically set within the template

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] title= [Set to] wstitle= or title= or article= [Notes]

Output: Set to wstitle= if set, if not to title= if set, if not to article= if set, if not set then left blank.

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] url= [Set to] url= [Notes]

Output: Set to the value of url= unless wstitle= is set in which case it is not set.

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] accessdate= [Set to] accessdate= [Notes]

Output: Set to the value of accessdate= or not set

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] language= [Notes]

Output: Not set

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] edition= [Set to] 11th [Notes]

Output: Set by default within the template, can be overridden

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] date= [Notes]

Output: Not set (see year)

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] year= [Set to] 1911 [Notes]

Output: Set by default within the template, can be overridden

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] month= [Notes]

Output: Not set

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] publisher= [Set to] Cambridge University Press [Notes]

Output: automatically set within the template unless short is set

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] volume= [Set to] volume= [Notes]

Output: Set to the value of volume= or not set

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] location= [Notes]

Output: Not set

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] id= [Notes]

Output: Not set

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] isbn= [Notes]

Output: Not set

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] oclc= [Notes]

Output: Not set

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] doi= [Notes]

Output: Not set

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] page= [Set to] page= [Notes]

Output: Set to the value of page= or not set

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] pages= [Set to] pages= [Notes]

Output: Set to the value of pages= or not set

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] quote= [Notes]

Output: Not set

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Paramater] ref= [Set to] ref = [Notes]

Output: Set to the value of ref= or not set

फलकम्:Cite EB1911 - विकिपीडिया


Input: [Description] Abbreviated weekday name [Code]

Output: %a

AspGrid.com - Object Reference: Column Object


Input: [Description] Full weekday name [Code]

Output: %A

AspGrid.com - Object Reference: Column Object


Input: [Description] Abbreviated month name [Code]

Output: %b

AspGrid.com - Object Reference: Column Object


Input: [Description] Full month name [Code]

Output: %B

AspGrid.com - Object Reference: Column Object


Input: [Description] Date and time representation appropriate for locale [Code]

Output: %c

AspGrid.com - Object Reference: Column Object


Input: [Description] Day of month as decimal number (01 - 31) [Code]

Output: %d

AspGrid.com - Object Reference: Column Object


Input: [Description] Hour in 24-hour format (00 - 23) [Code]

Output: %H

AspGrid.com - Object Reference: Column Object


Input: [Description] Hour in 12-hour format (01 - 12) [Code]

Output: %I

AspGrid.com - Object Reference: Column Object


Input: [Description] Day of year as decimal number (001 - 366) [Code]

Output: %j

AspGrid.com - Object Reference: Column Object


Input: [Description] Month as decimal number (01 - 12) [Code]

Output: %m

AspGrid.com - Object Reference: Column Object


Input: [Description] Minute as decimal number (00 - 59) [Code]

Output: %M

AspGrid.com - Object Reference: Column Object


Input: [Description] Current locale�s A.M./P.M. indicator for 12-hour clock [Code]

Output: %p

AspGrid.com - Object Reference: Column Object


Input: [Description] Second as decimal number (00 - 59) [Code]

Output: %S

AspGrid.com - Object Reference: Column Object


Input: [Description] Week of year as decimal number, with Sunday as first day of week (00 - 53) [Code]

Output: %U

AspGrid.com - Object Reference: Column Object


Input: [Description] Weekday as decimal number (0 - 6; Sunday is 0) [Code]

Output: %w

AspGrid.com - Object Reference: Column Object


Input: [Description] Week of year as decimal number, with Monday as first day of week (00 - 53) [Code]

Output: %W

AspGrid.com - Object Reference: Column Object


Input: [Description] Date representation for current locale [Code]

Output: %x

AspGrid.com - Object Reference: Column Object


Input: [Description] Time representation for current locale [Code]

Output: %X

AspGrid.com - Object Reference: Column Object


Input: [Description] Year without century, as decimal number (00 - 99) [Code]

Output: %y

AspGrid.com - Object Reference: Column Object


Input: [Description] Year with century, as decimal number [Code]

Output: %Y

AspGrid.com - Object Reference: Column Object


Input: [Description] Time-zone name or abbreviation; no characters if time zone is unknown [Code]

Output: %z

AspGrid.com - Object Reference: Column Object


Input: [Description] Percent sign [Code]

AspGrid.com - Object Reference: Column Object


Input: [Tag] 000 [Label] LEADER [Instructions] Click in this field to fill it in. Then set "Bibliographic level" to 'a' for articles or 's' for serials. Otherwise, leave everything as is. [Description]

Output: Describes the record(i.e. surrogate) -- is it a record for a monograph? A serial?


Input: [Tag] 001 [Label] CONTROL NUMBER [Instructions] Enter the accession number written inside the item here. For articles and items which do not have accession numbers, leave blank. [Description]

Output: Accession number.


Input: [Tag] 003 [Label] CONTROL NUMBER IDENTIFIER [Instructions] Click in this field to fill it in (will auto fill if you have your MARCOrgCode preference set). [Description]

Output: Your MARC Organizational Code


Input: [Tag] 005 [Label] D & T LATEST TRANSACTION [Instructions] Click in this field to fill it in. [Description]

Output: Current date and time.


Input: [Tag] 008 [Label] FIXED-LENGTH DATA ELEMENTS [Instructions] Generally you will only use 's' (single) or 'm' (multiple) options for position 06- use the former when the item was published in a single year, the latter when it was published over the course of several. If there is a single date, only enter a date in the first date field (positions 07-10). Enter the three-digit country code in positions 15-17, being sure to add spaces if the country code is fewer than three characters long. If there is an index, note that fact in position 31. Enter the three-letter language code in positions 35-37. [Description]

Output: Field containing computer-readable representations of a number of things.


Input: [Tag] 010 [Label] LCCN [Instructions] Check on the copyright page of the book (if it was published in the US) or the LC catalog for this number. If you can't find it, don't worry about it. [Description]

Output: A number assigned by the Library of Congress to uniquely identify the work.


Input: [Tag] 020 [Label] ISBN [Instructions] If this number isn't listed on the book, there probably isn't one. [Description]

Output: Unique number used by publishers to identify books.


Input: [Tag] 022 [Label] ISSN [Instructions] If this number isn't listed on the book, there probably isn't one. [Description]

Output: Unique number used by publishers to identify serials.


Input: [Tag] 033 [Label] DATE/TIME OF EVENT [Instructions] For auctions that took place on only one day, enter the date of the auction in the format YYYYMMDD in the subfield 'a' and a '0' in the first indicator. For auctions that took place over two consecutive days or any number of non-consecutive days, create a subfield 'a' for each day with the date in the format YYYYMMDD, and put a '1' in the first indicator. For auctions that took place over more than two consecutive days, create a subfield 'a' (in format YYYYMMDD) for the first day and a subfield 'a' (also in format YYYYMMDD) for the last day, and put a '2' in the first indicator. [Description]

Output: Used for auction dates. Required for auction catalogs.


Input: [Tag] 040 [Label] CATALOGING SOURCE [Instructions] For imported records, add a subfield 'd' with your OCLC code as the value. For new records, make sure that the subfield 'c' with your OCLC code as the value. [Description]

Output: Identifies which libraries created and modified the record.


Input: [Tag] 041 [Label] LANGUAGE CODE [Instructions] For significant portions of a text in a given language, there should be a subfield 'a' with that language code. If there are only summaries or abstracts in a specific language, create a subfield 'b' with that language code. [Description]

Output: Identifies all the languages used in an item, when two or more languages are present.


Input: [Tag] 100 [Label] MAIN ENTRY--PERSONAL [Instructions] See Authorized headings sheet and AACR2. The first indicator should generally be a '1', to indicate that the entry is surname first. If the name consists only of a forename, however, the first indicator should be '0'. [Description]

Output: Authorized form of the main author's name


Input: [Tag] 110 [Label] MAIN ENTRY--CORPORATE [Instructions] Auction catalogs should use a 110 field rather than a 100 field. See Authorized headings sheet and AACR2. Set the first indicator to '2'. [Description]

Output: Authorized form of the name of the main corporate author. Required for auction catalogs.


Input: [Tag] 111 [Label] MAIN ENTRY--MEETING [Instructions] See Authorized headings sheet and AACR2. Set the first indicator to '2'. [Description]

Output: Authorized form of the name of a meeting which acted as a main offer (e.g. conference proceedings)


Input: [Tag] 245 [Label] TITLE STATEMENT [Instructions] Enter the title in subfield 'a', the subtitle in subfield 'b', and the statement of responsibility in subfield 'c'. If you are creating a record for a single volume or part of a multi-part item, you should put the part number in subfield 'n' and the part title in subfield 'p.' For auction catalogs, the date (in 'MM/DD/YYYY' format) should be listed in square brackets in subfield 'f'. See ISBD punctuation sheet. Set the first indicator to '0' if there is no author, otherwise set it to '1'. Set the second indicator to the number of non-filing characters (i.e. characters in an initial articles plus the space... for "The " set the second indicator to '4'). [Description]

Output: Transcription of the title statement from the title page (or chief source of information)


Input: [Tag] 246 [Label] VARYING FORM OF TITLE [Instructions] If the patron might look for the work under a different title, enter it here. Do not include initial articles. The first indicator should be '3', unless the title is merely a variant spelling, in which case the first indicator should be '1'. [Description]

Output: Alternate form of title for searching and filing purposes


Input: [Tag] 250 [Label] EDITION STATEMENT [Instructions] Transcribe the edition statement exactly as it appears on the title-page. You may abbreviate if the edition statement is very long. [Description]

Output: Transcription of the edition statement from the title page (or chief source of information)


Input: [Tag] 260 [Label] PUBLICATION (IMPRINT) [Instructions] Put the location of publication in subfield 'a', the publisher in subfield 'b', and the year (or probable year) in subfield 'c'. See ISBD punctuation sheet. [Description]

Output: Publication information.


Input: [Tag] 300 [Label] PHYSICAL DESCRIPTION [Instructions] Enter the pagination statement in subfield 'a', a brief description of "special" contents such as illustrations or maps in subfield 'b' (see AACR2), and the size of the item in subfield 'c'. See ISBD punctuation sheet. [Description]

Output: Physical description


Input: [Tag] 490 [Label] SERIES STATEMENT [Instructions] Transcribe the series statement into subfield 'a' with the volume number in subfield 'v'. See ISBD punctuation sheet. Set the first indicator to '1' if you are using an 830. As a general rule, you should do so. [Description]

Output: Shows the series statement exactly as it appears on the item.


Input: [Tag] 500 [Label] GENERAL NOTE [Instructions] Enter notes as full sentences, with a separate 500 field for each distinct topic. [Description]

Output: Notes that don't fit anywhere else.


Input: [Tag] 501 [Label] WITH NOTE [Instructions] Put description of relationship in subfield 'a'. [Description]

Output: Notes whether the work is bound with the works described by other records.


Input: [Tag] 504 [Label] BIBLIOGRAPHY, ETC. NOTE [Instructions] If the work includes a bibliography and index, put the text "Includes bibliographical references (p. XXX-XXX) and index." in subfield 'a'. If the work does not include an index, remove that part of the sentence. If the references are scattered throughout the work and not gathered into a distinct sentence, remove the parenthetical statement. [Description]

Output: Indicates whether the work includes a bibliography.


Input: [Tag] 505 [Label] FORMATTED CONTENTS [Instructions] See ISBD punctuation sheet. Set the first indicator to '0'. If you are separately coding authors and titles, set the second indicator to '0'. Otherwise, leave the second indicator blank. [Description]

Output: List of contents in a standard format. Unformatted contents can be listed in a 500 (General Note) field.


Input: [Tag] 518 [Label] DATE/TIME OF EVENT NOTE [Instructions] For auction catalogs, enter the date of the auction in the format 'January 2, 1984' in the subfield 'a' [Description]

Output: Used for auction dates.


Input: [Tag] 520 [Label] SUMMARY, ETC. [Instructions] In general you do not need to write a summary. A summary might be called for, however, with items that cannot be easily reviewed by a patron, such as books with highly acidic paper or CD-ROMs. [Description]

Output: A brief summary or abstract of the book or article.


Input: [Tag] 546 [Label] LANGUAGE NOTE [Instructions] Only needed for works in multiple languages. See ISBD punctuation sheet. [Description]

Output: Note describing the languages used in the work


Input: [Tag] 561 [Label] PROVENANCE INFORMATION [Instructions] Used only for rare books. [Description]

Output: Describes the previous ownership of the item.


Input: [Tag] 563 [Label] BINDING INFORMATION [Instructions] Used only for rare books. [Description]

Output: Describes the binding of the item.


Input: [Tag] 590 [Label] LOCAL NOTE [Instructions] Used for auction catalogs to indicate what types of coins are sold in the auction- Roman, Greek, etc. [Description]

Output: Local notes. Required for auction catalogs.


Input: [Tag] 600 [Label] SUBJECT ADDED--PERSONAL [Instructions] See Authorized headings sheet and AACR2. The first indicator should generally be a '1', to indicate that the entry is surname first. If the name consists only of a forename, however, the first indicator should be '0'. If you found the name in the LC authority file, set the second indicator to '0'. Otherwise set the second indicator to '4'. [Description]

Output: Authorized form of personal names for people discussed in the work


Input: [Tag] 610 [Label] SUBJECT ADDED--CORPORATE [Instructions] See Authorized headings sheet and AACR2. Set the first indicator to '2'. If you found the name in the LC authority file, set the second indicator to '0'. Otherwise set the second indicator to '4'. [Description]

Output: Authorized form of corporate names for organizations discussed in the work


Input: [Tag] 611 [Label] SUBJECT ADDED--MEETING [Instructions] See Authorized headings sheet and AACR2. Set the first indicator to '2'. If you found the name in the LC authority file, set the second indicator to '0'. Otherwise set the second indicator to '4'. [Description]

Output: Authorized form of meeting names for meetings discussed in the work


Input: [Tag] 630 [Label] SUBJECT ADDED--UNIFORM TITLE [Instructions] See Authorized headings sheet and AACR2. Set the first indicator to the number of non-filing characters (i.e. characters in an initial articles plus the space... for "The " set the first indicator to '4'). If you found the name in the LC authority file, set the second indicator to '0'. Otherwise set the second indicator to '4'. [Description]

Output: Authorized form of titles for other works discussed in the work


Input: [Tag] 650 [Label] SUBJECT ADDED--TOPICAL [Instructions] See Authorized headings sheet and AACR2. If you found the name in the LC authority file, set the second indicator to '0'. Otherwise set the second indicator to '4'. [Description]

Output: Library of Congress Subject Heading terms describing the subject of the work


Input: [Tag] 651 [Label] SUBJECT ADDED--GEOGRAPHICAL [Instructions] See Authorized headings sheet and AACR2. If you found the name in the LC authority file, set the second indicator to '0'. Otherwise set the second indicator to '4'. [Description]

Output: Library of Congress Subject Heading geographical terms describing the subject of the work


Input: [Tag] 655 [Label] INDEX TERM--GENRE/FORM [Instructions] Generally used only for auction catalogs, which should have the genre heading "Auction catalogs." (make sure to find the authorized heading!) If you found the name in the LC authority file, set the second indicator to '0'. If you are using a term from a specific thesaurus, set the second indicator to '7' and put the code for the thesaurus in subfield '2'. Otherwise set the second indicator to '4'. [Description]

Output: Describes what an item is as opposed to what the item is about.


Input: [Tag] 690 [Label] LOCAL SUBJECT ADDED--TOPICAL [Instructions] If there is no appropriate LCSH term, you can use a 690 with subject headings you find on other items in the catalog. [Description]

Output: Used for headings from any custom subject authority file.


Input: [Tag] 691 [Label] LOCAL SUBJECT ADDED--GEOGRAPHICAL [Instructions] If there is no appropriate LCSH term, you can use a 691 with subject headings you find on other items in the catalog. [Description]

Output: Used for headings from any custom subject authority file.


Input: [Tag] 700 [Label] ADDED ENTRY--PERSONAL [Instructions] See Authorized headings sheet and AACR2. The first indicator should generally be a '1', to indicate that the entry is surname first. If the name consists only of a forename, however, the first indicator should be '0'. [Description]

Output: Used for second authors and other persons related to the production of the work.


Input: [Tag] 710 [Label] ADDED ENTRY--CORPORATE [Instructions] See Authorized headings sheet and AACR2. Set the first indicator to '2'. [Description]

Output: Used for corporate bodies related to the production of the work (e.g. publishers).


Input: [Tag] 711 [Label] ADDED ENTRY--MEETING [Instructions] See Authorized headings sheet and AACR2. Set the first indicator to '2'. [Description]

Output: Used for meetings related to the production of the work (e.g. symposia that contributed to the work).


Input: [Tag] 730 [Label] ADDED ENTRY--UNIFORM TITLE [Instructions] See Authorized headings sheet and AACR2. Set the first indicator to the number of non-filing characters (i.e. characters in an initial articles plus the space... for "The " set the first indicator to '4'). [Description]

Output: Used for uniform titles related to the production of the work (e.g. a work that inspired the present work)


Input: [Tag] 773 [Label] HOST ITEM ENTRY [Instructions] If the host publication is author main entry, enter the authorized form of the author's name in subfield 'a'. Put the title in subfield 't'. If the host publication is an independent work, put publication information in subfield 'd'. When available, ISSN and ISBN should always be used in, in subfields 'x' and 'z' respectively. Relationship information (e.g. volume number, page number, etc.) goes in subfield 'g'. Subfield 'q' contains an encoded representation of the location of the item: volume, issue, and section numbers are separated by colons, and the first page is entered following a '<' at the end of the subfield. See ISBD punctuation sheet. Set the first indicator to '0'. If you want the label "In:" to be generated, leave the second indicator blank. If you want something else displayed before the 773 text, set the second indicator to '8' and add a subfield 'i' with the label you want at the beginning of the field (e.g. "$iOffprint from:"). [Description]

Output: Describes the larger bibliographic unit that contains the work (e.g. book or journal containing the article being described in the current record)


Input: [Tag] 830 [Label] SERIES ENTRY--UNIFORM TITLE [Instructions] See Authorized headings sheet and AACR2. Set the second indicator to the number of non-filing characters (i.e. characters in an initial articles plus the space... for "The " set the second indicator to '4'). [Description]

Output: Authorized form of the series name transcribed in the 490 field. Often this will just be the same as the 490.


Input: [Tag] 852 [Label] LOCATION/CALL NUMBER [Instructions] Do not put anything in this field if you are cataloging a volume which gets only one record and a barcode. If the item does not get a barcode, or you are currently creating a record for an article in a volume, put the section in subfield 'a' (see ANS cataloging documentation), and the call number in subfield 'i'. Set the first indicator to '8'. [Description]

Output: Provides the section name for pre-barcode books, pamphlets, and some articles and serials.


Input: [Tag] 856 [Label] ELECTRONIC ACCESS [Instructions] Put the URL of any electronic copies or summaries, etc. in subfield 'u' and a link title in subfield 'y'. Set the first indicator to '4'. [Description]

Output: Links to material available online.


Input: [Tag] 942 [Label] ADDED ENTRY ELEMENTS (KOHA) [Instructions] Set the subfield 'c' to the appropriate item type. [Description]

Output: Used for Koha-specific data.


Input: [Class] MppDump [Description]

Output: This is a trivial class used to dump the contents of an MPP file broken down into its internal file and directory structure, with the content of each of the files written out as hex digits, and their ASCII equivalents.

Class Summary


Input: [Class] MpxjConvert [Description]

Output: This is a general utility designed to convert from one project file format to another.

Class Summary


Input: [Class] MpxjCreate [Description]

Output: This example illustrates creation of an MPX or an MSPDI file from scratch.

Class Summary


Input: [Class] MpxjFilter [Description]

Output: This example shows tasks or resources being read from a project file, a filter applied to the list, and the results displayed.

Class Summary


Input: [Class] MpxjQuery [Description]

Output: This example shows an MPP, MPX or MSPDI file being read, and basic task and resource data being extracted.

Class Summary


Input: [Class] PrimaveraConvert [Description]

Output: This utility is design simply to illustrate the use of the PrimaveraReader class.

Class Summary


Input: [Class] TaskDateDump [Description]

Output: Simple data dump utility.

Class Summary


Input: [Name] Equality [Expression] a == b [Return type] Convertible to bool [Type requirements]

Output: T is EqualityComparable


Input: [Name] Inequality [Expression] a != b [Return type] Convertible to bool [Type requirements]

Output: T is EqualityComparable


Input: [Name] Less [Expression] a < b [Return type] Convertible to bool [Type requirements]

Output: T is LessThanComparable


Input: [Name] Greater [Expression] a > b [Return type] Convertible to bool [Type requirements]

Output: T is LessThanComparable


Input: [Name] Less or equal [Expression] a <= b [Return type] Convertible to bool [Type requirements]

Output: T is LessThanComparable


Input: [Name] Greater or equal [Expression] a >= b [Return type] Convertible to bool [Type requirements]

Output: T is LessThanComparable


Input: [CODE] 00 [DML FUNCTION]

Output: Combined with a major code of 00, this code indicates successful completion of the DML operation. Combined with a non-zero major code, this code indicates that the DML operation was not completed successfully, due to central version causes, such as time-outs and program checks.


Input: [CODE] 01 [DML FUNCTION]

Output: An area has not been readied. When this code is combined with a major code of 16, an IF operation has resulted in a valid false condition.


Input: [CODE] 02 [DML FUNCTION]

Output: Either the db-key used with a FIND/OBTAIN DB-KEY statement or the direct db-key suggested for a STORE is not within the page range for the specified record name.


Input: [CODE] 04 [DML FUNCTION]

Output: The occurrence count of a variably occurring element has been specified as either less than zero or greater than the maximum number of occurrences defined in the control element.


Input: [CODE] 05 [DML FUNCTION]

Output: The specified DML function would have violated a duplicates-not-allowed option for a CALC, sorted or index set.


Input: [CODE] 06 [DML FUNCTION]

Output: No currency has been established for the named record, set or area.


Input: [CODE] 07 [DML FUNCTION]

Output: Either the end of a set, area, or index has been reached or the set is empty.


Input: [CODE] 08 [DML FUNCTION]

Output: Either the specified record, set, procedure, or LR verb is not in the subschema or the specified record is not a member of the set.


Input: [CODE] 09 [DML FUNCTION]

Output: The area has been readied with an incorrect usage mode.


Input: [CODE] 10 [DML FUNCTION]

Output: An existing access restriction or subschema usage prohibits execution of the specified DML specification. For the LRF users, the subschema in use allows access to database records only. For SPF users, this code may also indicate improper use of the ERASE statement. Commbined with a major code of 00, this code means the program has attempted to access a database record, but the subschema in use allows access to logical records only.


Input: [CODE] 11 [DML FUNCTION]

Output: The record cannot be stored in the specified area due to insufficient space.


Input: [CODE] 12 [DML FUNCTION]

Output: There is no db-key for the record to be stored. This is a system internal error and should be reported.


Input: [CODE] 13 [DML FUNCTION]

Output: A current record of run unit has not been established or has been nullified by a previous ERASE statement.


Input: [CODE] 14 [DML FUNCTION]

Output: The CONNECT statement cannot be executed because the requested record has been defined as a mandatory automatic member of the set.


Input: [CODE] 15 [DML FUNCTION]

Output: The DISCONNECT statement cannot be executed because the requested record has been defined as a mandatory automatic member of the set.


Input: [CODE] 16 [DML FUNCTION]

Output: The record cannot be connected to a set of which it is already a member.


Input: [CODE] 18 [DML FUNCTION]

Output: The record has not been bound.


Input: [CODE] 20 [DML FUNCTION]

Output: The current record is not the same type as the specified record name.


Input: [CODE] 21 [DML FUNCTION]

Output: Not all areas being used have been readied in the correct usage mode.


Input: [CODE] 22 [DML FUNCTION]

Output: The record name specified is not currently a member of the set name specified.


Input: [CODE] 23 [DML FUNCTION]

Output: The area name specified is either not in the subschema or not an extent area; or the record name specified has not been defined within the area name specified.


Input: [CODE] 25 [DML FUNCTION]

Output: No currency has been established for the named set.


Input: [CODE] 26 [DML FUNCTION]

Output: Record not found. Either no duplicates exist for the named record or the record name or SPF index entry cannot be found.


Input: [CODE] 28 [DML FUNCTION]

Output: The run unit has attempted to ready an area that has been readied previously.


Input: [CODE] 29 [DML FUNCTION]

Output: The run unit has attempted to place a lock on a record that is locked already by another run unit. A deadlock results and the run unit is aborted.


Input: [CODE] 30 [DML FUNCTION]

Output: An attempt has been made to erase the owner record of a non-empty set.


Input: [CODE] 31 [DML FUNCTION]

Output: The retrieval statement format conflicts with the record’s location mode.


Input: [CODE] 32 [DML FUNCTION]

Output: An attempt to retrieve a CALC/DUPLICATE record was unsuccessful; the value of the CALC field in variable storage is not equal to the value of the CALC control element in the current record of run unit.


Input: [CODE] 33 [DML FUNCTION]

Output: At least on set in which the record participates has not been included in the subschema.


Input: [CODE] 40 [DML FUNCTION]

Output: The WHERE clause in an OBTAIN NEXT logical-record request is inconsistent with a previous OBTAIN FIRST or OBTAIN NEXT command for the same record. Previously specified criteria, such as reference to a key field, has been changed. A path status of LR-ERROR is returned to the LRC block.


Input: [CODE] 41 [DML FUNCTION]

Output: The subschema contains no path that matches the WHERE clause in a logical-record request. A path status of LR-ERROR is returned to the LRC block.


Input: [CODE] 42 [DML FUNCTION]

Output: An ON clause included in the path by the DBA specified return of the LR-ERROR path status to the LRC block; an error has occurred while processing the LRF request.


Input: [CODE] 43 [DML FUNCTION]

Output: A program check has been recognized during evaluation of a WHERE clause; the program check indicates that either a WHERE clause has specified comparison of a packed decimal field to an unpacked non-numeric data field, or data in variable storage or a database record does not conform to its description. A path status of LR-ERROR is returned to the LRC block unless the DBA has included an ON clause to override this action in the path.


Input: [CODE] 44 [DML FUNCTION]

Output: The WHERE clause in a logical-record request does not supply a key element (sort key, CALC key or db-key) expected by the path. A path status of LR-ERROR is returned to the LRC block.


Input: [CODE] 45 [DML FUNCTION]

Output: During evaluation of a WHERE clause, a program check has been recognized because a subscript value is neither greater than zero nor less than its maximum allowed value plus one. A path status of LR-ERROR is returned to the LRC block unless the DBA has included an ON clause to override this action in the path.


Input: [CODE] 46 [DML FUNCTION]

Output: A program check has revealed an arithmetic exception (for example: overflow, underflow, significance, divide) during evaluation of a WHERE clause. A path status of LR-ERROR is returned to the LRC block unless the DBA has included an ON clause to override this action in the path.


Input: [CODE] 53 [DML FUNCTION]

Output: The subschema definition of an indexed set does not match the indexed set’s physical structure in the database.


Input: [CODE] 54 [DML FUNCTION]

Output: Either the prefix length of an SR51 record is less than zero or the data length is less than or equal to zero.


Input: [CODE] 55 [DML FUNCTION]

Output: An invalid length has been defined for a variable length record.


Input: [CODE] 56 [DML FUNCTION]

Output: An insufficient amount of memory to accomodate the IDMS/R compression/ decompression routines is available.


Input: [CODE] 60 [DML FUNCTION]

Output: A record occurrence type is inconsistent with the set named in the ERROR-SET field in the IDMS communication block. This code usually indicates a broken chain.


Input: [CODE] 61 [DML FUNCTION]

Output: No record can be found for an internal db-key. This code usually indicates a broken chain.


Input: [CODE] 62 [DML FUNCTION]

Output: A system-generated db-key points to a record occurrence, but no record with that db-key can be found. This code usually indicates a broken chain.


Input: [CODE] 63 [DML FUNCTION]

Output: The DBMS cannot interpret the DML function to be performed. When combined with a major code of 00, this means invalid function parameters have been passed on the call to the DBMS. For LRF users, a WHERE clause includes a keyword that is longer than the 32 characters allowed.


Input: [CODE] 64 [DML FUNCTION]

Output: The record cannot be found; the CALC control element has not been defined properly in the subschema.


Input: [CODE] 65 [DML FUNCTION]

Output: The database page read was not the page requested.


Input: [CODE] 66 [DML FUNCTION]

Output: The area specified is not avaiilable for update.


Input: [CODE] 67 [DML FUNCTION]

Output: The subschema invoked does not match the subschema object tables.


Input: [CODE] 68 [DML FUNCTION]

Output: The CICS interface was not started.


Input: [CODE] 69 [DML FUNCTION]

Output: A BIND RUN-UNIT may not have been issued; the CV may be inactive or not accepting new run-units; or the connection with the CV may have been broken due to time-out or other factors. When combined with a major code of 00, this code means the program has been disconnected from the DBMS.


Input: [CODE] 70 [DML FUNCTION]

Output: The database or journal file will not ready properly.


Input: [CODE] 71 [DML FUNCTION]

Output: The page range for the area being readied or the page range requested cannot found in the DMCL.


Input: [CODE] 72 [DML FUNCTION]

Output: There is insufficient memory to dynamically load a subschema or database procedure.


Input: [CODE] 73 [DML FUNCTION]

Output: A CV run-unit will exceed the max. users value specified at system generation.


Input: [CODE] 74 [DML FUNCTION]

Output: The dynamic load of a module has failed. If operating on the CV, a subschema or database procedure either was not found in the data dictionary or the load (core image) library or, if loaded, will exceed the number of subschema and the database procedures provided for at system generation.


Input: [CODE] 75 [DML FUNCTION]

Output: A read error has occurred.


Input: [CODE] 76 [DML FUNCTION]

Output: A write error has occurred.


Input: [CODE] 77 [DML FUNCTION]

Output: The run-unit has not been bound or has been bound twice. When combined with a major code of 00, this code means either the program is no longer signed on to the subschema or the variable subschema tables have been overwritten.


Input: [CODE] 78 [DML FUNCTION]

Output: An area wait deadlock has occurred.


Input: [CODE] 79 [DML FUNCTION]

Output: The run-unit has requested more db-key locks than are available to the system.


Input: [CODE] 80 [DML FUNCTION]

Output: The target node is either not active or has been disabled from the DDS configuration.


Input: [CODE] 81 [DML FUNCTION]

Output: The database name specified is not known to the CV.


Input: [CODE] 82 [DML FUNCTION]

Output: The subschema is not valid under the specified database.


Input: [CODE] 83 [DML FUNCTION]

Output: An error has occurred in accessing native VSAM data sets.


Input: [Method and Description] error(int code) Throws an appropriate exception based on the passed in error code. [Modifier and Type]

Output: static void

SWT (Eclipse Remote Application Platform API Reference)

Methods


Input: [Method and Description] error(int code, java.lang.Throwable throwable) Throws an appropriate exception based on the passed in error code. [Modifier and Type]

Output: static void

SWT (Eclipse Remote Application Platform API Reference)

Methods


Input: [Method and Description] error(int code, java.lang.Throwable throwable, java.lang.String detail) Throws an appropriate exception based on the passed in error code. [Modifier and Type]

Output: static void

SWT (Eclipse Remote Application Platform API Reference)

Methods


Input: [Method and Description] getMessage(java.lang.String key) Returns the NLS'ed message for the given argument. [Modifier and Type]

Output: static java.lang.String

SWT (Eclipse Remote Application Platform API Reference)

Methods


Input: [Method and Description] getPlatform() Returns the SWT platform name. [Modifier and Type]

Output: static java.lang.String

SWT (Eclipse Remote Application Platform API Reference)

Methods


Input: [Method and Description] getVersion() Returns the SWT version number as an integer. [Modifier and Type]

Output: static int

SWT (Eclipse Remote Application Platform API Reference)

Methods


Input: [Variable name] CompanyName [User-defined] Yes [Value]

Output: Your company name


Input: [Variable name] ProductName [User-defined] Yes [Value]

Output: Installation product name


Input: [Variable name] ProductVersion [User-defined] Yes [Value]

Output: Installation product version


Input: [Variable name] ProductMenu [User-defined] Yes1 [Value]

Output: Folder for creating program menu shortcuts


Input: [Variable name] ProductPath [User-defined] Yes [Value]

Output: Folder for creating product files and folders


Input: [Variable name] IsUserAnAdmin [User-defined] No [Value]

Output: Contains "1" if the current user has Administrator privileges; otherwise contains "0".


Input: [Variable name] NetFrameworkFullVersion [User-defined] No [Value]

Output: Full version number of .NET Framework installed, for example: "2.0.50727"


Input: [Variable name] NetFrameworkShortVersion [User-defined] No [Value]

Output: Short form of the .NET Framework version number, for example: "2.0"


Input: [Variable name] WindowTitle [User-defined] Yes [Value]

Output: Installer window title


Input: [Variable name] UninstallTitle [User-defined] Yes [Value]

Output: Uninstaller window title


Input: [Variable name] InstallerPath [User-defined] No [Value]

Output: The path to folder containing installer executable


Input: [Variable name] InstallerFile [User-defined] No [Value]

Output: The name of the installer executable. For example: setup.exe


Input: [Variable name] DesktopPath [User-defined] No [Value]

Output: Desktop folder


Input: [Variable name] FontsPath [User-defined] No [Value]

Output: System fonts folder


Input: [Variable name] MyDocumentsPath [User-defined] No [Value]

Output: 'My Documents' folder


Input: [Variable name] ProgramsPath [User-defined] No [Value]

Output: 'Program Files' folder


Input: [Variable name] CommonFiles [User-defined] No [Value]

Output: 'Common files' folder


Input: [Variable name] SystemPath [User-defined] No [Value]

Output: Windows System (System32) folder


Input: [Variable name] QuickLaunch [User-defined] No [Value]

Output: Quick Launch folder


Input: [Variable name] UserAppData [User-defined] No [Value]

Output: 'Application Data' folder2


Input: [Variable name] CommonAppData [User-defined] No [Value]

Output: 'Application Data' folder for all users3


Input: [Variable name] Favorites [User-defined] No [Value]

Output: The Internet Explorer "Favorites" folder


Input: [Variable name] CommonFavorites [User-defined] No [Value]

Output: The "Favorites" folder for all users


Input: [Variable name] TempPath [User-defined] No [Value]

Output: Temporary files folder


Input: [Variable name] WindowsPath [User-defined] No [Value]

Output: Windows folder


Input: [Variable name] CommonProgramsMenu [User-defined] No [Value]

Output: Common Programs menu folder


Input: [Variable name] CommonDesktopPath [User-defined] No [Value]

Output: Common Desktop folder


Input: [Variable name] CommonStartMenu [User-defined] No [Value]

Output: Common Start menu folder


Input: [Variable name] CommonStartupMenu [User-defined] No [Value]

Output: Common Startup menu folder


Input: [Variable name] UserProgramsMenu [User-defined] No [Value]

Output: User Programs menu folder


Input: [Variable name] UserStartMenu [User-defined] No [Value]

Output: User Start menu folder


Input: [Variable name] UserStartupMenu [User-defined] No [Value]

Output: User Startup menu folder


Input: [Variable name] UninstallCommand [User-defined] No [Value]

Output: Path to uninstaller executable


Input: [Variable name] UninstallLog [User-defined] No [Value]

Output: Path to uninstall log file


Input: [Key] h, j, k, l [Operation]

Output: left, down, up, right


Input: [Key] $ [Operation]

Output: To the end of the line


Input: [Key] ^ [Operation]

Output: To the beginning of the line


Input: [Key] G [Operation]

Output: To the end of the file


Input: [Key] :1 [Operation]

Output: To the beginning of the file


Input: [Key] :47 [Operation]

Output: To line 47


Input: [Values (default in bold)] true | false | Array [Description] Enable or disable minification. Optionally specify an array of advanced minification parameters. Currently the only advanced option is 'colors', which will compress all color values in any notation. [Option]

Output: minify


Input: [Values (default in bold)] block | single-line | padded [Description] Set the formatting mode. Overrides minify option if both are set. [Option]

Output: formatter


Input: [Values (default in bold)] use-platform | windows/win | unix [Description] Set the output style of newlines [Option]

Output: newlines


Input: [Values (default in bold)] true | false | Path [Description] Prepend a boilerplate to the output file [Option]

Output: boilerplate


Input: [Values (default in bold)] true | false [Description] Append a timestamped querystring to the output filename [Option]

Output: versioning


Input: [Values (default in bold)] Array [Description] An associative array of CSS variables to be applied at runtime. These will override variables declared globally or in the CSS. [Option]

Output: vars


Input: [Values (default in bold)] true | false [Description] Turn caching on or off. [Option]

Output: cache


Input: [Values (default in bold)] Path [Description] Specify an output directory for compiled files. Defaults to the same directory as the host file. [Option]

Output: output_dir


Input: [Values (default in bold)] Output filename [Description] Specify an output filename (suffix is added). [Option]

Output: output_file


Input: [Values (default in bold)] Path [Description] Directory for SVG and image files generated by plugins (defaults to the main file output directory). [Option]

Output: asset_dir


Input: [Values (default in bold)] false | true | Path [Description] Save compile stats and variables to a file in json format. [Option]

Output: stat_dump


Input: [Values (default in bold)] "all" | "moz", "webkit", ... | Array [Description] Limit aliasing to a specific vendor, or an array of vendors. [Option]

Output: vendor_target


Input: [Values (default in bold)] true | false | "absolute" [Description] Rewrite relative URLs inside inlined imported files. [Option]

Output: rewrite_import_urls


Input: [Values (default in bold)] Array [Description] An array of plugin names to enable. [Option]

Output: plugins


Input: [Values (default in bold)] true | false [Description] Output a source map (compliant with the Source Map v3 proposal). [Option]

Output: source_map


Input: [Values (default in bold)] Path [Description] Context for importing resources from relative urls (Only applies to `csscrush_string()` and command line utility). [Option]

Output: context


Input: [Values (default in bold)] Path [Description] Specify an alternative server document root for situations where the CSS is being served behind an alias or url rewritten path. [Option]

Output: doc_root


Input: [Values (default in bold)] Array [Description] An associative array of plugin and environment settings. Used primarily for plugin configuration. [Option]

Output: settings


Input: [Shortcut] ESC [What it does]

Output: Cancel current edit


Input: [Shortcut] Enter [What it does]

Output: Save current item and append a new item below it


Input: [Shortcut] CTRL+Enter [What it does]

Output: Save current item and append a new item above it


Input: [Shortcut] SHIFT+Enter [What it does]

Output: Save currently edited item and append a new item below it


Input: [Shortcut] CTRL+LeftArrow [What it does]

Output: Indent the item one time to the left. You can use this to create sub-items


Input: [Shortcut] CTRL+RightArrow [What it does]

Output: Indent the item one time to the right. You can use this to create sub-items


Input: [Shortcut] CTRL+UpArrow [What it does]

Output: Save current item and edit item above it


Input: [Shortcut] CTRL+DownArrow [What it does]

Output: Save current item and edit item below it


Input: [Shortcut] CTRL+B, CTRL+I [What it does]

Output: Insert syntax for bold or italic.


Input: [Shortcut] SHIFT+Click [What it does]

Output: Complete and move to history a sub-task or a recurring task (you need to hold Shift while checking it off).


Input: [Name] id [Description] The note ID [Permissions] Available to everyone on Facebook by default [Returns]

Output: A JSON string


Input: [Name] from [Description] The profile that created the note [Permissions] Available to everyone on Facebook by default [Returns]

Output: A JSON object containing id and name fields


Input: [Name] subject [Description] The title of the note [Permissions] Available to everyone on Facebook by default [Returns]

Output: A JSON string


Input: [Name] message [Description] The content of the note [Permissions] Available to everyone on Facebook by default [Returns]

Output: A JSON string containing HTML text


Input: [Name] created_time [Description] The time the note was initially published [Permissions] Available to everyone on Facebook by default [Returns]

Output: A JSON string containing a IETF RFC 3339 datetime


Input: [Name] updated_time [Description] The time the note was last updated [Permissions] Available to everyone on Facebook by default [Returns]

Output: A JSON string containing a IETF RFC 3339 datetime


Input: [Name] icon [Description] The icon that Facebook displays with notes [Permissions] Available to everyone on Facebook by default [Returns]

Output: A JSON string containing a valid URL


Input: [Attribute] getter= [Description]

Output: Use a custom name for the getter method.

Properties - Ry’s Objective-C Tutorial - RyPress


Input: [Attribute] setter= [Description]

Output: Use a custom name for the setter method.

Properties - Ry’s Objective-C Tutorial - RyPress


Input: [Attribute] readonly [Description]

Output: Don’t synthesize a setter method.

Properties - Ry’s Objective-C Tutorial - RyPress


Input: [Attribute] nonatomic [Description]

Output: Don’t guarantee the integrity of accessors in a multi-threaded environment. This is more efficient than the default atomic behavior.

Properties - Ry’s Objective-C Tutorial - RyPress


Input: [Attribute] strong [Description]

Output: Create an owning relationship between the property and the assigned value. This is the default for object properties.

Properties - Ry’s Objective-C Tutorial - RyPress


Input: [Attribute] weak [Description]

Output: Create a non-owning relationship between the property and the assigned value. Use this to prevent retain cycles.

Properties - Ry’s Objective-C Tutorial - RyPress


Input: [Attribute] copy [Description]

Output: Create a copy of the assigned value instead of referencing the existing instance.

Properties - Ry’s Objective-C Tutorial - RyPress


Input: [Option] -t threads [Description]

Output: Max count of concurrent DNS lookups (thread count) (default: 20, maximum: 400)

RDNSLOGS - Performs Reverse DNS lookups on Web Site Logs


Input: [Option] -v [Description]

Output: Verbosity switch. Use the -v switch only when you want to monitor the state of RDNSLOGS. It generates copious amounts of output and generally slows the program.

RDNSLOGS - Performs Reverse DNS lookups on Web Site Logs


Input: [Option] -r [Description]

Output: Recursively visit all configuration files specified by CONFIGFILE command

RDNSLOGS - Performs Reverse DNS lookups on Web Site Logs


Input: [Option] -n [Description]

Output: NO subnet host lookups. Default is to perform the subnet host lookups.

RDNSLOGS - Performs Reverse DNS lookups on Web Site Logs


Input: [Option] -l logfile [Description]

Output: You specified a log file specification on the command line. i.e. -l c:\logs\*.gz You can specify as many log file specs as can fit on a command line provided that each spec is preceded with a -l. If a log file spec contains a space, surround the spec with quotes. If a log file spec is made, a configuration file does not need to be specified.

RDNSLOGS - Performs Reverse DNS lookups on Web Site Logs


Input: [Option] -o dnscache [Description]

Output: You specify the desired DNS cache output filename.

RDNSLOGS - Performs Reverse DNS lookups on Web Site Logs


Input: [Option] -y DNS server [Description]

Output: Querying a specific DNS server. Use this switch to specify a particular DNS server to query. Not specifying the switch will make RDNSLOGS revert back to the default method of resolving names.

RDNSLOGS - Performs Reverse DNS lookups on Web Site Logs


Input: [Option] -x max tries [Description]

Output: Specifies the maximum number of attempts to resolve an IP address. Specifying 0 forces an indefinite attempt toward resolving the IP address. Works in conjunction with the -y switch. Default is 3 tries.

RDNSLOGS - Performs Reverse DNS lookups on Web Site Logs


Input: [Option] -m timeout [Description]

Output: Specifies the base timeout value for a lookup. If a lookup fails, the timeout value is doubled, up to a maximum of 60 secs, on the next and subsequent attempts. Works in conjunction with the -y switch. Default base timeout is 4 secs.

RDNSLOGS - Performs Reverse DNS lookups on Web Site Logs


Input: [Option] -c [Description]

Output: New in v6.0: Convert IP addresses to domain names in files. Creates *.trans files. Original files are not modified.

RDNSLOGS - Performs Reverse DNS lookups on Web Site Logs


Input: [Option] -b [Description]

Output: New in v6.0: Bypass Reverse Lookup. Used with -c switch. Use existing dnscache for file translation.

RDNSLOGS - Performs Reverse DNS lookups on Web Site Logs


Input: [Method Signature] getName() [Explanation]

Output: Returns the name of the plugin. This will be the name that will show up on the list of installed plugins. You should definately redefine this method, since the default implementation returns Undefined

Overview of the class NucleusPlugin (redefinable methods)


Input: [Method Signature] getAuthor() [Explanation]

Output: Returns the name of author of the plugin. This name will show up on the list of installed plugins. You should definately redefine this method, since the default implementation returns Undefined


Input: [Method Signature] getURL() [Explanation]

Output: Returns the URL of the site where the plugin can be downloaded, or where additional information about the plugin can be found. If no such site exists, a mailto:-link with the authors email address is appropriate. You should definately redefine this method, since the default implementation returns Undefined


Input: [Method Signature] getDescription() [Explanation]

Output: Returns a longer description of the plugin. This will show up on the list of installed plugins. The default implementation returns Undefined


Input: [Method Signature] getVersion() [Explanation]

Output: Returns the current version of the plugin. Returns 0.0 by default


Input: [Method Signature] getMinNucleusVersion() [Explanation]

Output: (v2.0b) Returns the minimum required Nucleus version. By default, this returns 155 (v1.55). If you are using plugin features that were introduced later, please implement this function (e.g. v2.0 => 200). Please note that Nucleus v1.55 does not use this function at all, so it remains possible to install newer plugins there, even if they use newer features.


Input: [Method Signature] getMinNucleusPatchLevel() [Explanation]

Output: (v3.1) Returns the minimum required Nucleus patch level that needs to be present when running the minimal required Nucleus version (getMinNucleusVersion). By default, this returns 0. This function is generally used when new plugin features are available only as patches to the latest released Nucleus version.


Input: [Method Signature] init() [Explanation]

Output: Initializes the plugin. This method gets called immediately after the plugin object is created and the plugid-attribute has been set. By default, this method does nothing.


Input: [Method Signature] doSkinVar($skinType) [Explanation]

Output: When plugins are called using the <%plugin(...)%>-skinvar, this method will be called. the $skinType parameter contains the type of skin (item, archive, ...) from where the plugin is called. Don't get confused by the fact that there's only one parameter. Multiple parameters can still be passed. More info on implementing the doSkinVar method. By default, this method does no output at all.


Input: [Method Signature] doTemplateVar(&$item) [Explanation]

Output: Basically the same as doSkinVar, but this time for calls of the <%plugin(...)%>-var in templates (item header/body/footer and dateheader/footer). By default, this method forwards the handling to the doSkinVar-method, using template as skintype. More information on implementing the doTemplateVar method


Input: [Method Signature] doTemplateCommentsVar(&$item, &$comment) [Explanation]

Output: (v2.0b) Basically the same as doSkinVar, but this time for calls of the <%plugin(...)%>-var in templates (comments-related parts). By default, this method forwards the handling to the doSkinVar-method, using template as skintype. More information on implementing the doTemplateCommentsVar method


Input: [Method Signature] doItemVar(&$item, &$param) [Explanation]

Output: (v3.30) Basically the same as doSkinVar, but this time for calls of the <%plugin(...)%>-var in an item. &$item provides the full item object of the item in which the ItemVar appears and &$param the parameters of the ItemVar.


Input: [Method Signature] doIf($key, $value) [Explanation]

Output: (v3.30) Evaluates a custom conditional statement for the if/ifnot/elseif/elseifnot skin variables. Must return either true or false. $key and $value are strings passed from the if/ifnot/elseif/elseifnot skin variable. Normally, the plugin should check whether $key has the value of $value, but other uses are possible. Plugins that make use of this method, should document its use for users of the plugin.


Input: [Method Signature] doAction($type) [Explanation]

Output: When a plugin wants to allow user interaction, it can allow actions through action.php. This is the script that Nucleus uses itself to handle new comments and karma votes. Called with the correct parameters, the doAction-method from a plugin can be called. The $type contains an optional message type. Extra variables from the request can be accessed from within the doAction method. By default, this method returns a string No Such Action which will trigger an error message. More info on doAction.


Input: [Method Signature] install() [Explanation]

Output: This method gets called on the moment the plugin is installed. It can perform initializing actions, such as the creation of database tables, the creation of plugin options, etc... By default, this method does nothing.


Input: [Method Signature] unInstall() [Explanation]

Output: Called when the plugin is uninstalled. It's a good thing to clean up information your plugin created in the database at this point. By default, this method does nothing.


Input: [Method Signature] getEventList() [Explanation]

Output: Plugins can subscribe to events. Events get generated whenever Nucleus performs a certain action. An AddItem event for example, will call all plugins that subscribed to this event. The called method will be event_AddItem($params). The $params-parameter is an associative array containing several fields of information, like the itemid for AddItem. Returns an empty array by default, indicating that the plugin does not subscribe to any event at all. More information about events.


Input: [Method Signature] getTableList() [Explanation]

Output: This method should return an array of database tables that the plugin has created. It's used in the backup feature that Nucleus offers, so plugin tables are also included in the backup. By default, returns an empty array.


Input: [Method Signature] hasAdminArea() [Explanation]

Output: Should return 1 if the plugin has an admin area of its own, and 0 if it doesn't. By default, 0 is returned.


Input: [Method Signature] getPluginDep() [Explanation]

Output: (v3.2) Returns an array of plugin names. Nucleus refuses to install the plugin if any of these plugins is not installed. By default, an empty array is returned. More information on plugin dependencies.


Input: [Shortcut Keys] Alt + F [Description]

Output: File menu options in current program.


Input: [Shortcut Keys] Alt + E [Description]

Output: Edit options in current program


Input: [Shortcut Keys] F1 [Description]

Output: Universal Help in almost every Windows program.


Input: [Shortcut Keys] Ctrl + A [Description]

Output: Select all text.


Input: [Shortcut Keys] Ctrl + F [Description]

Output: Open find window for current document or window.


Input: [Shortcut Keys] Ctrl + X [Description]

Output: Cut selected item.


Input: [Shortcut Keys] Shift + Del [Description]

Output: Cut selected item.


Input: [Shortcut Keys] Ctrl + C [Description]

Output: Copy selected item.


Input: [Shortcut Keys] Ctrl + Ins [Description]

Output: Copy selected item


Input: [Shortcut Keys] Ctrl + V [Description]

Output: Paste


Input: [Shortcut Keys] Shift + Ins [Description]

Output: Paste


Input: [Shortcut Keys] Ctrl + P [Description]

Output: Print the current page or document.


Input: [Shortcut Keys] Home [Description]

Output: Goes to beginning of current line.


Input: [Shortcut Keys] Ctrl + Home [Description]

Output: Goes to beginning of document.


Input: [Shortcut Keys] End [Description]

Output: Goes to end of current line.


Input: [Shortcut Keys] Ctrl + End [Description]

Output: Goes to end of document.


Input: [Shortcut Keys] Shift + Home [Description]

Output: Highlights from current position to beginning of line.


Input: [Shortcut Keys] Shift + End [Description]

Output: Highlights from current position to end of line.


Input: [Shortcut Keys] Ctrl + Left arrow [Description]

Output: Moves one word to the left at a time.


Input: [Shortcut Keys] Ctrl + Right arrow [Description]

Output: Moves one word to the right at a time.


Input: [Code] c [Meaning]

Output: A char


Input: [Code] i [Meaning]

Output: An int


Input: [Code] s [Meaning]

Output: A short


Input: [Code] l [Meaning]

Output: A long. l is treated as a 32-bit quantity on 64-bit programs.


Input: [Code] q [Meaning]

Output: A long long


Input: [Code] C [Meaning]

Output: An unsigned char


Input: [Code] I [Meaning]

Output: An unsigned int


Input: [Code] S [Meaning]

Output: An unsigned short


Input: [Code] L [Meaning]

Output: An unsigned long


Input: [Code] Q [Meaning]

Output: An unsigned long long


Input: [Code] f [Meaning]

Output: A float


Input: [Code] d [Meaning]

Output: A double


Input: [Code] B [Meaning]

Output: A C++ bool or a C99 _Bool


Input: [Code] v [Meaning]

Output: A void


Input: [Code] * [Meaning]

Output: A character string (char *)


Input: [Code] @ [Meaning]

Output: An object (whether statically typed or typed id)


Input: [Code] # [Meaning]

Output: A class object (Class)


Input: [Code] : [Meaning]

Output: A method selector (SEL)


Input: [Code] [array type] [Meaning]

Output: An array


Input: [Code] {name=type…} [Meaning]

Output: A structure


Input: [Code] (name=type…) [Meaning]

Output: A union


Input: [Code] bnum [Meaning]

Output: A bit field of num bits


Input: [Code] ^type [Meaning]

Output: A pointer to type


Input: [Code] ? [Meaning]

Output: An unknown type (among other things, this code is used for function pointers)


Input: [Value] 2305.0 [Name]

Output: gssr_id

Run Browser : Browse : Sequence Read Archive : NCBI/NLM/NIH


Input: [Value] snap [Name]

Output: instrument_name

Run Browser : Browse : Sequence Read Archive : NCBI/NLM/NIH


Input: [Value] BROAD:SEQUENCING_SAMPLE:2305.0 [Name]

Output: lsid

Run Browser : Browse : Sequence Read Archive : NCBI/NLM/NIH


Input: [Value] R127 [Name]

Output: project

Run Browser : Browse : Sequence Read Archive : NCBI/NLM/NIH


Input: [Value] 2 [Name]

Output: region

Run Browser : Browse : Sequence Read Archive : NCBI/NLM/NIH


Input: [Value] 612106060621 [Name]

Output: run_barcode

Run Browser : Browse : Sequence Read Archive : NCBI/NLM/NIH


Input: [Value] Aureli1997ListeriaLongRun612106 [Name]

Output: run_name

Run Browser : Browse : Sequence Read Archive : NCBI/NLM/NIH


Input: [FORM NAME] SMA [DESCRIPTION]

Output: Service mark Application

Kansas Secretary of State - Trademark / Service mark


Input: [FORM NAME] TMA [DESCRIPTION]

Output: Trademark Application

Kansas Secretary of State - Trademark / Service mark


Input: [FORM NAME] TSR [DESCRIPTION]

Output: Trademark or Service mark Renewal

Kansas Secretary of State - Trademark / Service mark


Input: [FORM NAME] TSS [DESCRIPTION]

Output: Trademark or Service mark Assignment

Kansas Secretary of State - Trademark / Service mark


Input: [FORM NAME] TSC [DESCRIPTION]

Output: Trademark or Service mark Cancellation

Kansas Secretary of State - Trademark / Service mark


Input: [FORM NAME] TSN [DESCRIPTION]

Output: Trademark Service Mark Name Change of Registrant/Owner

Kansas Secretary of State - Trademark / Service mark


Input: [Value] Spybot - Search & Destroy [Property]

Output: Product name


Input: [Value] Safer-Networking Ltd. [Property]

Output: Company name


Input: [Value] Scanner Service [Property]

Output: File description


Input: [Value] SDFSSvc.exe [Property]

Output: Original filename


Input: [Value] © 2009-2011 Safer-Networking Ltd. All rights reserved. [Property]

Output: Legal copyright


Input: [Value] Spybot® and Spybot - Search & Destroy® are registered trademarks. [Property]

Output: Legal trademark


Input: [Value] 2.0.3.0 [Property]

Output: Product version


Input: [Value] 2.0.3.160 [Property]

Output: File version


Input: [Function] setDotsPerMeterX() [Description]

Output: Defines the aspect ratio by setting the number of pixels that fit horizontally in a physical meter.


Input: [Function] setDotsPerMeterY() [Description]

Output: Defines the aspect ratio by setting the number of pixels that fit vertically in a physical meter.


Input: [Function] fill() [Description]

Output: Fills the entire image with the given pixel value.


Input: [Function] invertPixels() [Description]

Output: Inverts all pixel values in the image using the given InvertMode value.


Input: [Function] setColorTable() [Description]

Output: Sets the color table used to translate color indexes. Only monochrome and 8-bit formats.


Input: [Function] setColorCount() [Description]

Output: Resizes the color table. Only monochrome and 8-bit formats.


Input: [Parameter] USER [Description]

Output: The user as which the watchdog service runs


Input: [Parameter] ROTATE [Default] 10 [Description]

Output: Number of log files; 0 disables log rotation


Input: [Parameter] LOGSIZE [Default] 1MB [Description]

Output: Maximum size of a log file in bytes to trigger rotation


Input: [Parameter] LOGINTERVAL [Default] 1 day [Description]

Output: Maximum time interval in seconds to trigger log rotation


Input: [Parameter] BALLOON_INTERVAL [Default] 30000 [Description]

Output: Interval for checking the balloon size (msec)


Input: [Parameter] BALLOON_INCREMENT [Default] 256 [Description]

Output: Balloon size increment (MByte)


Input: [Parameter] BALLOON_DECREMENT [Default] 128 [Description]

Output: Balloon size decrement (MByte)


Input: [Parameter] BALLOON_LOWERLIMIT [Default] 64 [Description]

Output: Balloon size lower limit (MByte)


Input: [Parameter] BALLOON_SAFETYMARGIN [Default] 1024 [Description]

Output: Free memory required for decreasing the balloon size (MByte)


Input: [Character] B [Font style]

Output: Bold


Input: [Character] I [Font style]

Output: Italic


Input: [Character] N [Font style]

Output: Normal


Input: [Character] Q [Font style]

Output: Opaque


Input: [Character] - [Font style]

Output: Strikeout


Input: [Character] T [Font style]

Output: Transparent


Input: [Character] U [Font style]

Output: Underline


Input: [Step One] Step Two

Output: Go to the Groundspeak website at Groundspeak.com, or click the "Track Travel Bugs" icon on the left side of the screen. There you will see a scarab with a entry field. Enter the bug's 6 digit code in that field and click the arrow. The six digit code is the "Secret Code" that allows only people who have actually handled the bug to make notes or create movement for the bug. Keep this code a secret - making sure that it's not in the log or in any photos. Unscrupulous cachers could potentially wreak havoc by grabbing a bug they never really had and moving it to a cache in India. You also might want to write the bug's number down in case you want to write a note to the bug page. When you put the bug back into play, you don't get the opportunity to tell part of the story unless you make a note. You'll need that number to be able to make a note on the page.

Log the cache that you found the bug in. It would be nice if you also mentioned on the cache page that you found the bug and grabbed it, but it is not necessary.


Input: [Step One] Step Three

Output: Once you click the arrow, you'll be taken to the bug's page. Take the time to read any goals that the bug might have. Click the "Found it? Log it!" link in the upper right hand corner.

Log the cache that you found the bug in. It would be nice if you also mentioned on the cache page that you found the bug and grabbed it, but it is not necessary.


Input: [Step One] Step Four

Output: On the form, make sure the drop down says "I have it!", then you'll need to enter that 6 digit code AGAIN as a verification. You also have the opportunity to have the system notify you each time this bug moves, and make any and all comments you feel appropriate. Once you complete this step, the bug is in your "inventory." You can have multiple bugs in your inventory. If you just want to add to the story, or tell the portion of the story from when you picked up the bug to when you placed it, make sure the drop down says "Making a note". Sometimes, there is a quirk on the site that even when you're making a note, it will grab the bug. Just be away that this might happen.

Log the cache that you found the bug in. It would be nice if you also mentioned on the cache page that you found the bug and grabbed it, but it is not necessary.


Input: [Step One] Step Five

Output: Take the bug out into the real world, photograph it, have fun, and eventually place it in a new cache - hopefully one that helps the bug on its mission.

Log the cache that you found the bug in. It would be nice if you also mentioned on the cache page that you found the bug and grabbed it, but it is not necessary.


Input: [Step One] Step Six

Output: Once the bug is placed in a real cache, go back to the Geocaching.com site for that cache and log your visit as normal.

Log the cache that you found the bug in. It would be nice if you also mentioned on the cache page that you found the bug and grabbed it, but it is not necessary.


Input: [Step One] Step Seven

Output: As you're filling out the form for logging the cache, you have a new drop down at the bottom of the screen (this won't appear if you don't have any bugs in your inventory). Choose the bug you're dropping off. If you've been to the cache previously, you do not need to log this as a "Found it!" to drop off the bug. It can be done as a Post a Note or a Couldn't Find it! - although that doesn't make logical sense. Once you click the button Click to log your visit!, the bug will appear as being in that cache. Your job is done!!!

Log the cache that you found the bug in. It would be nice if you also mentioned on the cache page that you found the bug and grabbed it, but it is not necessary.


Input: [Class Name] container [Description] Constrains the content to a 580px wrapper on large screens (95% on small screens) and centers it within the body. [Element Type]

Output: table


Input: [Class Name] row [Description] Separates each row of content. [Element Type]

Output: table


Input: [Class Name] wrapper [Description] Wraps each .columns table, in order to create a gutter between columns and force them to expand to full width on small screens. [Element Type]

Output: td


Input: [Class Name] last [Description] Class applied to the last .wrapper td in each row in order for the gutter to work properly. If you only have one (presumably full-width) .columns table (and therefore one .wrapper td) in a row, the .wrapper td still needs to have the last class applied to it. [Element Type]

Output: td


Input: [Class Name] {number} [Description] Can be any number between one and twelve (spelled out). Used to determine how wide your .columns tables are. The number of columns in each row should add up to 12, including offset columns . [Element Type]

Output: table


Input: [Class Name] columns [Description] Table that displays as n-twelfths of the width of the 580px .container table on large screens, and expands to the full width of the .container table on small screens. [Element Type]

Output: table


Input: [Class Name] expander [Description] An empty (and invisible) element added after the content element in a .columns table. It forces the content td to expand to the full width of the screen on small devices, instead of just the width of the content within the td. [Element Type]

Output: td


Input: [Name] allowIf [Default Value] false [Description]

Output: Allow assignment within the conditional expression of an if statement


Input: [Name] allowFor [Default Value] false [Description]

Output: Allow assignment within the conditional expression of a for statement


Input: [Name] allowWhile [Default Value] false [Description]

Output: Allow assignment within the conditional expression of a while statement


Input: [Name] allowTernary [Default Value] false [Description]

Output: Allow assignment within the conditional expression of a ternary operator


Input: [Name] allowTernaryResults [Default Value] false [Description]

Output: Allow assignment within the result expressions of a ternary operator


Input: [Name] allowIncrementDecrement [Default Value] false [Description]

Output: Allow increment or decrement operators within the conditional expression of an if, for, or while statement


Input: [Class] ComponentBase [Description]

Output: This class can be used as the base class for UNO components.

com.sun.star.lib.uno.helper (Java UNO Runtime Reference)

Class Summary


Input: [Class] Factory [Description]

Output: Factory helper class supporting com.sun.star.lang.XServiceInfo and com.sun.star.lang.XSingleComponentFactory.

com.sun.star.lib.uno.helper (Java UNO Runtime Reference)

Class Summary


Input: [Class] InterfaceContainer [Description]

Output: This class is a container for interfaces.

com.sun.star.lib.uno.helper (Java UNO Runtime Reference)

Class Summary


Input: [Class] PropertySet [Description]

Output: This class is an implementation of the interfaces com.sun.star.beans.XPropertySet, com.sun.star.beans.XFastPropertySet and com.sun.star.beans.XMultiPropertySet.

com.sun.star.lib.uno.helper (Java UNO Runtime Reference)

Class Summary


Input: [Class] PropertySetMixin [Description]

Output: A helper mixin to implement certain UNO interfaces related to property set handling on top of the attributes of a given UNO interface type.

com.sun.star.lib.uno.helper (Java UNO Runtime Reference)

Class Summary


Input: [Class] PropertySetMixin.BoundListeners [Description]

Output: A class used by clients of PropertySetMixin when implementing UNO interface type attribute setter functions.

com.sun.star.lib.uno.helper (Java UNO Runtime Reference)

Class Summary


Input: [Class] UnoUrl [Description]

Output: Object representation and parsing of Uno Urls, which allow to locate a named Uno object in a different process.

com.sun.star.lib.uno.helper (Java UNO Runtime Reference)

Class Summary


Input: [Class] WeakAdapter [Description]

Output: An XAdapter implementation that holds a weak reference (java.lang.ref.WeakReference) to an object.

com.sun.star.lib.uno.helper (Java UNO Runtime Reference)

Class Summary


Input: [Class] WeakBase [Description]

Output: This class can be used as the base class for UNO components.

com.sun.star.lib.uno.helper (Java UNO Runtime Reference)

Class Summary


Input: [Corresponding instance type] BlobValue [Usage] Binary value with a MIME type [DataType]

Output: BlobDataType


Input: [Corresponding instance type] BooleanValue [Usage] Boolean value [DataType]

Output: BooleanDataType


Input: [Corresponding instance type] ColorValue [Usage] Represents a color [DataType]

Output: ColorDataType


Input: [Corresponding instance type] CurrencyValue [Usage] An amount of money in a specified currency [DataType]

Output: CurrencyDataType


Input: [Corresponding instance type] EnumeratedValue [Usage] Enumerated set of values [DataType]

Output: EnumeratedDataType


Input: [Corresponding instance type] ExtentValue [Usage] An extent, captured by width and length [DataType]

Output: ExtentDataType


Input: [Corresponding instance type] FloatValue [Usage] Double-precision floating point with a possible range [DataType]

Output: FloatDataType


Input: [Corresponding instance type] IntegerValue [Usage] Integer with a possible range [DataType]

Output: IntegerDataType


Input: [Corresponding instance type] MultiplicityValue [Usage] Multiplicity in a RelationshipType [DataType]

Output: MultiplicityDataType


Input: [Corresponding instance type] PointValue [Usage] A point in a two-dimensional plane [DataType]

Output: PointDataType


Input: [Corresponding instance type] StringValue [Usage] A string [DataType]

Output: StringDataType


Input: [Corresponding instance type] TimePeriodValue [Usage] A period of time, aka duration [DataType]

Output: TimePeriodDataType


Input: [Corresponding instance type] TimeStampValue [Usage] A point in time [DataType]

Output: TimeStampDataType


Input: [Foreign type] integer [Prolog type] integer [C type] PlLong [Description of the C type]

Output: value of the integer


Input: [Foreign type] positive [Prolog type] positive integer [C type] PlLong [Description of the C type]

Output: value of the integer


Input: [Foreign type] float [Prolog type] floating point number [C type] double [Description of the C type]

Output: value of the floating point number


Input: [Foreign type] number [Prolog type] number [C type] double [Description of the C type]

Output: value of the number


Input: [Foreign type] atom [Prolog type] atom [C type] PlLong [Description of the C type]

Output: internal key of the atom


Input: [Foreign type] boolean [Prolog type] boolean [C type] PlLong [Description of the C type]

Output: value of the boolean (0=false, 1=true)


Input: [Foreign type] char [Prolog type] character [C type] PlLong [Description of the C type]

Output: value of (the code of) the character


Input: [Foreign type] code [Prolog type] character code [C type] PlLong [Description of the C type]

Output: value of the character-code


Input: [Foreign type] byte [Prolog type] byte [C type] PlLong [Description of the C type]

Output: value of the byte


Input: [Foreign type] in_char [Prolog type] in-character [C type] PlLong [Description of the C type]

Output: value of the character or -1 for end-of-file


Input: [Foreign type] in_code [Prolog type] in-character code [C type] PlLong [Description of the C type]

Output: value of the character-code or -1 for end-of-file


Input: [Foreign type] in_byte [Prolog type] in-byte [C type] PlLong [Description of the C type]

Output: value of the byte or -1 for the end-of-file


Input: [Foreign type] string [Prolog type] atom [C type] char * [Description of the C type]

Output: C string containing the name of the atom


Input: [Foreign type] chars [Prolog type] character list [C type] char * [Description of the C type]

Output: C string containing the characters of the list


Input: [Foreign type] codes [Prolog type] character-code list [C type] char * [Description of the C type]

Output: C string containing the characters of the list


Input: [Foreign type] term [Prolog type] Prolog term [C type] PlTerm [Description of the C type]

Output: generic Prolog term


Input: [Attribute] name [Description]

Output: The name for the attribute that this tag file accepts. The value for the name attribute must be unique throughout the current tag file.

Easy Custom Tags with Tag Files, Part 1 | Java.net


Input: [Attribute] required [Description]

Output: Indicates whether this attribute is required. The value can be true or false (default).

Easy Custom Tags with Tag Files, Part 1 | Java.net


Input: [Attribute] fragment [Description]

Output: Indicates whether this attribute is a fragment to be evaluated by the tag handler, or a normal attribute to be evaluated by the container prior to being passed to the tag handler. The value is either true or false (default). The value is true if this attribute is to be evaluated by the tag handler.

Easy Custom Tags with Tag Files, Part 1 | Java.net


Input: [Attribute] rtexprvalue [Description]

Output: Specifies whether the attribute's value may be dynamically calculated at runtime by a scriplet expression. The value is either true (default) or false.

Easy Custom Tags with Tag Files, Part 1 | Java.net


Input: [Attribute] type [Description]

Output: The type of the attribute value. The default is java.lang.String.

Easy Custom Tags with Tag Files, Part 1 | Java.net


Input: [Attribute] description [Description]

Output: The description of this attribute.

Easy Custom Tags with Tag Files, Part 1 | Java.net


Input: [Parameter] id [Value] Unique identifier [Description] Used to link TWISTYSHOW, TWISTYHIDE and TWISTYTOGGLE. [Remark]

Output: required


Input: [Parameter] mode [Value] "div" or "span" [Description] Specify if the Twisty Toggle section will use a or a tag. Note that if the contents contains block elements such as div, mode should be div as well to create valid HTML markup. [Remark]

Output: optional, defaults to


Input: [Parameter] class [Value] CSS class name [Description] Class for content div or span [Remark]

Output: optional, default none


Input: [Parameter] remember [Value] "on", "off" [Description] If "on", the Twisty state is remembered the next time the page is shown. If "off", the stored setting will be cleared. Note: when used, think carefully about a unique name (id) for the Twisty, otherwise the cookie that is set might affect other Twisties with the same name. Also note that only interaction is stored, not the state of the Twisty when left unclicked. [Remark]

Output: optional, no default


Input: [Parameter] start [Value] "hide" or "show" [Description] Initial state of the Twisty; this will override any setting stored in a cookie (see remember). [Remark]

Output: optional, default no initial state


Input: [Parameter] firststart [Value] "hide" or "show" [Description] Initial state of the Twisty the first time the visitor gets to see the Twisty; this will NOT override cookie settings (see remember). [Remark]

Output: optional, default no initial state


Input: [Parameter] noscript [Value] "hide" [Description] Make content hidden in case use does not have JavaScript on [Remark]

Output: optional, default content is shown with no JavaScript


Input: [Description] Use this parameter to set the strategy for resolving ambiguous location names. ignore - the Routing Service will simply use the first location found for an address. check - the Routing Service will return a full list of the possible location matches in the collections attribute of the response. Default = 'ignore' [Request Parameter]

Output: ambiguities String

Directions Web Service - MapQuest Platform


Input: [Description] Specifies the format of the request. If this parameter is not supplied, the input format is assumed to be JSON-formatted text. The JSON-formatted input text must be supplied as either the "json" parameter of an HTTP GET, or as the BODY of an HTTP POST. If this parameter is "xml", the XML-formatted input text must be supplied as either the "xml" parameter of an HTTP GET, or as the BODY of an HTTP POST. Must be one of the following, if supplied: json xml Defaults to 'json' when using POST; otherwise it determines which to use based on parameters given. [Request Parameter]

Output: inFormat

Directions Web Service - MapQuest Platform


Input: [Description] This parameter, if present, should contain the JSON-formatted text of the request. Use this parameter if you want to submit your request in JSON format, but do not want to use an HTTP POST to submit body text. Note: Remember to URL-escape the text in this parameter! [Request Parameter]

Output: json

Directions Web Service - MapQuest Platform


Input: [Description] This parameter, if present, should contain the XML-formatted text of the request. Use this parameter if you want to submit your request in XML format, but do not want to use an HTTP POST to submit body text. Note: Remember to URL-escape the text in this parameter! [Request Parameter]

Output: xml

Directions Web Service - MapQuest Platform


Input: [Description] Specifies the format of the response. Must be one of the following, if supplied: json xml Default = 'json' [Request Parameter]

Output: outFormat

Directions Web Service - MapQuest Platform


Input: [Description] A JavaScript function name. The JSON-formatted response will be wrapped in a call to the supplied callback function name to provide JSONP functionality. This functionality might be needed to do cross-site scripting. See the Wikipedia.org entry for JSON for more details. [Request Parameter]

Output: callback

Directions Web Service - MapQuest Platform


Input: [Key] prefixes [Info]

Output: A list of all announced prefixes + the timelines when they were visible.


Input: [Key] prefix [Info]

Output: The announced prefix.


Input: [Key] timelines [Info]

Output: All the timelines when the prefix was announced.


Input: [Key] starttime [Info]

Output: Start time of this period.


Input: [Key] endtime [Info]

Output: End time of this period.


Input: [Key] query_starttime [Info]

Output: The start of the time the query covers.


Input: [Key] query_endtime [Info]

Output: The end of the time the query covers.


Input: [Key] latest_time & earliest_time [Info]

Output: Holds the latest and the earliest time data is available for.


Input: [Key] resource [Info]

Output: The resource used for the query.


Input: [#] 1 [Compared item] Repository format [CVS] CVS is based on RCS files of versions control. Each file connected to CVS is an ordinary file containing some additional information. It is quite natural that the tree of these files repeats the file tree in the local directory. Thus, with CVS you should not be anxious about data loss, and you can easily correct RCS files if necessary. [SVN]

Output: The basis of SVN is a relational database (BerkleyDB) either set of binary files (FS_FS). On one hand, this settles many problems (for example, concurrent access through the file share) and enables new functionalities (for example, transactions at operations performance). However, on the other hand, data storage now is not transparent, or at least is not available for user interference. That is why the utilities for "curing" and "recovering" of the repository (database) are provided.


Input: [#] 2 [Compared item] Speed [CVS] CVS works more slowly. [SVN]

Output: As a whole, due to some constructive solutions, SVN really works faster than CVS. It transmits less information through the network and supports more operations for offline mode. However, there is the reverse of the medal. Speed increasing is achieved basically at the expense of full backup of all work files on your computer.


Input: [#] 3 [Compared item] Tags & Branches (!!! IMPORTANT) [CVS] To our point of view, these are implemented properly. [SVN]

Output: The SVN developers assert with pride that they have got rid of 3 measurements by working with tags and branches. In practice it means that they have substituted both concepts for a capability of copying file(s) or directories within the repository with saving the history of changes. That is, both tag creation and branch creation are substituted for copying within the repository. From the SVN developers' viewpoint, this is very elegant decision, which simplifies one's life. However, we think that there is nothing to be proud of. As for branches, everything is not so bad, now branches are nothing but separate folders in the repository, which earlier have had some interconnection. As for tags, everything is much worse. Now you cannot tag a code, this function is simply missing. Certainly, to some extent this is compensated by universal numbering of files in SVN, that is, the whole repository gets the version number, but not each separate file. However, we suppose you will not deny that it is not very convenient to store a four- digit number instead of a symbolic tag.


Input: [#] 4 [Compared item] Meta data [CVS] CVS allows to store of only files and nothing else. [SVN]

Output: SVN allows to "attach" to a file any number of all possible named attributes. Excellent functionality, but it is not quite clear what it is necessary for.


Input: [#] 5 [Compared item] File types [CVS] CVS was initially intended for text data storage. That is why storage of other files (binary, unicode) is not trivial and requires special information, as well as adjustments on either server or client sides. [SVN]

Output: SVN manipulates all the file types and does not require your instructions.


Input: [#] 6 [Compared item] Rollback [CVS] CVS allows to rollback any commit in the repository, even if this may require some time (each file should be processed independently) [SVN]

Output: SVN does not allow rollback of commit. Authors suggest copy good repository state to the end of trunk to overwrite bad commit. However bad commit itself will remain in repository.


Input: [#] 7 [Compared item] Transactions [CVS] In CVS the support of transactions by the principle "all or nothing" is completely absent. For example, when you checkin several files (transfer them to the server), it is possible that the operation will be completed only for some of these files, and will not be completed for the rest (due to conflicts, for example). As a rule, it is sufficient to correct the situation and to repeat the operation for the remaining files (not for all files). That is, the files will be checked in in two steps. No cases of the repository damage due to absence of this functionality were observed. [SVN]

Output: SVN does support transactions by the principle "all or nothing". Probably this is an advantage of the system.


Input: [#] 8 [Compared item] Availability [CVS] Presently CVS is supported everywhere where you might need it. [SVN]

Output: SVN not yet so widly used, as the result there are places where it support still not implemented.


Input: [#] 9 [Compared item] Internal architecture and code. [CVS] CVS is very old system. Initially CVS was written as bunch of scripts around RCS executable. Later this packaged into single executable. But internal structure of code is poor and have lots of historical fixes. Till now there was several attempts to rewrite CVS from scratch, but as it is known without success. We, personally, tried to extract client code to make better integration between plug-in and CVS, but without success. Right now we not think that CVS may grows too much in its functionality. [SVN]

Output: Subversion authors really spent some time on internal SVN architecture. Still not know how good are some decisions they make. But one is clear, the code is well expandable, and future improvements are coming.


Input: [Compared item] Total score [CVS] 4 [SVN]

Output: 5


Input: [XML Tag] TFSName [Description] The uniform resource identifier (URI) of the team project collection. The format for the URI is as follows: http://ServerName:Port/VirtualDirectoryName/CollectionName If no virtual directory is used, the format for the URI is as follows: http://ServerName:Port/CollectionName [Parameter]

Output: CollectionURI

frichter-it-blog | A blog dedicated to helping System Administrators


Input: [XML Tag] LogFolder [Description] The location of the folder where you want the log file to be written. The log file that will be created is named TEAMPROJECT.log, and it will contain the events from running the batch file command. For example, you can specify “C:\” for the log folder name. If you leave the value for the folder location blank, the log file will be written to %temp% and will be named following the naming conventions for logs that the New Project Creation Wizard generates. You can locate the log file by navigating to the following directory: $:\Documents and Settings\user name\Local Settings\Temp\VSTS_TeamProjectCreation_yyyy_mm_dd_hh_mm_ss.log. [Parameter]

Output: LogFolderName

frichter-it-blog | A blog dedicated to helping System Administrators


Input: [XML Tag] ProjectName [Description] The name of the upgraded team project to be provisioned. You must specify the name of a team project that is defined in the project collection that you specified in the CollectionURI parameter. [Parameter]

Output: TeamProjectName

frichter-it-blog | A blog dedicated to helping System Administrators


Input: [XML Tag] AddFeaturesToExistingProject [Description] Specify true to indicate that you are adding features to an existing team project and false to indicate that you are creating a team project. [Parameter]

Output: true | false

frichter-it-blog | A blog dedicated to helping System Administrators


Input: [XML Tag] ProjectReportsEnabled [Description] Specify true to provision a report site and false to exclude provisioning a report site. [Parameter]

Output: true | false

frichter-it-blog | A blog dedicated to helping System Administrators


Input: [XML Tag] ProjectReportsForceUpload [Description] Specify true to cause reports in the process template to be uploaded to the report site and falseto exclude the upload of reports. [Parameter]

Output: true | false

frichter-it-blog | A blog dedicated to helping System Administrators


Input: [XML Tag] ProjectSiteEnabled [Description] Specify true to enable the team project portal site and false to maintain the site as disabled for the team project. [Parameter]

Output: true | false

frichter-it-blog | A blog dedicated to helping System Administrators


Input: [XML Tag] ProjectSiteWebApplication [Description] Specifies the friendly name (not the URL) to the SharePoint Web application (for example, Team Project Portal). By default, the URL and the friendly name are the same. [Parameter]

Output: SharePointWebApp

frichter-it-blog | A blog dedicated to helping System Administrators


Input: [XML Tag] ProjectSitePath [Description] The relative site path where you want the project portal site to be created (for example, sites/DefaultCollection/MyProject). Note The site path that you specify must correspond to a Web site application that has been added to the team project collection where the team project is defined. For more information, see Add a SharePoint Web Application to Your Deployment. The relative site path corresponds to the home page of the project portal. [Parameter]

Output: PortalSitePath

frichter-it-blog | A blog dedicated to helping System Administrators


Input: [XML Tag] ProjectSiteTitle [Description] (Optional) If you want a project portal name that differs from the team project name, you can type a name that is easily identified by your team members. [Parameter]

Output: ProjectSiteTitle

frichter-it-blog | A blog dedicated to helping System Administrators