1<?xml version="1.0" encoding="UTF-8"?> 2 3 4<!--*********************************************************** 5 * 6 * Licensed to the Apache Software Foundation (ASF) under one 7 * or more contributor license agreements. See the NOTICE file 8 * distributed with this work for additional information 9 * regarding copyright ownership. The ASF licenses this file 10 * to you under the Apache License, Version 2.0 (the 11 * "License"); you may not use this file except in compliance 12 * with the License. You may obtain a copy of the License at 13 * 14 * http://www.apache.org/licenses/LICENSE-2.0 15 * 16 * Unless required by applicable law or agreed to in writing, 17 * software distributed under the License is distributed on an 18 * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY 19 * KIND, either express or implied. See the License for the 20 * specific language governing permissions and limitations 21 * under the License. 22 * 23 ***********************************************************--> 24 25 26 27<helpdocument version="1.0"> 28<meta> 29<topic id="textsbasicshared00000002xml" indexer="include" status="PUBLISH"> 30<title id="tit" xml-lang="en-US">$[officename] Basic Glossary</title> 31<filename>/text/sbasic/shared/00000002.xhp</filename> 32</topic> 33<history> 34<created date="2003-10-31T00:00:00">Sun Microsystems, Inc.</created> 35<lastedited date="2004-10-18T15:28:23">dedr: fixed #i30799# 36fpe: added sections and sort element</lastedited> 37</history> 38</meta> 39<body> 40<paragraph role="heading" id="hd_id3145068" xml-lang="en-US" level="1" l10n="U" oldref="1"><link href="text/sbasic/shared/00000002.xhp" name="$[officename] Basic Glossary">$[officename] Basic Glossary</link></paragraph> 41<paragraph role="paragraph" id="par_id3150792" xml-lang="en-US" l10n="U" oldref="2">This glossary explains some technical terms that you may come across when working with $[officename] Basic.</paragraph> 42<sort order="asc"> 43<section id="dezimal"> 44<paragraph role="heading" id="hd_id3155133" xml-lang="en-US" level="2" l10n="U" oldref="7">Decimal Point</paragraph> 45<paragraph role="paragraph" id="par_id3156443" xml-lang="en-US" l10n="U" oldref="8">When converting numbers, $[officename] Basic uses the locale settings of the system for determining the type of decimal and thousand separator.</paragraph> 46<paragraph role="paragraph" id="par_id3153092" xml-lang="en-US" l10n="U" oldref="9">The behavior has an effect on both the implicit conversion ( 1 + "2.3" = 3.3 ) as well as the runtime function <link href="text/sbasic/shared/03102700.xhp" name="IsNumeric">IsNumeric</link>.</paragraph> 47</section> 48<section id="colors"> 49<paragraph role="heading" id="hd_id3155854" xml-lang="en-US" level="2" l10n="U" oldref="29">Colors</paragraph> 50<paragraph role="paragraph" id="par_id3145366" xml-lang="en-US" l10n="U" oldref="30">In $[officename] Basic, colors are treated as long integer value. The return value of color queries is also always a long integer value. When defining properties, colors can be specified using their RGB code that is converted to a long integer value using the <link href="text/sbasic/shared/03010305.xhp" name="RGB function">RGB function</link>.</paragraph> 51</section> 52<section id="measurementunits"> 53<paragraph role="heading" id="hd_id3146119" xml-lang="en-US" level="2" l10n="U" oldref="32">Measurement Units</paragraph> 54<paragraph role="paragraph" id="par_id3154013" xml-lang="en-US" l10n="CHG" oldref="33">In $[officename] Basic, a <emph>method parameter</emph> or a <emph>property</emph> expecting unit information can be specified either as integer or long integer expression without a unit, or as a character string containing a unit. If no unit is passed to the method the default unit defined for the active document type will be used. If the parameter is passed as a character string containing a measurement unit, the default setting will be ignored. The default measurement unit for a document type can be set under <emph><switchinline select="sys"><caseinline select="MAC">%PRODUCTNAME - Preferences</caseinline><defaultinline>Tools - Options</defaultinline></switchinline> - (Document Type) - General</emph>.</paragraph> 55</section> 56<section id="twips"> 57<bookmark xml-lang="en-US" branch="index" id="bm_id3145801"><bookmark_value>twips; definition</bookmark_value> 58</bookmark> 59<paragraph role="heading" id="hd_id3145801" xml-lang="en-US" level="2" oldref="5">Twips</paragraph> 60<paragraph role="paragraph" id="par_id3154731" xml-lang="en-US" l10n="U" oldref="6">A twip is a screen-independent unit which is used to define the uniform position and size of screen elements on all display systems. A twip is 1/1440th of an inch or 1/20 of a printer's point. There are 1440 twips to an inch or about 567 twips to a centimeter.</paragraph> 61</section> 62<section id="urlnotation"> 63<paragraph role="heading" id="hd_id3153159" xml-lang="en-US" level="2" l10n="U" oldref="106">URL Notation</paragraph> 64<paragraph role="paragraph" id="par_id3153415" xml-lang="en-US" l10n="U" oldref="108">URLs (<emph>Uniform Resource Locators</emph>) are used to determine the location of a resource like a file in a file system, typically inside a network environment. A URL consists of a protocol specifier, a host specifier and a file and path specifier:</paragraph> 65<paragraph role="paragraph" id="par_id3149121" xml-lang="en-US" l10n="U" oldref="107"> 66<emph>protocol</emph>://<emph>host.name</emph>/<emph>path/to/the/file.html</emph> 67</paragraph> 68<paragraph role="paragraph" id="par_id3168612" xml-lang="en-US" l10n="U" oldref="109">The most common usage of URLs is on the internet when specifying web pages. Example for protocols are <emph>http</emph>, <emph>ftp</emph>, or <emph>file</emph>. The <emph>file</emph> protocol specifier is used when referring to a file on the local file system.</paragraph> 69<paragraph role="paragraph" id="par_id3150324" xml-lang="en-US" l10n="U" oldref="110">URL notation does not allow certain special characters to be used. These are either replaced by other characters or encoded. A slash (<emph>/</emph>) is used as a path separator. For example, a file referred to as <emph>C:\My File.odt</emph> on the local host in "Windows notation" becomes <emph>file:///C|/My%20File.odt</emph> in URL notation.</paragraph> 70</section> 71</sort> 72</body> 73</helpdocument> 74