DOCSLIB.ORG

Draft for Public Comment Australian Standard

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Draft for Public Comment Australian Standard COMMITTEE CT-002 DR 03657 (Project ID: 2496) Draft for Public Comment Australian Standard LIABLE TO ALTERATION—DO NOT USE AS A STANDARD BEGINNING DATE 30 December 2003 FOR COMMENT: CLOSING DATE 2 March 2004 FOR COMMENT: Digital television—Requirements for receivers Part 1: 7 MHz VHF/UHF DVB-T television broadcasts (Revision of AS 4933.1—2000) PRICE CODE: D COPYRIGHT Draft for Public Comment Australian Standard The committee responsible for the issue of this draft comprised representatives of organizations interested in the subject matter of the proposed Standard. These organizations are listed on the inside back cover. Comments are invited on the technical content, wording and general arrangement of the draft. The preferred method for submission of comment is to download the MS Word comment form found at http://www.standards.com.au/Catalogue/misc/Public%20Comment%20Form.doc. This form also includes instructions and examples of comment submission. When completing the comment form ensure that the number of this draft, your name and organization (if applicable) is recorded. Please place relevant clause numbers beside each comment. Editorial matters (i.e. spelling, punctuation, grammar etc.) will be corrected before final publication. The coordination of the requirements of this draft with those of any related Standards is of particular importance and you are invited to point out any areas where this may be necessary. Please provide supporting reasons and suggested wording for each comment. Where you consider that specific content is too simplistic, too complex or too detailed please provide an alternative. If the draft is acceptable without change, an acknowledgment to this effect would be appreciated. When completed, this form should be returned to the Projects Manager, Bala Balakrishnan via email to [email protected]. Normally no acknowledgment of comment is sent. All comments received electronically by the due date will be put before the relevant drafting committee. Because Standards committees operate electronically we cannot guarantee that comments submitted in hard copy will be considered along with those submitted electronically. Where appropriate, changes will be incorporated before the Standard is formally approved. If you know of other persons or organizations that may wish to comment on this draft Standard, could you please advise them of its availability. Further copies of the draft are available from the Customer Service Centre listed below and from our website at http://www.standards.com.au/. STANDARDS AUSTRALIA Customer Service Centre Telephone: 1300 65 46 46 Facsimile: 1300 65 49 49 e-mail: mailto:[email protected] Internet: http://www.standards.com.au/ Draft for Public Comment STANDARDS AUSTRALIA Committee CT-002—Broadcasting and Related Services Subcommittee CT-002-02 (CT/2/A) — TB Receiving Equipment DRAFT Australian Standard Digital television—Requirements for receivers Part 1: 7 MHz VHF/UHF DVB-T television broadcasts (Revision of AS 4933.1—2000) (To be AS 4933.1—200X) This draft proposes to provide television receiver manufacturers with the technical specifications and requirements of digital television receivers in order to achieve successful reception from free-to-air DTTB transmissions that comply with the Australian DTTB transmission Standard AS 4599 (including current Amendments). Comment on the draft is invited from people and organizations concerned with this subject. It would be appreciated if those submitting comment would follow the guidelines given on the inside front cover. This document is a draft Australian Standard only and is liable to alteration in the light of comment received. It is not to be regarded as an Australian Standard until finally issued as such by Standards Australia. 2496-PDR 22/12/2003 DRAFT ONLY 2 DRAFT ONLY PREFACE This Standard was prepared by the Joint Standards Australia/Standards New Zealand Committee CT 002, Broadcasting and Related Services. It is the result of a consensus among the representatives to the Joint Committee to produce it as an Australian Standard. The objective of this Standard is to provide television receiver manufacturers with the technical specifications and requirements of digital television receivers in order to achieve successful reception from free-to-air DTTB transmissions that comply with the Australian DTTB transmission Standard: AS 4599, (including current Amendments) Digital television—Terrestrial broadcasting— Characteristics of digital terrestrial television transmissions. Interoperability issues for DVB-S, DVB-C and Datacasting are not addressed in this part of the Standard. The terms ‘normative’ and ‘informative’ have been used in this Standard to define the application of the Appendix to which they apply. A ‘normative’ Appendix is an integral part of a Standard, whereas an ‘informative’ Appendix is only for information and guidance. Informative sections are included also in the main body of this standard. 2496-PDR 22/12/2003 DRAFT ONLY 3 DRAFT ONLY CONTENTS PREFACE……….......................................................................................................................2 SECTION 1 SCOPE AND APPLICATION ...........................................................................11 1.1 Scope……................................................................................................................. 11 1.2 Application................................................................................................................ 11 SECTION 2 REFERENCED DOCUMENTS .........................................................................13 SECTION 3 ESSENTIAL AND OPTIONAL REQUIREMENTS..........................................16 3.1 RECEIVER REQUIREMENTS ............................................................................... 16 1 Basic features ................................................................................................17 1.1 Minimum requirements for Terrestrial Reception—Performance .......... 17 1.2 Receive capability for analogue PAL transmissions............................... 18 1.3 Australian regulatory and safety requirements........................................ 18 1.3.1 Electrical safety.......................................................................18 1.3.2 EMC........................................................................................18 1.4 Receiver display resolution specification................................................ 18 2 Power on operations ......................................................................................18 2.1 First time operation initialization ............................................................ 18 2.2 Subsequent switch-on.............................................................................. 18 2.3 Identifying new services in current or new location ............................... 19 2.4 Stand-By Power ..................................................................................... 19 3 User Operation ..............................................................................................19 3.1 Operating system..................................................................................... 19 3.2 Hardware reset ........................................................................................ 19 3.3 Initial Set-Up........................................................................................... 19 3.3.1 Set-up Menu and Non-volatile information storage.................19 3.3.2 Initial tuning scan (Virgin Mode) ...........................................19 3.4 Assigning Numbering to Services and navigation .................................. 19 3.4.1 Menu List of Services..............................................................19 3.4.2 Logical Channel Numbering (LCN) ........................................20 3.4.3 Services without LCNs............................................................20 3.4.4 Duplicated LCNs and Service (Channel) list editing. ..............21 3.4.5 Linkage Descriptor..................................................................21 3.4.6 Dynamic response to PAT, PMT, NIT and SDT updates.........21 3.5 Display Electronic Services Guide (OSD) and navigation ..................... 22 3.6 Signal quality monitor............................................................................. 22 3.7 Selection of radio services....................................................................... 22 3.8 Service unavailable— On-screen advice:................................................ 22 3.9 Remote Control ....................................................................................... 22 4 RF Characteristics, COFDM Demodulation and Channel decoding...............23 4.1 RF Characteristics ................................................................................... 23 4.1.1 Transmission channel bandwidth.............................................23 4.1.2 Notional receiver noise figure ................................................23 4.1.3 RF connector ...........................................................................23 4.1.4 Digital terrestrial receiver tuner’s frequency range..................23 4.1.5 Channel Offsets.......................................................................23 4.1.6 COFDM Intermediate Frequency (IF) and Spectrum polarity..23 2496-PDR 22/12/2003 DRAFT ONLY 4 DRAFT ONLY 4.2 Operation in Single Frequency Network (SFN) Environments .............. 24 4.3 COFDM modes .....................................................................................
Load more

