1New features with AN-2018-05-02: 2 3This is the first localization step for the schily source consolidation. Many 4programs now (hopefully) call gettext() for all strings that need localization. 5 6- The next step will include dgettext() calls for the libraries and the 7 missing programs 8 9- The following step will include the extracted strings 10 11- The last step will include German translations and install support 12 for the resulting binary message object files. 13 14----------> Please test and report compilation problems! <--------- 15 16***** NOTE: As mentioned since 2004, frontends to the tools should ***** 17***** call all programs in the "C" locale ***** 18***** by e.g. calling: LC_ALL=C cdrecord .... ***** 19***** unless these frontends support localized strings ***** 20***** used by the cdrtools with NLS support. ***** 21 22 *** WARNING *** 23 *** Need new smake *** 24 25 *** Due to the fact that schily-tools 2014-04-03 introduced to use new macro 26 *** expansions and a related bug fix in smake, you need a new smake 27 *** to compile this source. If your smake is too old and aborts, ensure this 28 *** by calling: 29 30 cd ./psmake 31 ./MAKE-all 32 cd .. 33 psmake/smake 34 psmake/smake install 35 36 *** Due to the fact that schily-tools 2014-01-26 introduced 37 *** optimizations for the Schily version of SunPro Make, you 38 *** need at least the dmake version from 2018/01/11 with support 39 *** for the "export" directive to compile with this makefile system. 40 41 42 WARNING: the new version of the isoinfo program makes use of the 43 *at() series of functions that have been introduced by Sun 44 in August 2001 and added to POSIX.1-2008. For older platforms, 45 libschily now includes emulations for these functions but 46 these emulations have not yet been tested thoroughly. 47 Please report problems! 48 49 The new smake version mentioned above is smake-1.2.4 50 51- libschily::getargs.c: Fixed a 38 year old bug bug with option parsing 52 that did cause a core dump in case that something like "-l,all" - an 53 option name that contains a comma - was used. This bug was detected 54 with "bsh" but it has a potential to affect all tools that use 55 getargs() to parse options - so all schilytools that are not derived 56 from UNIX soures are affected. 57 58 Thanks to Heiko Ei�feldt for reporting 59 60- libxtermcap: Fixed a bug that could cause tdecode() to run past the 61 end of a non-conforming string that could e.g. appear when tdecode() 62 is called from the "map" builtin in bsh or bosh (Bourne Shell). 63 64 Thanks to Heiko Ei�feldt for reporting 65 66- bsh: wordeql() could access a string beyond the end in case that the 67 word in that string was shorter than the reference. 68 69 Thanks to Heiko Ei�feldt for reporting 70 71- bsh: "$@$@" could cause an illegal call to iswhite(-2) as the check for 72 "$@" with ac <= 1 that needs to remove the argument completely was 73 imperfect. 74 75 Thanks to Heiko Ei�feldt for reporting 76 77- bsh & libshedit: '"' and '\'' are now in the list of characters that 78 need quoting during a TAB filename expansion. This affects bsh and the 79 Bourne Shell. 80 81- Bourne Shell: added an #ifdef EXPAND_DEBUG to expand.c to help debugging 82 hard to debug pattern matching cases. 83 84- Bourne Shell: When in strict POSIX mode (set -o posix), "case" pattern 85 matching no longer implements a fallback to a vanilla string compare in 86 case that gmatch() fails. This differs from what Bourne Shell and ksh 87 implement, but it is aligned with opinion of the majority of the people 88 in the POSIX commitee. 89 90- Bourne Shell: try to avoid an ugly line break in the man page. 91 92- Bourne Shell: the conformance tests have been modified to deal with 93 spaces in PATH - needed on Cygwin. 94 95 Thanks to Heiko Ei�feldt for reporting 96 97- star: star -diff is now able to compare nanoseconds in timestamps. 98 This requires a tar archive with full POSIX.1-2001 extended tar 99 header extensions. If the archive does not include sub-second 100 resolution, star -diff implements a silent fallback to what previously 101 has been done: just compare the seconds. 102 103- smake: man page now uses a 4-digit year. 104 105- SCCS: The logname() function in libcomobj now substitutes " " by 106 "_". This is needed as Cygwin permits to have spaces in the user name 107 but this would be in conflict with our history file format that uses 108 " " as a field separator. 109 110 Thanks to Heiko Ei�feldt for reporting 111 112- SCCS: The username arguments for "admin" and "sccs" are now modified 113 in case that they contain space characters (" "). This is needed to 114 match the modifications for the history file format - see above. 115 116- SCCS: The sccsfile(4) man page has been enhanced to mention the fact 117 that spaces in usernames are impossible in the history file. 118 119- SCCS: The conformance tests have been rewritten to deal with user names 120 and working directories that include spaces. 121 122- SCCS: Some sources have been converted to better follow the Cstyle 123 conventions. 124 125 126- Bourne Shell Missing features for POSIX compliance: 127 128 - Support for $'...' quoting (this is not needed for the current 129 version of POSIX but for the next POSIX 130 version that will be named SUSv8). 131 The development of SUSv8 will start in 132 late 2016. 133 134 We are now expecting the Bourne Shell to be fully POSIX compliant. 135 136- Bourne Shell further TODO list: 137 138 - Finish loadable builtin support. 139 140 - POSIX does not allow us to implement ". -h", so we will 141 add a "source" builtin to be able to implement "source -h" 142 143- The following builtins (that are available in bsh) are still missing in 144 the Bourne Shell: 145 146 err echo with output going to stderr 147 glob echo with '\0' instead of ' ' between args 148 env a builtin version of /usr/bin/env 149 150 The following bsh intrinsics are still missing in the Bourne Shell: 151 152 - the restricted bsh has restriction features that 153 are missing in the Bourne shell. 154 155 - source -h read file into history but do not execute 156 157 and probably more features not yet identified to be bsh unique. 158 159 160 161Author: 162 163Joerg Schilling 164D-13353 Berlin 165Germany 166 167Email: joerg@schily.net, js@cs.tu-berlin.de 168 joerg.schilling@fokus.fraunhofer.de 169 170Please mail bugs and suggestions to me. 171