Import RISC OS distribution stuff. (3rd party modules, etc.)

This commit is contained in:
Michael Drake 2012-10-02 14:16:39 +01:00
parent 2f1ca751d6
commit e8312277a5
92 changed files with 2409 additions and 1 deletions

View File

@ -120,6 +120,6 @@ netsurf.zip: $(EXETARGET)
$(eval $@_TMPDIR := $(shell mktemp -d))
$(Q) $(RM) $@
rsync --archive --verbose $(CURDIR)/!NetSurf $($@_TMPDIR)
mv $($@_TMPDIR)/!NetSurf/ReadMe $($@_TMPDIR)
mv $($@_TMPDIR)/riscos/distribution/ReadMe $($@_TMPDIR)
cd $($@_TMPDIR) && /opt/netsurf/arm-unknown-riscos/env/bin/zip -9vr\, $(CURDIR)/$@ *
$(Q) $(RM) -rf $($@_TMPDIR)

View File

@ -0,0 +1,5 @@
| Unicode Boot file
|
Set Unicode$Dir <Obey$Dir>
SetMacro Unicode$Path <Unicode$Dir>.,Resources:$.Resources.Unicode.
IconSprites Unicode:!Sprites

View File

@ -0,0 +1 @@
This application contains resources for Unicode support in applications.

View File

@ -0,0 +1,5 @@
| Unicode Run file
|
Set Unicode$Dir <Obey$Dir>
SetMacro Unicode$Path <Unicode$Dir>.,Resources:$.Resources.Unicode.
IconSprites Unicode:!Sprites

Binary file not shown.

After

Width:  |  Height:  |  Size: 64 B

View File

@ -0,0 +1 @@
a˙b˙c˙d˙e˙f˙g˙h˙i˙j˙k˙l˙m˙n˙o˙p˙q˙r˙s˙t˙u˙v˙w˙x˙y˙z˙{˙|˙}˙~˙˙€˙<E282AC>˙˙<E2809A>˙„˙…˙†˙‡˙<E280A1>˙‰˙Š˙˙Ś˙Ť˙Ž˙Ź˙<C5B9>˙˙˙“˙”˙•˙˙—˙<E28094>˙™˙š˙˙ś˙ť˙ž˙ź˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙

File diff suppressed because one or more lines are too long

View File