Recommended publications
  • Wireless October 1985 85P
    Wireless October 1985 85p 68000 computer board Memory expansion Switched -mode power supply Multi-standard digital terminal Australia AS 3.30 Spain Pts. 370.00 Denmark DKr. 38.00 Switzerland SFr. 8.00 Germany DM 7.00 Singapore MS 7.00 Holland DPI. 9.00 U.S.A. S 4.00 Italy. L 4200 www.americanradiohistory.com DUAL TRACE THE ANSWER TEKOSCILLOSCOPES BY ANY MEASURE Now! Tek quality and expert advice are just a free phone call away... Our National Order Desk line gets you fast delivery of the industry's leading value/ performance portables... and technical advice from experts! The 60MHz 2213A, 2215A and the 100MHz 2235 and 2236 These UK offer unprecedented reliability anufactured 'scopes are and affordability, plus the obtainable through the industry's first 3 year warranty National Order Desk. Call us on labour and parts, CRT to order or obtain literature, included. or to talk to our expert on All 2200 series scopes scope applications. have the bandwidth for digital ..talk circuits and sensitivity for low signal analogue measurement. The sweep speeds for fast logic families, and delayed sweep for to Pete fast, accurate timing Dial 100 and ask for measurement. The top of the range 2236 combines a Freefone Tek- scope counter/timer/DMM with the Tektronix UK Ltd scope to provide fast, easy Fourth Avenue, Globe Park, measurements for voltage, Marlow, Bucks SL7 1YD Tel: (06284) 6000 resistance and temperature. Telex: 847277 & 847378 The Company reserves the right to modify designs, speci'ications and change prices without notice. Tektronix (:I)MMI1Fflll.If 1.IIItNI.1 CIRCLE 1 FOR FURTHER INFORMATION www.americanradiohistory.com Editor ELECTRONICS PHILIP DARRINGTON Deputy Editor GEOFFREY SHORTER, B.Sc.
    [Show full text]
  • Kaleido-X User's Manual
    Kaleido-X User’s Manual Part Number: M770-2800-111 1 June 2011 Copyright © 2007-2011 Miranda Technologies Inc. All rights reserved. ATTENTION: please read the following terms and conditions carefully. By using Kaleido-X documentation, you agree to the following terms and conditions: Miranda Technologies Inc. hereby grants permission and license to owners of Kaleido-X to use their product manuals for their own internal business use. Manuals for Miranda Technologies Inc. products may not be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose unless specifically authorized in writing by Miranda Technologies Inc. A Miranda Technologies Inc. manual may have been revised to reflect changes made to the product during its manufacturing life. Thus, different versions of a manual may exist for any given product. Care should be taken to ensure that one obtains the proper manual version for a specific product serial number. Information in this document is subject to change without notice and does not represent a commitment on the part of Miranda Technologies Inc. Title Kaleido-X User’s Manual Part Number M770-2800-111 Revision 1 June 2011, 4:37 pm ii Table of Contents 1 New Features 1 Overview. 1 New Feature in Kaleido-X Version 5.30. 1 Features Introduced in Kaleido-X Version 5.20 . 2 Features Introduced in Kaleido-X Version 5.10 . 2 2 Getting Started 5 About this Document . 5 System Overview. 6 Kaleido-Modular . 6 Kaleido-X16. 8 Kaleido-X (4RU) . 10 Kaleido-X (7RU) . 11 Kaleido-X (7RU) x 2 Expansion .
    [Show full text]
  • Introduction to Closed Captions
    TECHNICAL PAPER Introduction to Closed Captions By Glenn Eguchi Senior Computer Scientist April 2015 © 2015 Adobe Systems Incorporated. All rights reserved. If this whitepaper is distributed with software that includes an end user agreement, this guide, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. Except as permitted by any such license, no part of this guide may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of Adobe Systems Incorporated. Please note that the content in this guide is protected under copyright law even if it is not distributed with software that includes an end user license agreement. The content of this guide is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or inaccuracies that may appear in the informational content contained in this guide. This article is intended for US audiences only. Any references to company names in sample templates are for demonstration purposes only and are not intended to refer to any actual organization. Adobe and the Adobe logo, and Adobe Primetime are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. Adobe Systems Incorporated, 345 Park Avenue, San Jose, California 95110, USA. Notice to U.S. Government End Users.
    [Show full text]
  • Powerserver Configuration Guide for .NET
    PowerServer Configuration Guide for .NET Appeon® PowerServer® 2017 (on .NET) FOR WINDOWS DOCUMENT ID: ADC20240-01-0700-01 LAST REVISED: October 27, 2017 Copyright © 2000-2017 by Appeon Limited. All rights reserved. This publication pertains to Appeon software and to any subsequent release until otherwise indicated in new editions or technical notes. Information in this document is subject to change without notice. The software described herein is furnished under a license agreement, and it may be used or copied only in accordance with the terms of that agreement. No part of this publication may be reproduced, transmitted, or translated in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without the prior written permission of Appeon Limited. Appeon, the Appeon logo, Appeon PowerBuilder, Appeon PowerServer, PowerServer, PowerServer Toolkit, AEM, and PowerServer Web Component are trademarks of Appeon Limited. SAP, Sybase, Adaptive Server Anywhere, SQL Anywhere, Adaptive Server Enterprise, iAnywhere, Sybase Central, and Sybase jConnect for JDBC are trademarks or registered trademarks of SAP and SAP affiliate company. Java and JDBC are trademarks or registered trademarks of Sun Microsystems, Inc. All other company and product names used herein may be trademarks or registered trademarks of their respective companies. Use, duplication, or disclosure by the government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of DFARS 52.227-7013 for the DOD and as set forth in FAR 52.227-19(a)-(d) for civilian agencies. Appeon Limited, 1/F, Shell Industrial Building, 12 Lee Chung Street, Chai Wan District, Hong Kong. Contents 1 About This Book ...................................................................................................
    [Show full text]
  • DVB); Specification for Service Information (SI) in DVB Systems
    Final draft ETSI EN 300 468 V1.5.1 (2003-01) European Standard (Telecommunications series) Digital Video Broadcasting (DVB); Specification for Service Information (SI) in DVB systems European Broadcasting Union Union Européenne de Radio-Télévision EBU·UER 2 Final draft ETSI EN 300 468 V1.5.1 (2003-01) Reference REN/JTC-DVB-128 Keywords broadcasting, digital, DVB, MPEG, service, TV, video ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, send your comment to: [email protected] Copyright Notification No part may be reproduced except as authorized by written permission.
    [Show full text]
  • International Register of Coded Character Sets to Be Used with Escape Sequences for Information Interchange in Data Processing
    INTERNATIONAL REGISTER OF CODED CHARACTER SETS TO BE USED WITH ESCAPE SEQUENCES 1 Introduction 1.1 General This document is the ISO International Register of Coded Character Sets To Be Used With Escape Sequences for information interchange in data processing. It is compiled in accordance with the provisions of ISO/IEC 2022, "Code Extension Technique" and of ISO 2375 "Procedure for Registration of Escape Sequences". This International Register contains coded character sets which have been registered in accordance with procedures given in ISO 2375. Its purpose is to identify widely used coded character sets and associate with each a unique escape sequence by means of which it can be designated according to ISO/IEC 2022 and ISO/IEC 4873. The publication of this International Register should promote compatibility in international information interchange and avoid duplication of effort in developing application-oriented coded character sets. Registration provides an identification for a coded character set but implies nothing about its status; it may or may not be part of a standard of an international, national or a corporate body. However, if such a standard is published subsequently to the registration, it would be appropriate for the escape sequence identifying the character set to be specified in the standard. If it is desired to register a set, application should be made to the Registration Authority through an appropriate Sponsoring Authority as specified in ISO 2375. Any character set can be a candidate for registration if it meets the requirements of ISO 2375. The Registration Authority ascertains that the proposals received are formally in accordance with this International Standard, technically in accordance with ISO/IEC 2022, and, where applicable, with ISO/IEC 646 and ISO/IEC 4873, and meet the presentation practice of the Registration Authority.
    [Show full text]
  • Windows Mbox Viewer User Manual 1.0.2.6 Table of Contents 1 Modification History
    Windows MBox Viewer User Manual 1.0.2.6 Table of Contents 1 Modification History.......................................................................................................................3 2 Feedback..........................................................................................................................................3 3 Overview.........................................................................................................................................4 4 Installation.......................................................................................................................................4 5 Running the MBox viewer..............................................................................................................4 5.1 Argument List Summary..............................................................................................................4 5.2 Setting Options from GUI............................................................................................................5 5.3 Basic Use Case.............................................................................................................................6 5.4 Mail Context Menu.......................................................................................................................7 5.5 Mail Archive Context menu.........................................................................................................8 5.6 Mail Attachments..........................................................................................................................9
    [Show full text]
  • (Tech 3264) to Ebu-Tt Subtitle Files
    TECH 3360 EBU-TT, PART 2 MAPPING EBU STL (TECH 3264) TO EBU-TT SUBTITLE FILES VERSION 1.0 SOURCE: SP/MIM – XML SUBTITLES Geneva May 2017 There are blank pages throughout this document. This document is paginated for two sided printing Tech 3360 - Version 1.0 EBU-TT Part 2 - EBU STL Mapping to EBU-TT Conformance Notation This document contains both normative text and informative text. All text is normative except for that in the Introduction, any section explicitly labelled as ‘Informative’ or individual paragraphs which start with ‘Note:’ Normative text describes indispensable or mandatory elements. It contains the conformance keywords ‘shall’, ‘should’ or ‘may’, defined as follows: ‘Shall’ and ‘shall not’: Indicate requirements to be followed strictly and from which no deviation is permitted in order to conform to the document. ‘Should’ and ‘should not’: Indicate that, among several possibilities, one is recommended as particularly suitable, without mentioning or excluding others. OR indicate that a certain course of action is preferred but not necessarily required. OR indicate that (in the negative form) a certain possibility or course of action is deprecated but not prohibited. ‘May’ and ‘need not’: Indicate a course of action permissible within the limits of the document. Default identifies mandatory (in phrases containing “shall”) or recommended (in phrases containing “should”) values that can, optionally, be overwritten by user action or supplemented with other options in advanced applications. Mandatory defaults must be supported. The support of recommended defaults is preferred, but not necessarily required. Informative text is potentially helpful to the user, but it is not indispensable and it does not affect the normative text.
    [Show full text]
  • [MS-UCODEREF]: Windows Protocols Unicode Reference
    [MS-UCODEREF]: Windows Protocols Unicode Reference Intellectual Property Rights Notice for Open Specifications Documentation . Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies. Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL's, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft Open Specification Promise or the Community Promise. If you would prefer a written license, or if the technologies described in the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected]. Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights.
    [Show full text]
  • Beocollectors.Com
    Þ»±Ê·•·±² ߪ¿²¬ ÎÚ îèŒ ú ߪ¿²¬ ÎÚ íîŒ Þ»±Ê·•·±² ߪ¿²¬ ÎÚ ÝÌÊ Ì§°» èíí¨ô èìí¨ Ì§°» èíé¨ Í»®ª·½» Ó¿²«¿´ Û²¹´·•¸ô Ù»®³¿²ô Ú®»²½¸ô ׬¿´·¿²ô Í°¿²·•¸ BeoCollectors.com BeoCollectors.com BeoCollectors.com BeoCollectors.com ÓßÍÌÛÎ Ô×ÒÕ Ð·² ï Ü¿¬¿ó óðòîëÊ oðòïÊ ½¿¬·±² ¬± ±¬¸»® ÌÊ ¬®¿²•³·••·±² •§•¬»³• øÌÊ ±²´§÷ з² î Ü¿¬¿õ õðòîëÊ oðòïÊ Ì§°» ͧ•¬»³ Ó±¼ò ÊÌΠ̧°» ÞñÙ ÞñÙñÔñÔŽñ×ñÜñÕ ÞñÙñÔñ×ñÓñÜñÕ Í§•¬»³ B з² í ÓÔ •»²•» èìíð ÞñÙ ÛË ÞñÙ ììëí ÞñÙ øßî ÞñÙ÷ èðððîçì èðððîçë ±® ììëï Þñ٠з² ìóïð ÒòÝò øßîô Ò×ÝßÓ ÞñÙ÷ èìíî ×ñÓñÜñÕ ØÕ × ììëç ×ñÜñÕ øÒ×ÝßÓ ×÷ î èðððîçì î eoз² ïï ó•«°°´§ ª±´¬¿¹» óéÊ ¬± óïëÊ ø·² •¬¿²¼¾§ óíÊ ¬± óïëÊ÷ èìíí × ÙÞ × ììëç ×ñÜñÕ øÒ×ÝßÓ ×÷ ï ï èðððîçë èìíì ÞñÙ ×ÌßÔÇ ÞñÙ ììëí ÞñÙ øßî ÞñÙ÷ èðððîçì èðððîçë з² ïî õ•«°°´§ ª±´¬¿¹» õéÊ ¬± õïëÊ ø·² •¬¿²¼¾§ õíÊ ¬± õïëÊ÷ èìíë ÞñÙ ßËÍ ÞñÙ ììëí ÞñÙ øßî ÞñÙ÷ èðððîçì èðððîçë ±® ììëï Þñ٠з² ïí ß«¼·± óÔ ïÊ Þ¿´ô η² îòîÓ±¸³•ô ᫬ é뱸³• øßîô Ò×ÝßÓ ÞñÙ÷ èìíê ÞñÙñÜñÕ ÛÛË ÞñÙ ììëê ÞñÙñÜñÕ ï èðððîçë з² ïì ß«¼·± õÔ ïÊ Þ¿´ô η² îòîÓ±¸³•ô ᫬ éëÓ±¸³• øßîô Ò×ÝßÓ ÞñÙñÜñÕ÷ èìíé ÞñÙñ×ñÓñÜñÕ Ìß× ÞñÙ ììëí ÞñÙ øßî ÞñÙ÷ èðððîçì î C з² ïë ß«¼·± óÎ ïÊ Þ¿´ô η² îòîÓ±¸³•ô ᫬ é뱸³• ±® ììëï ÞñÙ øßîô Ò×ÝßÓ ÞñÙ÷ з² ïê ß«¼·± õÎ ïÊ Þ¿´ô η² îòîÓ±¸³•ô ᫬ é뱸³• èìíè ÞñÙñÔñÔŽ ÚøÙÞ÷ ÞñÙ ììëë ÞñÙñÔñÔŽñ× ï èðððîçë ßî ÞñÙô o Ò×ÝßÓ ÞñÙñÔñ×÷ ÍóÊØÍ Ð·² ï Ç ÙÒÜ ll з² î Ý ÙÒÜ Ð·² í Ô«³·²¿²½» ·² øÇ÷ ï Ê°° éë ±¸³• e з² ì ݸ®±³·²¿²½» ·² øÝ÷ ï Ê°° éë ±¸³• ½¿¬·±² ¬± ±¬¸»® ÌÊ ¬®¿²•³·••·±² •§•¬»³• øÌÊ ±²´§÷ ̧°» ͧ•¬»³ Ó±¼ò ÊÌΠ̧°» ÞñÙ ÞñÙñÔñÔŽñ×ñÜñÕ ÞñÙñÔñ×ñÓñÜñÕ Ê×ÜÛÑ Ý±³°±•·¬» ª·¼»± ·² ïÊ°° éë ±¸³• ͧ•¬»³ c èííð ÞñÙ ÛË ÞñÙ ììëí
    [Show full text]
  • Appeon Server Configuration Guide for .NET*
    Appeon Server Configuration Guide for .NET* Appeon® 6.0 for PowerBuilder® WINDOWS Not available in Sybase Distribution. For differences of distributions, refer to the Distributions section in Introduction to Appeon. DOCUMENT ID: DC00812-01-0600-03 LAST REVISED: July 2008 Copyright © 2008 by Appeon Corporation. All rights reserved. This publication pertains to Appeon software and to any subsequent release until otherwise indicated in new editions or technical notes. Information in this document is subject to change without notice. The software described herein is furnished under a license agreement, and it may be used or copied only in accordance with the terms of that agreement. No part of this publication may be reproduced, transmitted, or translated in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without the prior written permission of Appeon Corporation. Appeon, the Appeon logo, Appeon Developer, Appeon Enterprise Manager, AEM, Appeon Server and Appeon Server Web Component are trademarks or registered trademarks of Appeon Corporation. Sybase, Adaptive Server Anywhere, Adaptive Server Enterprise, iAnywhere and PowerBuilder, are trademarks or registered trademarks of Sybase, Inc. Java, JDBC and JDK are trademarks or registered trademarks of Sun, Inc. All other company and product names used herein may be trademarks or registered trademarks of their respective companies. Use, duplication, or disclosure by the government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of DFARS 52.227-7013 for the DOD and as set forth in FAR 52.227- 19(a)-(d) for civilian agencies. Appeon Corporation, 1/F, Shell Industrial Building, 12 Lee Chung Street, Chai Wan District, Hong Kong.
    [Show full text]
  • Unicode - I18N
    Encodings - Unicode - I18N Généralités......................................................................................................................................................................3 Locales............................................................................................................................................................................6 Locale..........................................................................................................................................................................6 Character encoding.....................................................................................................................................................6 Code pages..................................................................................................................................................................6 Codepage Identifiers...................................................................................................................................................7 GetCPInfo...................................................................................................................................................................9 setlocale.....................................................................................................................................................................10 Preprocessor directive...............................................................................................................................................12
    [Show full text]