@ -0,0 +1,303 @@
# > Unicode:Files.Aliases
# Mapping of character set encoding names to their canonical form
#
# Lines starting with a '#' are comments, blank lines are ignored.
#
# Based on http://www.iana.org/assignments/character-sets and
# http://www.iana.org/assignments/ianacharset-mib
#
# Canonical Form MIBenum Aliases...
#
US-ASCII 3 iso-ir-6 ANSI_X3.4-1986 ISO_646.irv:1991 ASCII ISO646-US ANSI_X3.4-1968 us IBM367 cp367 csASCII
ISO-10646-UTF-1 27 csISO10646UTF1
ISO_646.basic:1983 28 ref csISO646basic1983
INVARIANT 29 csINVARIANT
ISO_646.irv:1983 30 iso-ir-2 irv csISO2IntlRefVersion
BS_4730 20 iso-ir-4 ISO646-GB gb uk csISO4UnitedKingdom
NATS-SEFI 31 iso-ir-8-1 csNATSSEFI
NATS-SEFI-ADD 32 iso-ir-8-2 csNATSSEFIADD
NATS-DANO 33 iso-ir-9-1 csNATSDANO
NATS-DANO-ADD 34 iso-ir-9-2 csNATSDANOADD
SEN_850200_B 35 iso-ir-10 FI ISO646-FI ISO646-SE se csISO10Swedish
SEN_850200_C 21 iso-ir-11 ISO646-SE2 se2 csISO11SwedishForNames
KS_C_5601-1987 36 iso-ir-149 KS_C_5601-1989 KSC_5601 korean csKSC56011987
ISO-2022-KR 37 csISO2022KR
EUC-KR 38 csEUCKR EUCKR
ISO-2022-JP 39 csISO2022JP
ISO-2022-JP-2 40 csISO2022JP2
ISO-2022-CN 104
ISO-2022-CN-EXT 105
JIS_C6220-1969-jp 41 JIS_C6220-1969 iso-ir-13 katakana x0201-7 csISO13JISC6220jp
JIS_C6220-1969-ro 42 iso-ir-14 jp ISO646-JP csISO14JISC6220ro
IT 22 iso-ir-15 ISO646-IT csISO15Italian
PT 43 iso-ir-16 ISO646-PT csISO16Portuguese
ES 23 iso-ir-17 ISO646-ES csISO17Spanish
greek7-old 44 iso-ir-18 csISO18Greek7Old
latin-greek 45 iso-ir-19 csISO19LatinGreek
DIN_66003 24 iso-ir-21 de ISO646-DE csISO21German
NF_Z_62-010_(1973) 46 iso-ir-25 ISO646-FR1 csISO25French
Latin-greek-1 47 iso-ir-27 csISO27LatinGreek1
ISO_5427 48 iso-ir-37 csISO5427Cyrillic
JIS_C6226-1978 49 iso-ir-42 csISO42JISC62261978
BS_viewdata 50 iso-ir-47 csISO47BSViewdata
INIS 51 iso-ir-49 csISO49INIS
INIS-8 52 iso-ir-50 csISO50INIS8
INIS-cyrillic 53 iso-ir-51 csISO51INISCyrillic
ISO_5427:1981 54 iso-ir-54 ISO5427Cyrillic1981
ISO_5428:1980 55 iso-ir-55 csISO5428Greek
GB_1988-80 56 iso-ir-57 cn ISO646-CN csISO57GB1988
GB_2312-80 57 iso-ir-58 chinese csISO58GB231280
NS_4551-1 25 iso-ir-60 ISO646-NO no csISO60DanishNorwegian csISO60Norwegian1
NS_4551-2 58 ISO646-NO2 iso-ir-61 no2 csISO61Norwegian2
NF_Z_62-010 26 iso-ir-69 ISO646-FR fr csISO69French
videotex-suppl 59 iso-ir-70 csISO70VideotexSupp1
PT2 60 iso-ir-84 ISO646-PT2 csISO84Portuguese2
ES2 61 iso-ir-85 ISO646-ES2 csISO85Spanish2
MSZ_7795.3 62 iso-ir-86 ISO646-HU hu csISO86Hungarian
JIS_C6226-1983 63 iso-ir-87 x0208 JIS_X0208-1983 csISO87JISX0208
greek7 64 iso-ir-88 csISO88Greek7
ASMO_449 65 ISO_9036 arabic7 iso-ir-89 csISO89ASMO449
iso-ir-90 66 csISO90
JIS_C6229-1984-a 67 iso-ir-91 jp-ocr-a csISO91JISC62291984a
JIS_C6229-1984-b 68 iso-ir-92 ISO646-JP-OCR-B jp-ocr-b csISO92JISC62991984b
JIS_C6229-1984-b-add 69 iso-ir-93 jp-ocr-b-add csISO93JIS62291984badd
JIS_C6229-1984-hand 70 iso-ir-94 jp-ocr-hand csISO94JIS62291984hand
JIS_C6229-1984-hand-add 71 iso-ir-95 jp-ocr-hand-add csISO95JIS62291984handadd
JIS_C6229-1984-kana 72 iso-ir-96 csISO96JISC62291984kana
ISO_2033-1983 73 iso-ir-98 e13b csISO2033
ANSI_X3.110-1983 74 iso-ir-99 CSA_T500-1983 NAPLPS csISO99NAPLPS
ISO-8859-1 4 iso-ir-100 ISO_8859-1 ISO_8859-1:1987 latin1 l1 IBM819 CP819 csISOLatin1 8859_1 ISO8859-1
ISO-8859-2 5 iso-ir-101 ISO_8859-2 ISO_8859-2:1987 latin2 l2 csISOLatin2 8859_2 ISO8859-2
T.61-7bit 75 iso-ir-102 csISO102T617bit
T.61-8bit 76 T.61 iso-ir-103 csISO103T618bit
ISO-8859-3 6 iso-ir-109 ISO_8859-3 ISO_8859-3:1988 latin3 l3 csISOLatin3 8859_3 ISO8859-3
ISO-8859-4 7 iso-ir-110 ISO_8859-4 ISO_8859-4:1988 latin4 l4 csISOLatin4 8859_4 ISO8859-4
ECMA-cyrillic 77 iso-ir-111 KOI8-E csISO111ECMACyrillic
CSA_Z243.4-1985-1 78 iso-ir-121 ISO646-CA csa7-1 ca csISO121Canadian1
CSA_Z243.4-1985-2 79 iso-ir-122 ISO646-CA2 csa7-2 csISO122Canadian2
CSA_Z243.4-1985-gr 80 iso-ir-123 csISO123CSAZ24341985gr
ISO-8859-6 9 iso-ir-127 ISO_8859-6 ISO_8859-6:1987 ECMA-114 ASMO-708 arabic csISOLatinArabic
ISO-8859-6-E 81 csISO88596E ISO_8859-6-E
ISO-8859-6-I 82 csISO88596I ISO_8859-6-I
ISO-8859-7 10 iso-ir-126 ISO_8859-7 ISO_8859-7:1987 ELOT_928 ECMA-118 greek greek8 csISOLatinGreek 8859_7 ISO8859-7
T.101-G2 83 iso-ir-128 csISO128T101G2
ISO-8859-8 11 iso-ir-138 ISO_8859-8 ISO_8859-8:1988 hebrew csISOLatinHebrew 8859_8 ISO8859-8
ISO-8859-8-E 84 csISO88598E ISO_8859-8-E
ISO-8859-8-I 85 csISO88598I ISO_8859-8-I
CSN_369103 86 iso-ir-139 csISO139CSN369103
JUS_I.B1.002 87 iso-ir-141 ISO646-YU js yu csISO141JUSIB1002
ISO_6937-2-add 14 iso-ir-142 csISOTextComm
IEC_P27-1 88 iso-ir-143 csISO143IECP271
ISO-8859-5 8 iso-ir-144 ISO_8859-5 ISO_8859-5:1988 cyrillic csISOLatinCyrillic 8859_5 ISO8859-5
JUS_I.B1.003-serb 89 iso-ir-146 serbian csISO146Serbian
JUS_I.B1.003-mac 90 macedonian iso-ir-147 csISO147Macedonian
ISO-8859-9 12 iso-ir-148 ISO_8859-9 ISO_8859-9:1989 latin5 l5 csISOLatin5 8859_9 ISO8859-9
greek-ccitt 91 iso-ir-150 csISO150 csISO150GreekCCITT
NC_NC00-10:81 92 cuba iso-ir-151 ISO646-CU csISO151Cuba
ISO_6937-2-25 93 iso-ir-152 csISO6937Add
GOST_19768-74 94 ST_SEV_358-88 iso-ir-153 csISO153GOST1976874
ISO_8859-supp 95 iso-ir-154 latin1-2-5 csISO8859Supp
ISO_10367-box 96 iso-ir-155 csISO10367Box
ISO-8859-10 13 iso-ir-157 l6 ISO_8859-10:1992 csISOLatin6 latin6 8859_10 ISO8859-10
latin-lap 97 lap iso-ir-158 csISO158Lap
JIS_X0212-1990 98 x0212 iso-ir-159 csISO159JISX02121990
DS_2089 99 DS2089 ISO646-DK dk csISO646Danish
us-dk 100 csUSDK
dk-us 101 csDKUS
JIS_X0201 15 X0201 csHalfWidthKatakana
KSC5636 102 ISO646-KR csKSC5636
ISO-10646-UCS-2 1000 csUnicode UCS-2 UCS2
ISO-10646-UCS-4 1001 csUCS4 UCS-4 UCS4
DEC-MCS 2008 dec csDECMCS
hp-roman8 2004 roman8 r8 csHPRoman8
macintosh 2027 mac csMacintosh MACROMAN MAC-ROMAN X-MAC-ROMAN
IBM037 2028 cp037 ebcdic-cp-us ebcdic-cp-ca ebcdic-cp-wt ebcdic-cp-nl csIBM037
IBM038 2029 EBCDIC-INT cp038 csIBM038
IBM273 2030 CP273 csIBM273
IBM274 2031 EBCDIC-BE CP274 csIBM274
IBM275 2032 EBCDIC-BR cp275 csIBM275
IBM277 2033 EBCDIC-CP-DK EBCDIC-CP-NO csIBM277
IBM278 2034 CP278 ebcdic-cp-fi ebcdic-cp-se csIBM278
IBM280 2035 CP280 ebcdic-cp-it csIBM280
IBM281 2036 EBCDIC-JP-E cp281 csIBM281
IBM284 2037 CP284 ebcdic-cp-es csIBM284
IBM285 2038 CP285 ebcdic-cp-gb csIBM285
IBM290 2039 cp290 EBCDIC-JP-kana csIBM290
IBM297 2040 cp297 ebcdic-cp-fr csIBM297
IBM420 2041 cp420 ebcdic-cp-ar1 csIBM420
IBM423 2042 cp423 ebcdic-cp-gr csIBM423
IBM424 2043 cp424 ebcdic-cp-he csIBM424
IBM437 2011 cp437 437 csPC8CodePage437
IBM500 2044 CP500 ebcdic-cp-be ebcdic-cp-ch csIBM500
IBM775 2087 cp775 csPC775Baltic
IBM850 2009 cp850 850 csPC850Multilingual
IBM851 2045 cp851 851 csIBM851
IBM852 2010 cp852 852 csPCp852
IBM855 2046 cp855 855 csIBM855
IBM857 2047 cp857 857 csIBM857
IBM860 2048 cp860 860 csIBM860
IBM861 2049 cp861 861 cp-is csIBM861
IBM862 2013 cp862 862 csPC862LatinHebrew
IBM863 2050 cp863 863 csIBM863
IBM864 2051 cp864 csIBM864
IBM865 2052 cp865 865 csIBM865
IBM866 2086 cp866 866 csIBM866
IBM868 2053 CP868 cp-ar csIBM868
IBM869 2054 cp869 869 cp-gr csIBM869
IBM870 2055 CP870 ebcdic-cp-roece ebcdic-cp-yu csIBM870
IBM871 2056 CP871 ebcdic-cp-is csIBM871
IBM880 2057 cp880 EBCDIC-Cyrillic csIBM880
IBM891 2058 cp891 csIBM891
IBM903 2059 cp903 csIBM903
IBM904 2060 cp904 904 csIBBM904
IBM905 2061 CP905 ebcdic-cp-tr csIBM905
IBM918 2062 CP918 ebcdic-cp-ar2 csIBM918
IBM1026 2063 CP1026 csIBM1026
EBCDIC-AT-DE 2064 csIBMEBCDICATDE
EBCDIC-AT-DE-A 2065 csEBCDICATDEA
EBCDIC-CA-FR 2066 csEBCDICCAFR
EBCDIC-DK-NO 2067 csEBCDICDKNO
EBCDIC-DK-NO-A 2068 csEBCDICDKNOA
EBCDIC-FI-SE 2069 csEBCDICFISE
EBCDIC-FI-SE-A 2070 csEBCDICFISEA
EBCDIC-FR 2071 csEBCDICFR
EBCDIC-IT 2072 csEBCDICIT
EBCDIC-PT 2073 csEBCDICPT
EBCDIC-ES 2074 csEBCDICES
EBCDIC-ES-A 2075 csEBCDICESA
EBCDIC-ES-S 2076 csEBCDICESS
EBCDIC-UK 2077 csEBCDICUK
EBCDIC-US 2078 csEBCDICUS
UNKNOWN-8BIT 2079 csUnknown8BiT
MNEMONIC 2080 csMnemonic
MNEM 2081 csMnem
VISCII 2082 csVISCII
VIQR 2083 csVIQR
KOI8-R 2084 csKOI8R
KOI8-U 2088
IBM00858 2089 CCSID00858 CP00858 PC-Multilingual-850+euro
IBM00924 2090 CCSID00924 CP00924 ebcdic-Latin9--euro
IBM01140 2091 CCSID01140 CP01140 ebcdic-us-37+euro
IBM01141 2092 CCSID01141 CP01141 ebcdic-de-273+euro
IBM01142 2093 CCSID01142 CP01142 ebcdic-dk-277+euro ebcdic-no-277+euro
IBM01143 2094 CCSID01143 CP01143 ebcdic-fi-278+euro ebcdic-se-278+euro
IBM01144 2095 CCSID01144 CP01144 ebcdic-it-280+euro
IBM01145 2096 CCSID01145 CP01145 ebcdic-es-284+euro
IBM01146 2097 CCSID01146 CP01146 ebcdic-gb-285+euro
IBM01147 2098 CCSID01147 CP01147 ebcdic-fr-297+euro
IBM01148 2099 CCSID01148 CP01148 ebcdic-international-500+euro
IBM01149 2100 CCSID01149 CP01149 ebcdic-is-871+euro
Big5-HKSCS 2101
IBM1047 2102 IBM-1047
PTCP154 2103 csPTCP154 PT154 CP154 Cyrillic-Asian
Amiga-1251 2104 Ami1251 Amiga1251 Ami-1251
KOI7-switched 2105
UNICODE-1-1 1010 csUnicode11
SCSU 1011
UTF-7 1012
UTF-16BE 1013
UTF-16LE 1014
UTF-16 1015
CESU-8 1016 csCESU-8
UTF-32 1017
UTF-32BE 1018
UTF-32LE 1019
BOCU-1 1020 csBOCU-1
UNICODE-1-1-UTF-7 103 csUnicode11UTF7
UTF-8 106 UNICODE-1-1-UTF-8 UNICODE-2-0-UTF-8 utf8
ISO-8859-13 109 8859_13 ISO8859-13
ISO-8859-14 110 iso-ir-199 ISO_8859-14:1998 ISO_8859-14 latin8 iso-celtic l8 8859_14 ISO8859-14
ISO-8859-15 111 ISO_8859-15 Latin-9 8859_15 ISO8859-15
ISO-8859-16 112 iso-ir-226 ISO_8859-16:2001 ISO_8859-16 latin10 l10
GBK 113 CP936 MS936 windows-936
GB18030 114
OSD_EBCDIC_DF04_15 115
OSD_EBCDIC_DF03_IRV 116
OSD_EBCDIC_DF04_1 117
JIS_Encoding 16 csJISEncoding
Shift_JIS 17 MS_Kanji csShiftJIS X-SJIS Shift-JIS
EUC-JP 18 csEUCPkdFmtJapanese Extended_UNIX_Code_Packed_Format_for_Japanese EUCJP
Extended_UNIX_Code_Fixed_Width_for_Japanese 19 csEUCFixWidJapanese
ISO-10646-UCS-Basic 1002 csUnicodeASCII
ISO-10646-Unicode-Latin1 1003 csUnicodeLatin1 ISO-10646
ISO-Unicode-IBM-1261 1005 csUnicodeIBM1261
ISO-Unicode-IBM-1268 1006 csUnicodeIBM1268
ISO-Unicode-IBM-1276 1007 csUnicodeIBM1276
ISO-Unicode-IBM-1264 1008 csUnicodeIBM1264
ISO-Unicode-IBM-1265 1009 csUnicodeIBM1265
ISO-8859-1-Windows-3.0-Latin-1 2000 csWindows30Latin1
ISO-8859-1-Windows-3.1-Latin-1 2001 csWindows31Latin1
ISO-8859-2-Windows-Latin-2 2002 csWindows31Latin2
ISO-8859-9-Windows-Latin-5 2003 csWindows31Latin5
Adobe-Standard-Encoding 2005 csAdobeStandardEncoding
Ventura-US 2006 csVenturaUS
Ventura-International 2007 csVenturaInternational
PC8-Danish-Norwegian 2012 csPC8DanishNorwegian
PC8-Turkish 2014 csPC8Turkish
IBM-Symbols 2015 csIBMSymbols
IBM-Thai 2016 csIBMThai
HP-Legal 2017 csHPLegal
HP-Pi-font 2018 csHPPiFont
HP-Math8 2019 csHPMath8
Adobe-Symbol-Encoding 2020 csHPPSMath
HP-DeskTop 2021 csHPDesktop
Ventura-Math 2022 csVenturaMath
Microsoft-Publishing 2023 csMicrosoftPublishing
Windows-31J 2024 csWindows31J
GB2312 2025 csGB2312 EUC-CN EUCCN CN-GB
Big5 2026 csBig5 BIG-FIVE BIG-5 CN-BIG5 BIG_FIVE x-x-big5
windows-1250 2250 CP1250 MS-EE
windows-1251 2251 CP1251 MS-CYRL
windows-1252 2252 CP1252 MS-ANSI
windows-1253 2253 CP1253 MS-GREEK
windows-1254 2254 CP1254 MS-TURK
windows-1255 2255
windows-1256 2256 CP1256 MS-ARAB
windows-1257 2257 CP1257 WINBALTRIM
windows-1258 2258
TIS-620 2259
HZ-GB-2312 2085
# Additional encodings not defined by IANA
# Arbitrary allocations
#CP737 3001
#CP853 3002
#CP856 3003
CP874 3004 WINDOWS-874
#CP922 3005
#CP1046 3006
#CP1124 3007
#CP1125 3008 WINDOWS-1125
#CP1129 3009
#CP1133 3010 IBM-CP1133
#CP1161 3011 IBM-1161 IBM1161 CSIBM1161
#CP1162 3012 IBM-1162 IBM1162 CSIBM1162
#CP1163 3013 IBM-1163 IBM1163 CSIBM1163
#GEORGIAN-ACADEMY 3014
#GEORGIAN-PS 3015
#KOI8-RU 3016
#KOI8-T 3017
#MACARABIC 3018 X-MAC-ARABIC MAC-ARABIC
#MACCROATIAN 3019 X-MAC-CROATIAN MAC-CROATIAN
#MACGREEK 3020 X-MAC-GREEK MAC-GREEK
#MACHEBREW 3021 X-MAC-HEBREW MAC-HEBREW
#MACICELAND 3022 X-MAC-ICELAND MAC-ICELAND
#MACROMANIA 3023 X-MAC-ROMANIA MAC-ROMANIA
#MACTHAI 3024 X-MAC-THAI MAC-THAI
#MACTURKISH 3025 X-MAC-TURKISH MAC-TURKISH
#MULELAO-1 3026
CP949 3027 WINDOWS-949
# From Unicode Lib
ISO-IR-182 4000
ISO-IR-197 4002
ISO-2022-JP-1 4008
MACCYRILLIC 4009 X-MAC-CYRILLIC MAC-CYRILLIC
MACUKRAINE 4010 X-MAC-UKRAINIAN MAC-UKRAINIAN
MACCENTRALEUROPE 4011 X-MAC-CENTRALEURROMAN MAC-CENTRALEURROMAN
JOHAB 4012
ISO-8859-11 4014 iso-ir-166 ISO_8859-11 ISO8859-11 8859_11
X-CURRENT 4999 X-SYSTEM
X-ACORN-LATIN1 5001
X-ACORN-FUZZY 5002

Binary file not shown.

Binary file not shown.

Binary file not shown.

View File

@ -0,0 +1,34 @@
AcornURI 1.04
-------------
Hi. This is a complete reimplementation of Acorn's URI module such that it
works on Iyonix. This allows simple URI / URL launching from applications.
Merge this !System with your own, then (re)launch your favourite browser to
ensure it's running.
This has a few advantages over the official offering: it's smaller,
compatible with more browsers and more tolerant of errors.
This is released under the terms of the LGPL, which is included in this
archive as the file Copying. Previous versions of this module were released
under the GPL, and are still available from sudden.recoil.org.
Source is available from the same place you downloaded this archive, ie
<http://sudden.recoil.org/others/acornuri/acornuri104src.zip>
Changelog
---------
v1.04 20-May-06 Relicensed under the LGPL (rather than GPL)
v1.03 11-May-04 Changed the order of things to try, so it now
always prefers browsers which are already loaded
v1.02 19-Feb-04 Fixed claiming of URIs where I'd misread the spec
Added automatic fall-back to the ANT protocol
Removed some service calls to improve reliability
--
Christian Ludlam
chris@recoil.org

View File

@ -0,0 +1,504 @@
GNU LESSER GENERAL PUBLIC LICENSE
Version 2.1, February 1999
Copyright (C) 1991, 1999 Free Software Foundation, Inc.
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
[This is the first released version of the Lesser GPL. It also counts
as the successor of the GNU Library Public License, version 2, hence
the version number 2.1.]
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.
This license, the Lesser General Public License, applies to some
specially designated software packages--typically libraries--of the
Free Software Foundation and other authors who decide to use it. You
can use it too, but we suggest you first think carefully about whether
this license or the ordinary General Public License is the better
strategy to use in any particular case, based on the explanations below.
When we speak of free software, we are referring to freedom of use,
not price. Our General Public Licenses are designed to make sure that
you have the freedom to distribute copies of free software (and charge
for this service if you wish); that you receive source code or can get
it if you want it; that you can change the software and use pieces of
it in new free programs; and that you are informed that you can do
these things.
To protect your rights, we need to make restrictions that forbid
distributors to deny you these rights or to ask you to surrender these
rights. These restrictions translate to certain responsibilities for
you if you distribute copies of the library or if you modify it.
For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that we gave
you. You must make sure that they, too, receive or can get the source
code. If you link other code with the library, you must provide
complete object files to the recipients, so that they can relink them
with the library after making changes to the library and recompiling
it. And you must show them these terms so they know their rights.
We protect your rights with a two-step method: (1) we copyright the
library, and (2) we offer you this license, which gives you legal
permission to copy, distribute and/or modify the library.
To protect each distributor, we want to make it very clear that
there is no warranty for the free library. Also, if the library is
modified by someone else and passed on, the recipients should know
that what they have is not the original version, so that the original
author's reputation will not be affected by problems that might be
introduced by others.
Finally, software patents pose a constant threat to the existence of
any free program. We wish to make sure that a company cannot
effectively restrict the users of a free program by obtaining a
restrictive license from a patent holder. Therefore, we insist that
any patent license obtained for a version of the library must be
consistent with the full freedom of use specified in this license.
Most GNU software, including some libraries, is covered by the
ordinary GNU General Public License. This license, the GNU Lesser
General Public License, applies to certain designated libraries, and
is quite different from the ordinary General Public License. We use
this license for certain libraries in order to permit linking those
libraries into non-free programs.
When a program is linked with a library, whether statically or using
a shared library, the combination of the two is legally speaking a
combined work, a derivative of the original library. The ordinary
General Public License therefore permits such linking only if the
entire combination fits its criteria of freedom. The Lesser General
Public License permits more lax criteria for linking other code with
the library.
We call this license the "Lesser" General Public License because it
does Less to protect the user's freedom than the ordinary General
Public License. It also provides other free software developers Less
of an advantage over competing non-free programs. These disadvantages
are the reason we use the ordinary General Public License for many
libraries. However, the Lesser license provides advantages in certain
special circumstances.
For example, on rare occasions, there may be a special need to
encourage the widest possible use of a certain library, so that it becomes
a de-facto standard. To achieve this, non-free programs must be
allowed to use the library. A more frequent case is that a free
library does the same job as widely used non-free libraries. In this
case, there is little to gain by limiting the free library to free
software only, so we use the Lesser General Public License.
In other cases, permission to use a particular library in non-free
programs enables a greater number of people to use a large body of
free software. For example, permission to use the GNU C Library in
non-free programs enables many more people to use the whole GNU
operating system, as well as its variant, the GNU/Linux operating
system.
Although the Lesser General Public License is Less protective of the
users' freedom, it does ensure that the user of a program that is
linked with the Library has the freedom and the wherewithal to run
that program using a modified version of the Library.
The precise terms and conditions for copying, distribution and
modification follow. Pay close attention to the difference between a
"work based on the library" and a "work that uses the library". The
former contains code derived from the library, whereas the latter must
be combined with the library in order to run.
GNU LESSER GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License Agreement applies to any software library or other
program which contains a notice placed by the copyright holder or
other authorized party saying it may be distributed under the terms of
this Lesser General Public License (also called "this License").
Each licensee is addressed as "you".
A "library" means a collection of software functions and/or data
prepared so as to be conveniently linked with application programs
(which use some of those functions and data) to form executables.
The "Library", below, refers to any such software library or work
which has been distributed under these terms. A "work based on the
Library" means either the Library or any derivative work under
copyright law: that is to say, a work containing the Library or a
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language. (Hereinafter, translation is
included without limitation in the term "modification".)
"Source code" for a work means the preferred form of the work for
making modifications to it. For a library, complete source code means
all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control compilation
and installation of the library.
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it). Whether that is true depends on what the Library does
and what the program that uses the Library does.
1. You may copy and distribute verbatim copies of the Library's
complete source code as you receive it, in any medium, provided that
you conspicuously and appropriately publish on each copy an
appropriate copyright notice and disclaimer of warranty; keep intact
all the notices that refer to this License and to the absence of any
warranty; and distribute a copy of this License along with the
Library.
You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for a
fee.
2. You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices
stating that you changed the files and the date of any change.
c) You must cause the whole of the work to be licensed at no
charge to all third parties under the terms of this License.
d) If a facility in the modified Library refers to a function or a
table of data to be supplied by an application program that uses
the facility, other than as an argument passed when the facility
is invoked, then you must make a good faith effort to ensure that,
in the event an application does not supply such function or
table, the facility still operates, and performs whatever part of
its purpose remains meaningful.
(For example, a function in a library to compute square roots has
a purpose that is entirely well-defined independent of the
application. Therefore, Subsection 2d requires that any
application-supplied function or table used by this function must
be optional: if the application does not supply it, the square
root function must still compute square roots.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Library,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Library, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Library.
In addition, mere aggregation of another work not based on the Library
with the Library (or with a work based on the Library) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may opt to apply the terms of the ordinary GNU General Public
License instead of this License to a given copy of the Library. To do
this, you must alter all the notices that refer to this License, so
that they refer to the ordinary GNU General Public License, version 2,
instead of to this License. (If a newer version than version 2 of the
ordinary GNU General Public License has appeared, then you can specify
that version instead if you wish.) Do not make any other change in
these notices.
Once this change is made in a given copy, it is irreversible for
that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy.
This option is useful when you wish to copy part of the code of
the Library into a program that is not a library.
4. You may copy and distribute the Library (or a portion or
derivative of it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you accompany
it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange.
If distribution of object code is made by offering access to copy
from a designated place, then offering equivalent access to copy the
source code from the same place satisfies the requirement to
distribute the source code, even though third parties are not
compelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library". Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.
However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library". The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.
When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library. The
threshold for this to be true is not precisely defined by law.
If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work. (Executables containing this object code plus portions of the
Library will still fall under Section 6.)
Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.
6. As an exception to the Sections above, you may also combine or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.
You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License. You must supply a copy of this License. If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License. Also, you must do one
of these things:
a) Accompany the work with the complete corresponding
machine-readable source code for the Library including whatever
changes were used in the work (which must be distributed under
Sections 1 and 2 above); and, if the work is an executable linked
with the Library, with the complete machine-readable "work that
uses the Library", as object code and/or source code, so that the
user can modify the Library and then relink to produce a modified
executable containing the modified Library. (It is understood
that the user who changes the contents of definitions files in the
Library will not necessarily be able to recompile the application
to use the modified definitions.)
b) Use a suitable shared library mechanism for linking with the
Library. A suitable mechanism is one that (1) uses at run time a
copy of the library already present on the user's computer system,
rather than copying library functions into the executable, and (2)
will operate properly with a modified version of the library, if
the user installs one, as long as the modified version is
interface-compatible with the version that the work was made with.
c) Accompany the work with a written offer, valid for at
least three years, to give the same user the materials
specified in Subsection 6a, above, for a charge no more
than the cost of performing this distribution.
d) If distribution of the work is made by offering access to copy
from a designated place, offer equivalent access to copy the above
specified materials from the same place.
e) Verify that the user has already received a copy of these
materials or that you have already sent this user a copy.
For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it. However, as a special exception,
the materials to be distributed need not include anything that is
normally distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies
the executable.
It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system. Such a contradiction means you cannot
use both them and the Library together in an executable that you
distribute.
7. You may place library facilities that are a work based on the
Library side-by-side in a single library together with other library
facilities not covered by this License, and distribute such a combined
library, provided that the separate distribution of the work based on
the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:
a) Accompany the combined library with a copy of the same work
based on the Library, uncombined with any other library
facilities. This must be distributed under the terms of the
Sections above.
b) Give prominent notice with the combined library of the fact
that part of it is a work based on the Library, and explaining
where to find the accompanying uncombined form of the same work.
8. You may not copy, modify, sublicense, link with, or distribute
the Library except as expressly provided under this License. Any
attempt otherwise to copy, modify, sublicense, link with, or
distribute the Library is void, and will automatically terminate your
rights under this License. However, parties who have received copies,
or rights, from you under this License will not have their licenses
terminated so long as such parties remain in full compliance.
9. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Library or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Library (or any work based on the
Library), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Library or works based on it.
10. Each time you redistribute the Library (or any work based on the
Library), the recipient automatically receives a license from the
original licensor to copy, distribute, link with or modify the Library
subject to these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties with
this License.
11. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Library at all. For example, if a patent
license would not permit royalty-free redistribution of the Library by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Library.
If any portion of this section is held invalid or unenforceable under any
particular circumstance, the balance of the section is intended to apply,
and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
12. If the distribution and/or use of the Library is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Library under this License may add
an explicit geographical distribution limitation excluding those countries,
so that distribution is permitted only in or among countries not thus
excluded. In such case, this License incorporates the limitation as if
written in the body of this License.
13. The Free Software Foundation may publish revised and/or new
versions of the Lesser General Public License from time to time.
Such new versions will be similar in spirit to the present version,
but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Library
specifies a version number of this License which applies to it and
"any later version", you have the option of following the terms and
conditions either of that version or of any later version published by
the Free Software Foundation. If the Library does not specify a
license version number, you may choose any version ever published by
the Free Software Foundation.
14. If you wish to incorporate parts of the Library into other free
programs whose distribution conditions are incompatible with these,
write to the author to ask for permission. For software which is
copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this. Our
decision will be guided by the two goals of preserving the free status
of all derivatives of our free software and of promoting the sharing
and reuse of software generally.
NO WARRANTY
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Libraries
If you develop a new library, and you want it to be of the greatest
possible use to the public, we recommend making it free software that
everyone can redistribute and change. You can do so by permitting
redistribution under these terms (or, alternatively, under the terms of the
ordinary General Public License).
To apply these terms, attach the following notices to the library. It is
safest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the library's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Also add information on how to contact you by electronic and paper mail.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the library, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the
library `Frob' (a library for tweaking knobs) written by James Random Hacker.
<signature of Ty Coon>, 1 April 1990
Ty Coon, President of Vice
That's all there is to it!

View File

@ -0,0 +1,45 @@
What is Iconv?
==============
Iconv is a module which provides character set conversion akin to that provided
by the C iconv() function.
Iconv Installation instructions
===============================
To install the Iconv module, simply use the System merge utility provided by
Configure to merge the !System directory provided with the one on your system.
Use the Boot merge facility in Configure to merge the provided !Boot directory
with the one on your system. If there is no !Boot merge facility provided on
your system, simply drag the !Boot directory over your existing boot structure.
Further documentation can be found in the "doc" directory.
Note for developers:
~~~~~~~~~~~~~~~~~~~~
The "stubs" directory contains source for a set of C stubs.
See the ReadMe file in that directory for further information.
Licence
=======
Iconv is Copyright © 2004-11 J-M Bell
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
* The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

View File

@ -0,0 +1,132 @@
Iconv Module API
================
If using C, then you really should be using the libiconv stubs provided
(or UnixLib, if appropriate). See the iconv.h header file for further
documentation of these calls.
Iconv_Open (&57540)
-------------------
Create a conversion descriptor
On Entry: r0 -> string containing name of destination encoding (eg "UTF-8")
r1 -> string containing name of source encoding (eg "CP1252")
On Exit: r0 = conversion descriptor
All others preserved
Either encoding name may have a number of parameters appended to them.
Parameters are separated by a pair of forward-slashes ("//").
Currently defined parameters are:
Parameter: Destination: Source:
TRANSLIT Transliterate unrepresentable None
output.
The conversion descriptor is an opaque value. The user should not,
therefore, assume anything about its meaning, nor modify it in any way.
Doing so is guaranteed to result in undefined behaviour.
Iconv_Iconv (&57541)
--------------------
This SWI is deprecated and Iconv_Convert should be used instead.
Iconv_Close (&57542)
--------------------
Destroy a conversion descriptor
On Entry: r0 = conversion descriptor to destroy
On Exit: r0 = 0
All others preserved
Iconv_Convert (&57543)
---------------------
Convert a byte sequence to another encoding
On Entry: r0 = conversion descriptor returned by Iconv_Open
r1 -> input buffer (or NULL to reset encoding context)
r2 = length of buffer pointed to by r1
r3 -> output buffer
r4 = length of buffer pointed to by r3
On Exit: r0 = number of non-reversible conversions performed (always 0)
r1 -> updated input buffer pointer (after last input read)
r2 = number of bytes remaining in input buffer
r3 -> updated output buffer pointer (i.e. end of output)
r4 = number of free bytes in the output buffer
All others preserved
Note that all strings should be NUL-terminated so, if calling from BASIC,
some terminating character munging may be needed.
Errors:
Should an error occur, the SWI will return with V set and r0 -> error buffer.
Note that only the error number will be filled in and may be one of:
ICONV_NOMEM (&81b900)
ICONV_INVAL (&81b901)
ICONV_2BIG (&81b902)
ICONV_ILSEQ (&81b903)
These map directly to the corresponding C errno values.
Iconv_CreateMenu (&57544)
-------------------------
Create a menu data structure containing all available encodings.
On Entry: r0 = flags. All bits reserved, must be 0
r1 -> buffer, or 0 to read required length
r2 = length of buffer in r1
r3 -> currently selected encoding name, or 0 if none selected
r4 -> buffer for indirected data, or 0 to read length
r5 = length of buffer in r4
On Exit: r2 = required size of buffer in r1 if r1 = 0 on entry,
or length of data placed in buffer
r5 = required size of buffer in r4 if r4 = 0 on entry,
or length of data placed in buffer
Menu titles are direct form text buffers. Menu entries are indirect text.
Entry text is stored in the buffer pointed to by R4 on entry to this call.
Iconv_DecodeMenu (&57545)
-------------------------
Decode a selection in a menu generated by Iconv_CreateMenu.
Places the corresponding encoding name in the result buffer.
On Entry: r0 = flags. All bits reserved, must be 0
r1 -> menu definition
r2 -> menu selections, as per Wimp_Poll
r3 -> buffer for result or 0 to read required length
r4 = buffer length
On Exit: r4 = required size of buffer if r3 = 0 on entry,
or length of data placed in buffer (0 if no selected
encoding)
The menu selections block pointed to by r2 on entry should be based at
the root of the encodings menu structure (i.e. index 0 in the block
should correspond to the selection in the main encoding menu).
This call will update the selection status of the menu(s) appropriately.
Example Code:
=============
Example code may be found in the IconvEg BASIC file.

View File

@ -0,0 +1,107 @@
Iconv Changelog
===============
0.01 10-Sep-2004
----------------
- Initial version - unreleased.
0.02 27-Sep-2004
----------------
- Use allocated SWI & error chunks.
- Fix issues in 8bit encoding handling.
- First public release.
0.03 22-Jan-2005
----------------
- Add Iconv_Convert SWI with improved interface.
- Deprecate Iconv_Iconv SWI.
- Add encoding name alias handling.
- Bundle !Unicode resource.
0.04 08-Apr-2005
----------------
- Improve parameter checking.
- Fix potential memory leaks.
- Add encoding menu creation and selection handling.
0.05 27-Jun-2005
----------------
- Improve encoding alias support, using external data file.
- Add StubsG build for A9home users.
0.06 05-Nov-2005
----------------
- Modified menu creation API to store indirected text in a
user-provided buffer. This change is backwards incompatible.
0.07 11-Feb-2006
----------------
- Corrected output values for E2BIG errors.
- Fixed input pointer update after successful conversion.
0.08 11-Mar-2007
----------------
- Tightened up parameter checking in various places.
- Improve aliases hash function.
- Make 8bit write function's return values match encoding_write
with encoding_WRITE_STRICT set.
- Fix bug in 8bit writing which resulted in the remaining buffer
size being reduced even if nothing was written.
- Improve support for endian-specific Unicode variants.
- Work around issue in UnicodeLib where remaining buffer size is
reduced if an attempt is made to write an unrepresentable character.
- Add rudimentary //TRANSLIT support - simply replaces with '?' for now.
- Make UnicodeLib handle raw ISO-8859-{1,2,9,10,15} and not attempt
ISO-6937-2-25 shift sequences.
- Remove StubsG build as A9home now has a C99 capable C library.
- Overhaul documentation.
0.09 20-Nov-2008
----------------
- Restructured source tree into cross-platform and RO-specific parts.
- New build system to go with this.
- Fixes for compiling with GCC4.
- Introduce *Iconv command which performs command line conversion.
- Fixes/improvements to the handlers for:
+ US-ASCII
+ UTF-8
+ ISO-8859-7
+ ISO-8859-8
+ ISO-8859-11
+ Windows-1256
+ MacRoman
+ JIS X 0208
+ JIS X 0212
+ KS X 1001
+ EUC-JP
+ Any ISO-2022 based charset that uses a 94x94 table in GR
+ Johab
+ ShiftJIS
- Add support for ISO-8859-16 (Latin 10)
- Significantly improve detection and reporting of error conditions
0.10 29-Nov-2008
----------------
- Fixes to the *Iconv command parameter parsing
- Ensure *Iconv outputs all converted data when the input is invalid
- Fix handling of illegal UTF-8 byte sequences
- Fix handling of incomplete multibyte input sequences.
0.11 04-Jan-2011
----------------
- Detect missing mapping file when using 8bit codecs. This prevents spurious
memory exhaustion errors.
- Toolchain used to build 0.10 turns out to have produced broken code.
- Minor additions to the charset alias mapping file.

View File

@ -0,0 +1,204 @@
Introduction:
=============
This file documents an approximate correlation between the data files
provided in the !Unicode distribution and the encoding headers in GNU
libiconv 1.9.1.
Those with '?' in the iconv column either are not represented in iconv
or I've missed the relevant header file ;)
A number of encodings are present in the iconv distribution but not
in !Unicode. These are documented at the end of this file.
Changelog:
==========
v 0.01 (09-Sep-2004)
~~~~~~~~~~~~~~~~~~~~
Initial Incarnation
v 0.02 (11-Sep-2004)
~~~~~~~~~~~~~~~~~~~~
Documented additional encodings supported by the Iconv module.
Corrected list of !Unicode deficiencies.
!Unicode->iconv:
================
Unicode: iconv: notes:
Acorn.Latin1 riscos1.h
Apple.CentEuro mac_centraleurope.h
Apple.Cyrillic mac_cyrillic.h
Apple.Roman mac_roman.h
Apple.Ukrainian mac_ukraine.h
BigFive big5.h
ISO2022.C0.40[ISO646] ?
ISO2022.C1.43[IS6429] ?
ISO2022.G94.40[646old] iso646_cn.h
ISO2022.G94.41[646-GB] ?
ISO2022.G94.42[646IRV] ?
ISO2022.G94.43[FinSwe] ?
ISO2022.G94.47[646-SE] ?
ISO2022.G94.48[646-SE] ?
ISO2022.G94.49[JS201K] jisx0201.h top of JIS range
ISO2022.G94.4A[JS201R] jisx0201.h iso646_jp.h bottom of JIS range
ISO2022.G94.4B[646-DE] ?
ISO2022.G94.4C[646-PT] ?
ISO2022.G94.54[GB1988] ?
ISO2022.G94.56[Teltxt] ?
ISO2022.G94.59[646-IT] ?
ISO2022.G94.5A[646-ES] ?
ISO2022.G94.60[646-NO] ?
ISO2022.G94.66[646-FR] ?
ISO2022.G94.69[646-HU] ?
ISO2022.G94.6B[Arabic] ?
ISO2022.G94.6C[IS6397] ?
ISO2022.G94.7A[SerbCr] ?
ISO2022.G94x94.40[JS6226] ?
ISO2022.G94x94.41[GB2312] gb2312.h
ISO2022.G94x94.42[JIS208] jis0x208.h
ISO2022.G94x94.43[KS1001] ksc5601.h
ISO2022.G94x94.44[JIS212] jis0x212.h
ISO2022.G94x94.47[CNS1] cns11643_1.h the tables differ
ISO2022.G94x94.48[CNS2] cns11643_2.h
ISO2022.G94x94.49[CNS3] cns11643_3.h
ISO2022.G94x94.4A[CNS4] cns11643_4.h
ISO2022.G94x94.4B[CNS5] cns11643_5.h
ISO2022.G94x94.4C[CNS6] cns11643_6.h
ISO2022.G94x94.4D[CNS7] cns11643_7.h
ISO2022.G96.41[Lat1] iso8859_1.h
ISO2022.G96.42[Lat2] iso8859_2.h
ISO2022.G96.43[Lat3] iso8859_3.h
ISO2022.G96.44[Lat4] iso8859_4.h
ISO2022.G96.46[Greek] ?
ISO2022.G96.47[Arabic] iso8859_6.h ISO-8859-6 ignored
ISO2022.G96.48[Hebrew] ?
ISO2022.G96.4C[Cyrill] ?
ISO2022.G96.4D[Lat5] iso8859_5.h
ISO2022.G96.50[LatSup] ?
ISO2022.G96.52[IS6397] ?
ISO2022.G96.54[Thai] tis620.h
ISO2022.G96.56[Lat6] iso8859_6.h
ISO2022.G96.58[L6Sami] ?
ISO2022.G96.59[Lat7] iso8859_7.h
ISO2022.G96.5C[Welsh] ?
ISO2022.G96.5D[Sami] ?
ISO2022.G96.5E[Hebrew] ?
ISO2022.G96.5F[Lat8] iso8859_8.h
ISO2022.G96.62[Lat9] iso8859_9.h
KOI8-R koi8_r.h
Microsoft.CP1250 cp1250.h
Microsoft.CP1251 cp1251.h
Microsoft.CP1252 cp1252.h
Microsoft.CP1254 cp1254.h
Microsoft.CP866 cp866.h
Microsoft.CP932 cp932.h cp932ext.h
iconv->!Unicode:
================
Iconv has the following encodings, which are not present in !Unicode.
Providing a suitable data file for !Unicode is trivial. Whether UnicodeLib
will then act upon the addition of these is unknown.
This list is ordered as per libiconv's NOTES file.
European & Semitic languages:
ISO-8859-16 (iso8859_16.h)
KOI8-{U,RU,T} (koi8_xx.h)
CP125{3,5,6,7} (cp125n.h)
CP850 (cp850.h)
CP862 (cp862.h)
Mac{Croatian,Romania,Greek,Turkish,Hebrew,Arabic} (mac_foo.h)
Japanese:
None afaikt.
Simplified Chinese:
GB18030 (gb18030.h, gb18030ext.h)
HZ-GB-2312 (hz.h)
Traditional Chinese:
CP950 (cp950.h)
BIG5-HKSCS (big5hkscs.h)
Korean:
CP949 (cp949.h)
Armenian:
ARMSCII-8 (armscii_8.h)
Georgian:
Georgian-Academy, Georgian-PS (georgian_academy.h, georgian_ps.h)
Thai:
CP874 (cp874.h)
MacThai (mac_thai.h)
Laotian:
MuleLao-1, CP1133 (mulelao.h, cp1133.h)
Vietnamese:
VISCII, TCVN (viscii.h, tcvn.h)
CP1258 (cp1258.h)
Unicode:
BE/LE variants of normal encodings. I assume UnicodeLib handles
these, but can't be sure.
C99 / JAVA - well, yes.
Iconv Module:
=============
The iconv module is effectively a thin veneer around UnicodeLib. However,
8bit encodings are implemented within the module rather than using the
support in UnicodeLib. The rationale for this is simply that, although
UnicodeLib will understand (and act upon - reportedly...) additions to
the ISO2022 Unicode resource, other encodings are ignored. As the vast
majority of outstanding encodings fall into this category, and the code
is fairly simple, it made sense to implement it within the module.
With use of the iconv module, the list of outstanding encodings is
reduced to:
CP1255 (requires state-based transcoding)
GB18030 (not 8bit - reportedly a requirement of PRC)
HZ-GB-2312 (not 8bit - supported by IE4)
CP950 (not 8bit - a (MS) variant of Big5)
BIG5-HKSCS (not 8bit - again, a Big5 variant)
CP949 (not 8bit)
ARMSCII-8 (easily implemented, if required)
VISCII (easily implemented, if required)
CP1258, TCVN (requires state-based transcoding)
Additionally, the rest of the CodePage encodings implemented in iconv
but not listed above (due to omissions from the iconv documentation)
are implemented by the iconv module.

View File

@ -0,0 +1,761 @@
UnixLib Copyright
-----------------
UnixLib is Copyright (c) 1995-1999 Simon Callan, Nick Burrett,
Nicholas Clark and Peter Burwood.
These contributors have expressed "no interest" in any further licensing or
copyright in regards to UnixLib.
Other sections are (c) 1999-2006 Nick Burrett, John Tytgat, Peter Naulls,
Peter Teichmann, Alex Waugh, Christian Ludlam, Theo Markettos, Graham Shaw,
James Bursa and John-Mark Bell.
In January 2005, permission was obtained from all relevant contributors
by Peter Naulls to license all past and present contributions to UnixLib
(where possible) under the revised BSD license. The license is included
in the next section and is applicable to all code in UnixLib that does not
have an explicit license in its source.
Prior to 4th January 2005 and after May 2001, UnixLib contained code licensed
under the GNU General Public License, and versions of UnixLib produced
between these dates are subject to the provisions of the GPL. We realised
that this might cause potential problems with the wider use of UnixLib in
RISC OS, and along with the desire to clarify the overall licensing status of
UnixLib, GPL code was removed from UnixLib and the above permission from all
copyright holders allowed UnixLib contributions to be relicensed as per the
revised BSD license. The GPL is therefore not included in this notice
as it is no longer relevant to UnixLib.
Practical notes on using UnixLib in your own programs:
This is a plain English version of guidelines for use of UnixLib in
your programs. It does not override any of the licenses included
below, but is intended to state instances when it may be used in
free and non-free software. Where there is contradiction or
ambiguity in this wording, please refer to the specifics of the licence
in question. These recommendations are based upon our understading
of the GPL/LGPL and BSD licenses and are subject to change should
our understanding of the topics improve.
- Because UnixLib contains code that is subject to the Lesser GNU
Public License, the LGPL is the overriding consideration when
linking UnixLib to programs (unless the program itself is GPL).
- You are free to use sections of UnixLib in your own programs
subject to the conditions of that code. If the entirety of
that code is under a BSD license, then you can generally use
that code as you see fit, and there is no further obligation
from you as long as the copyright notice remains. If you
use LGPL code in your program, then your program must also be
distributed under the LGPL (or GPL).
- If you use UnixLib in its intended original form - that is as a
supporting library for ported programs to RISC OS - then your program
is subject to the LGPL; or the GPL if the program is covered by that.
Note that you must make the source and any modifications available to for
both if requested. This is of course equally true if you write an original
GPL program using UnixLib. In most cases, no additional action is
required of you, especially since source is usually readibly available.
- If you use UnixLib for a non-free program - whether that's commercial or
otherwise, then you should carefully read section 6 of the LGPL. This
applies, because at the present time, there is no practical method of
dynamic linking on RISC OS. At such time that UnixLib is available as a
shared library, then programs dynamically linking to it will no longer be
subject to the LPGL as applied to UnixLib.
- Section 6 means that in practice, you must supply, or offer to
supply either source or object code for your program.
This is mainly to allow rebuilding of the executable program
with later or modified versions of UnixLib. You must of course
supply (or better, contribute to the GCCSDK project) any
modifications you make to UnixLib upon request.
Recommended reading:
Frequently Asked Questions about the GNU GPL
http://www.fsf.org/licenses/gpl-faq.html (has some sections on LGPL)
About the justifications for using LGPL
http://www.fsf.org/licenses/why-not-lgpl.html
===========================================================================
Copyright (c) 1995-2005 UnixLib Developers
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. The name of the author may not be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
===========================================================================
Portions of UnixLib are copyright The Regents of the University of
California.
Portions of this library are copyright Sun Microsystems, Inc. The
Portions of this library are derived from the GNU C Library and fall under
the GNU Library General Public License.
Portions of this library are copyright Henry Spencer.
Portions of this library are copyright The Regents of the University of
California, Sun Microsystems, Inc., Scriptics Corporation, ActiveState
Corporation and other parties.
Portions of this library are copyright PostgreSQL Global Development Group.
The licenses for the above are duplicated below.
===========================================================================
Copyright (c) The Regents of the University of California.
All rights reserved.
This code is derived from software contributed to Berkeley by
Chris Torek.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software
must display the following acknowledgement:
This product includes software developed by the University of
California, Berkeley and its contributors.
4. Neither the name of the University nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
===========================================================================
Copyright (C) 1993 by Sun Microsystems, Inc. All rights reserved.
Developed at SunPro, a Sun Microsystems, Inc. business.
Permission to use, copy, modify, and distribute this
software is freely granted, provided that this notice
is preserved.
===========================================================================
GNU LIBRARY GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1991 Free Software Foundation, Inc.
59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
[This is the first released version of the library GPL. It is
numbered 2 because it goes with version 2 of the ordinary GPL.]
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.
This license, the Library General Public License, applies to some
specially designated Free Software Foundation software, and to any
other libraries whose authors decide to use it. You can use it for
your libraries, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if
you distribute copies of the library, or if you modify it.
For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that we gave
you. You must make sure that they, too, receive or can get the source
code. If you link a program with the library, you must provide
complete object files to the recipients so that they can relink them
with the library, after making changes to the library and recompiling
it. And you must show them these terms so they know their rights.
Our method of protecting your rights has two steps: (1) copyright
the library, and (2) offer you this license which gives you legal
permission to copy, distribute and/or modify the library.
Also, for each distributor's protection, we want to make certain
that everyone understands that there is no warranty for this free
library. If the library is modified by someone else and passed on, we
want its recipients to know that what they have is not the original
version, so that any problems introduced by others will not reflect on
the original authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that companies distributing free
software will individually obtain patent licenses, thus in effect
transforming the program into proprietary software. To prevent this,
we have made it clear that any patent must be licensed for everyone's
free use or not licensed at all.
Most GNU software, including some libraries, is covered by the ordinary
GNU General Public License, which was designed for utility programs. This
license, the GNU Library General Public License, applies to certain
designated libraries. This license is quite different from the ordinary
one; be sure to read it in full, and don't assume that anything in it is
the same as in the ordinary license.
The reason we have a separate public license for some libraries is that
they blur the distinction we usually make between modifying or adding to a
program and simply using it. Linking a program with a library, without
changing the library, is in some sense simply using the library, and is
analogous to running a utility program or application program. However, in
a textual and legal sense, the linked executable is a combined work, a
derivative of the original library, and the ordinary General Public License
treats it as such.
Because of this blurred distinction, using the ordinary General
Public License for libraries did not effectively promote software
sharing, because most developers did not use the libraries. We
concluded that weaker conditions might promote sharing better.
However, unrestricted linking of non-free programs would deprive the
users of those programs of all benefit from the free status of the
libraries themselves. This Library General Public License is intended to
permit developers of non-free programs to use free libraries, while
preserving your freedom as a user of such programs to change the free
libraries that are incorporated in them. (We have not seen how to achieve
this as regards changes in header files, but we have achieved it as regards
changes in the actual functions of the Library.) The hope is that this
will lead to faster development of free libraries.
The precise terms and conditions for copying, distribution and
modification follow. Pay close attention to the difference between a
"work based on the library" and a "work that uses the library". The
former contains code derived from the library, while the latter only
works together with the library.
Note that it is possible for a library to be covered by the ordinary
General Public License rather than by this special one.
GNU LIBRARY GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License Agreement applies to any software library which
contains a notice placed by the copyright holder or other authorized
party saying it may be distributed under the terms of this Library
General Public License (also called "this License"). Each licensee is
addressed as "you".
A "library" means a collection of software functions and/or data
prepared so as to be conveniently linked with application programs
(which use some of those functions and data) to form executables.
The "Library", below, refers to any such software library or work
which has been distributed under these terms. A "work based on the
Library" means either the Library or any derivative work under
copyright law: that is to say, a work containing the Library or a
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language. (Hereinafter, translation is
included without limitation in the term "modification".)
"Source code" for a work means the preferred form of the work for
making modifications to it. For a library, complete source code means
all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control compilation
and installation of the library.
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it). Whether that is true depends on what the Library does
and what the program that uses the Library does.
1. You may copy and distribute verbatim copies of the Library's
complete source code as you receive it, in any medium, provided that
you conspicuously and appropriately publish on each copy an
appropriate copyright notice and disclaimer of warranty; keep intact
all the notices that refer to this License and to the absence of any
warranty; and distribute a copy of this License along with the
Library.
You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for a
fee.
2. You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices
stating that you changed the files and the date of any change.
c) You must cause the whole of the work to be licensed at no
charge to all third parties under the terms of this License.
d) If a facility in the modified Library refers to a function or a
table of data to be supplied by an application program that uses
the facility, other than as an argument passed when the facility
is invoked, then you must make a good faith effort to ensure that,
in the event an application does not supply such function or
table, the facility still operates, and performs whatever part of
its purpose remains meaningful.
(For example, a function in a library to compute square roots has
a purpose that is entirely well-defined independent of the
application. Therefore, Subsection 2d requires that any
application-supplied function or table used by this function must
be optional: if the application does not supply it, the square
root function must still compute square roots.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Library,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Library, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Library.
In addition, mere aggregation of another work not based on the Library
with the Library (or with a work based on the Library) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may opt to apply the terms of the ordinary GNU General Public
License instead of this License to a given copy of the Library. To do
this, you must alter all the notices that refer to this License, so
that they refer to the ordinary GNU General Public License, version 2,
instead of to this License. (If a newer version than version 2 of the
ordinary GNU General Public License has appeared, then you can specify
that version instead if you wish.) Do not make any other change in
these notices.
Once this change is made in a given copy, it is irreversible for
that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy.
This option is useful when you wish to copy part of the code of
the Library into a program that is not a library.
4. You may copy and distribute the Library (or a portion or
derivative of it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you accompany
it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange.
If distribution of object code is made by offering access to copy
from a designated place, then offering equivalent access to copy the
source code from the same place satisfies the requirement to
distribute the source code, even though third parties are not
compelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library". Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.
However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library". The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.
When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library. The
threshold for this to be true is not precisely defined by law.
If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work. (Executables containing this object code plus portions of the
Library will still fall under Section 6.)
Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.
6. As an exception to the Sections above, you may also compile or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.
You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License. You must supply a copy of this License. If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License. Also, you must do one
of these things:
a) Accompany the work with the complete corresponding
machine-readable source code for the Library including whatever
changes were used in the work (which must be distributed under
Sections 1 and 2 above); and, if the work is an executable linked
with the Library, with the complete machine-readable "work that
uses the Library", as object code and/or source code, so that the
user can modify the Library and then relink to produce a modified
executable containing the modified Library. (It is understood
that the user who changes the contents of definitions files in the
Library will not necessarily be able to recompile the application
to use the modified definitions.)
b) Accompany the work with a written offer, valid for at
least three years, to give the same user the materials
specified in Subsection 6a, above, for a charge no more
than the cost of performing this distribution.
c) If distribution of the work is made by offering access to copy
from a designated place, offer equivalent access to copy the above
specified materials from the same place.
d) Verify that the user has already received a copy of these
materials or that you have already sent this user a copy.
For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it. However, as a special exception,
the source code distributed need not include anything that is normally
distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies
the executable.
It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system. Such a contradiction means you cannot
use both them and the Library together in an executable that you
distribute.
7. You may place library facilities that are a work based on the
Library side-by-side in a single library together with other library
facilities not covered by this License, and distribute such a combined
library, provided that the separate distribution of the work based on
the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:
a) Accompany the combined library with a copy of the same work
based on the Library, uncombined with any other library
facilities. This must be distributed under the terms of the
Sections above.
b) Give prominent notice with the combined library of the fact
that part of it is a work based on the Library, and explaining
where to find the accompanying uncombined form of the same work.
8. You may not copy, modify, sublicense, link with, or distribute
the Library except as expressly provided under this License. Any
attempt otherwise to copy, modify, sublicense, link with, or
distribute the Library is void, and will automatically terminate your
rights under this License. However, parties who have received copies,
or rights, from you under this License will not have their licenses
terminated so long as such parties remain in full compliance.
9. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Library or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Library (or any work based on the
Library), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Library or works based on it.
10. Each time you redistribute the Library (or any work based on the
Library), the recipient automatically receives a license from the
original licensor to copy, distribute, link with or modify the Library
subject to these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
11. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Library at all. For example, if a patent
license would not permit royalty-free redistribution of the Library by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Library.
If any portion of this section is held invalid or unenforceable under any
particular circumstance, the balance of the section is intended to apply,
and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
12. If the distribution and/or use of the Library is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Library under this License may add
an explicit geographical distribution limitation excluding those countries,
so that distribution is permitted only in or among countries not thus
excluded. In such case, this License incorporates the limitation as if
written in the body of this License.
13. The Free Software Foundation may publish revised and/or new
versions of the Library General Public License from time to time.
Such new versions will be similar in spirit to the present version,
but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Library
specifies a version number of this License which applies to it and
"any later version", you have the option of following the terms and
conditions either of that version or of any later version published by
the Free Software Foundation. If the Library does not specify a
license version number, you may choose any version ever published by
the Free Software Foundation.
14. If you wish to incorporate parts of the Library into other free
programs whose distribution conditions are incompatible with these,
write to the author to ask for permission. For software which is
copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this. Our
decision will be guided by the two goals of preserving the free status
of all derivatives of our free software and of promoting the sharing
and reuse of software generally.
NO WARRANTY
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
END OF TERMS AND CONDITIONS
Appendix: How to Apply These Terms to Your New Libraries
If you develop a new library, and you want it to be of the greatest
possible use to the public, we recommend making it free software that
everyone can redistribute and change. You can do so by permitting
redistribution under these terms (or, alternatively, under the terms of the
ordinary General Public License).
To apply these terms, attach the following notices to the library. It is
safest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the library's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Library General Public
License as published by the Free Software Foundation; either
version 2 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Library General Public License for more details.
You should have received a copy of the GNU Library General Public
License along with this library; if not, write to the Free
Software Foundation, Inc., 59 Temple Place - Suite 330, Boston,
MA 02111-1307, USA
Also add information on how to contact you by electronic and paper mail.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the library, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the
library `Frob' (a library for tweaking knobs) written by James Random Hacker.
<signature of Ty Coon>, 1 April 1990
Ty Coon, President of Vice
That's all there is to it!
===========================================================================
Copyright (c) 1998, 1999 Henry Spencer. All rights reserved.
Development of this software was funded, in part, by Cray Research Inc.,
UUNET Communications Services Inc., Sun Microsystems Inc., and Scriptics
Corporation, none of whom are responsible for the results. The author
thanks all of them.
Redistribution and use in source and binary forms -- with or without
modification -- are permitted for any purpose, provided that
redistributions in source form retain this entire copyright notice and
indicate the origin and nature of any modifications.
I'd appreciate being given credit for this package in the documentation
of software which uses it, but that is not a requirement.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
HENRY SPENCER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
===========================================================================
This software is copyrighted by the Regents of the University of
California, Sun Microsystems, Inc., Scriptics Corporation, ActiveState
Corporation and other parties. The following terms apply to all files
associated with the software unless explicitly disclaimed in
individual files.
The authors hereby grant permission to use, copy, modify, distribute,
and license this software and its documentation for any purpose, provided
that existing copyright notices are retained in all copies and that this
notice is included verbatim in any distributions. No written agreement,
license, or royalty fee is required for any of the authorized uses.
Modifications to this software may be copyrighted by their authors
and need not follow the licensing terms described here, provided that
the new terms are clearly indicated on the first page of each file where
they apply.
IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
MODIFICATIONS.
GOVERNMENT USE: If you are acquiring this software on behalf of the
U.S. government, the Government shall have only "Restricted Rights"
in the software and related documentation as defined in the Federal
Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
are acquiring the software on behalf of the Department of Defense, the
software shall be classified as "Commercial Computer Software" and the
Government shall have only "Restricted Rights" as defined in Clause
252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the
authors grant the U.S. Government and others acting in its behalf
permission to use and distribute the software in accordance with the
terms specified in this license.
===========================================================================
PostgreSQL Database Management System
(formerly known as Postgres, then as Postgres95)
Portions Copyright (c) 1996-2005, PostgreSQL Global Development Group
Portions Copyright (c) 1994, The Regents of the University of California
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose, without fee, and without a written agreement
is hereby granted, provided that the above copyright notice and this
paragraph and the following two paragraphs appear in all copies.
IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR
DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING
LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS
DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS
ON AN "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO
PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.

304
riscos/distribution/3rdParty/Tinct/!Help vendored Normal file
View File

@ -0,0 +1,304 @@
Tinct
=====
This module provides the necessary functionality to display alpha-blended
sprites both scaled and otherwise. It also provides functions for dithering,
error diffusion and performing bi-linear filtering to improve their appearance.
Technical information
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
To ensure future compatibility, this module does not patch the OS in any way
and works in a totally legal way. It also does not write to itself in any
way, so is suitable for running from ROM.
Redirection to sprites is supported, although due to the overheads involved
with caching the colour translation tables it is not recommended that this is
done frequently. There are some exceptions to this, however, as redirecting to
a 16bpp or 32bpp mode sprite does not require any translation tables, and
redirecting to a sprite that has the same mode and palette as the previous
destination that Tinct was used for causes a minimum overhead as the
translation tables are checked and cached values are used if possible.
Format of a sprite with 8-bit alpha channel
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
The sprite format used by Tinct differs from those used by RISC OS Select,
and whilst facilities are supplied to convert sprites into the required format,
no facilities are provided to manipulate them.
All sprites used by Tinct must be 32bpp, and cannot have a standard RISC OS
mask specified. The basic format of the sprite is shown below, with the
restrictions to the standard sprite format marked with an asterisk (*):
[+0] Offset to next sprite
[+4] Sprite name, up to 12 characters with trailing zeroes
[+16] Width in words - 1
[+20] Height in scan lines - 1
[+24] First bit used
[+28] Last bit used
[+32] Offset to sprite image
[+36] * Offset to sprite image (no mask allowed)
[+40] * Sprite type (must be 0x301680B5)
Whereas for normal sprites the sprite image would be a series of colour words
of the format RrGgBb00, alpha-blended sprites use the empty byte to specify
the alpha value, ie RrGgBbAa.
The alpha values represent the blending level on a linear scale where 0x00
represents that the source pixel is totally transparent and 0xff that it is
totally opaque. It should be noted that as a standard 32bpp sprite (eg as
created with !Paint) will have the alpha channel set to 0x00 by default no
output will be visible when plotting as an alpha-blended sprite.
Error handling
¨¨¨¨¨¨¨¨¨¨¨¨¨¨
If an incorrect sprite is attempted to be used, Tinct currently always returns
error number 0x700 (SBadSpriteFile) rather than the specific cause of the
problem (eg. BadDPI, BadMSFlags or BadPixelDepth) as OS_SpriteOp would do.
There are several technical reasons for this behaviour, and future versions of
Tinct may return more descriptive errors depending on the cause.
SWIs provided
¯¯¯¯¯¯¯¯¯¯¯¯¯
Tinct provides four SWIs to plot sprites and one to convert sprites to their
32bpp equivalent. All values supplied to Tinct must be in OS units, and the
current OS clipping rectangle is used.
The sprite pointers provided are equivalent to calling OS_SpriteOp with
bit 9 of the reason code set. To plot a sprite by name, the sprite should
first be found by using OS_SpriteOp with reason code 0x18 and using the
returned sprite address.
Tinct_PlotAlpha (0x57240)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Plots an alpha-blended sprite at the specified coordinates.
-> R2 Sprite pointer
R3 X coordinate
R4 Y coordinate
R7 Flag word
Tinct_PlotScaledAlpha (0x57241)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Plots a scaled alpha-blended sprite at the specified coordinates.
-> R2 Sprite pointer
R3 X coordinate
R4 Y coordinate
R5 Scaled sprite width
R6 Scaled sprite height
R7 Flag word
Tinct_Plot (0x57242)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Plots a sprite at the specified coordinates with a constant 0xff value for
the alpha channel, ie without a mask.
-> R2 Sprite pointer
R3 X coordinate
R4 Y coordinate
R7 Flag word
Tinct_PlotScaled (0x57243)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Plots a scaled sprite at the specified coordinates with a constant 0xff value
for the alpha channel, ie without a mask.
-> R2 Sprite pointer
R3 X coordinate
R4 Y coordinate
R5 Scaled sprite width
R6 Scaled sprite height
R7 Flag word
Tinct_ConvertSprite (0x57244)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Converts a paletted sprite into its 32bpp equivalent. Sufficient memory must
have previously been allocated for the sprite (44 + width * height * 4).
As sprites with 16bpp or 32bpp do not have palettes, conversion cannot be
performed on these variants. All sprites must be supplied with a full palette,
eg 8bpp must have 256 palette entries.
-> R2 Source sprite pointer
R3 Destination sprite pointer
Tinct_AvailableFeatures (0x57245)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Returns the features available to the caller by specifying bits in the flag
word. The features available are unique for each mode, although the current
version of Tinct supports the same subset of features for all modes.
-> R0 Feature to test for, or 0 for all features
<- R0 Features available
Tinct_Compress (0x57246)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Compresses an image using a fast algorithm. Sufficient memory must have been
previously allocated for the maximum possible compressed size. This value is
equal to 28 + (width * height * 4) * 33 / 32.
-> R0 Source sprite pointer
R2 Output data buffer
R3 Output bytes available
R7 Flag word
<- R0 Size of compressed data
Tinct_Decompress (0x57247)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Decompresses an image previously compressed. Sufficient memory must have been
previously allocated for the decompressed data (44 + width * height * 4) where
width and height are available at +0 and +4 of the compressed data respectively.
-> R0 Input data buffer
R2 Output data buffer
R7 Flag word (currently 0)
<- R0 Size of decompressed data
Flag word (plotting)
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
All the SWIs provided by Tinct for plotting use a common flag word to
describe the manner in which the plot is performed. Each bit controls a
particular characteristic of the plotting:
0 Forcibly read the screen base (only use if hardware scrolling)
1 Use bi-linear filtering when scaling sprites
2 Dither colours in 16bpp and below
3 Perform error diffusion if bit 2 clear, invert dither pattern if set
4 Horizontally fill the current graphics window with the sprite
5 Vertically fill the current graphics window with the sprite
6 Forcibly read the palette (only use if changing palette outside of
the WIMP)
7 Use OS_SpriteOp to perform final plotting (see note)
8+ Reserved (must be 0) if bit 7 is clear, background colour to
blend the alpha channel to otherwise
If a bit is set in the flag word that cannot be honoured by the current
version of Tinct then it is ignored. Tinct_AvailableFeatures can be used
to test in advance what flags will be honoured.
Bi-linear filtering
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Although bi-linear filtering is only relevant during scaled plotting, this
situation occurs when the EigFactors of the mode are not equal. As such, an
application should always set their preferred flags to ensure consistency. The
case of XEig * 2 = YEig (rectangular pixel modes) for even height sprites is a
special case and has optimised code implemented.
There is an upper limit to the size of sprite that can be bi-linear filtered.
The checks that are currently made are:
scaled_width / sprite_width < 256
scaled_height / sprite_height < 256
scaled_width * max(sprite_height, scaled_height) < 32,768
It should be noted that as bi-linear filtering is performed as a pre-filter,
it carries a sizable overhead. However, as all scaling calculations are
performed during this filter, tiled plotting (bits 4 and 5) are affected by
a smaller margin (in certain cases a speed gain can be achieved).
As bi-linear filtering is performed using a pre-filter, it can be used in
association with OS_SpriteOp rendering.
Error diffusion and dithering
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
If both error diffusion and dithering are enabled then the image is plotted
using only dithering, but with the dither pattern inverted. This enables an
application to provide the user with what appears to be a higher quality image
by redrawing every frame with the flag toggled.
There is a significant speed difference between dithering and error diffusion,
and Tinct does not support error diffusion in all colour depths. If error
diffusion is requested, but cannot be performed by Tinct then dithering with
an inverted pattern is used (as if bits 2 and 3 were set).
There is an upper limit to the size of sprite that Tinct can perform error
diffusion on. This is currently set to a display width of 2047 pixels wide with
an unlimited height. Any attempt to use a higher resolution will result in
dithered rendering with an inverted pattern (ie bits 2 and 3 set).
As error diffusion and dithering are implemented during the plot cycle, it is
not possible to use them in association with OS_SpriteOp rendering. However,
the bits should be set as future versions of Tinct may respect them for users
of RISC OS 3.1 where true colour sprites are not supported.
Sprite filling
¨¨¨¨¨¨¨¨¨¨¨¨¨¨
If filling is specified, then the supplied co-ordinate is the offset of the
pattern relative to (0, 0) used for the fill. For example, a 64x64 sprite that
is plotted with bits 4 and 5 set and a position of (32, 16) would fill the
current graphics window with multiple copies of the image stating with the
first image plotted at (-32, -48).
The caller should not concern itself with the size of the image being tiled
as small images are internally optimised where possible to maximise the
plotting speed.
Rendering using OS_SpriteOp
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
It can be useful to use Tinct to perform the rendering to using OS_SpriteOp.
There are two general situations where this may be useful:
1) To output to a printer driver
2) To allow hardware acceleraton (such as a ViewFinder card)
By using Tinct rather than a direct OS_SpriteOp call, it allows the caller to
retain certain features Tinct provides (such as sprite filling and a limited
version of the standard alpha blending) and allows the caller to have a common
plotting interface.
When using this feature for alpha-blended sprites, the background colour
specified in the top 24-bits of the flag word is used for blending with any
pixels that are not transparent. This requires that Tinct requires a second
copy of the sprite in memory to modify which may present a significant overhead
in some situations. Plotting opaquely does not have any such overheads.
Using OS_SpriteOp rendering does not currently work on RISC OS 3.1 or earlier
due to the lack of support for true colour sprites. Future versions of Tinct
may remove this restriction.
Flag word (compression)
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
The flag word used by Tinct_Compress can be used to improve the compression
ratio by performing pre-filtering on the data. The flags below relate only to
compression and should not be passed to Tinct_Decompress.
0 Image is opaque, remove the alpha channel prior to compression
All unspecified bits are reserved for future expansion and as such should be
set to 0.
Compressed data format
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Certain aspects of the compressed data format are guaranteed to remain constant,
so may be used by applications.
+0 Sprite width
+4 Sprite height
+8 Sprite name (12 chars)
+20 Compression flags
+24 Number of bytes of data following
The method of compression is not guaranteed to remain constant over future
revisions of Tinct, but subsequent versions will decompress data compressed
with previous versions.
Contact details
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
If you would like to report a problem relating to Tinct, provide feedback, or
request a licence for a commercial product, please use the details below:
Address: 5 Queens Close, East Markham, Newark, Nottinghamshire, NG22 0QY. UK
E-mail: info@tinct.net
Website: www.tinct.net
Copyright and licence details
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Tinct is © copyright Richard Wilson, 2004.
Distribution and usage
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Unrestricted use of Tinct is hereby granted for any non-commercial product. Any
use as part of a commercial product requires written consent from the author.
No charge may be made relating to the distribution of this software, and this
copyright information should be included in all copies of the software.
Modified versions of this program may not be distributed without the authors
consent, nor may modified versions of the source code or relating files.