In Southern Equinoctial and Lent
At the end of this Metric year TRINPsite comprises 922 public files, of
which approximately 720 different or 'unique' ones: 122 *.htm
(not *Txt.htm), 6 *.html, 447 *.HTM, 1 *Txt.htm, 6 style sheets,
9 JavaScript files, 85 pictures, 4 ikons and 40 sound files.
The present text file (AddNRev/65ASWW.HTM) was added in Southern
Equinoctial Month.
In Southern Mid-Lent a new sound file was created: the file Sound/ZzY/Shige/LiuLiu1R.mp3
(260 kB, 16 secs).
It offers the lyrics of the children's song
Liu Cheng Liu in
Zhezhong Yuyan ('Chinese').
That is, the song is not sung but read by means of a text-to-speech
synthesizer.
The sound file Sound/ZzY/Shige/Anan2R.mp3 is not
new, but replaces Anan1R.mp3 because of changes in the text.
It uses the same NeoSpeech synthesizer, but now with a male instead of
female voice.
Until the last month of this year the text at the end of the Book of
Instruments, which is also called
"End of the Book of Instruments" was part
of the same file as the last section of the Book of Instruments.
It has now been put in a separate document (MNI/BoI/End.HTM), just like the
"End of the Book of Fundamentals"
(MNI/BoF/End.HTM) and the
"End of the Book of Symbols"
(MNI/BoS/End.HTM).
This is more in line with the original paper
Model in which these texts were printed on
separate pages as well.
While the addition of a new file or the deletion of an old file is always
mentioned here, changes in the contents of old documents need not be.
This equally applies to the formats of already existing files.
Since the introduction of the latest F7 format (discussed below), it is
not only new text files which are presented in this format, but also more
and more old text files.
However, such revisions are not listed separately here.
In Southern Early and Mid-Yule
On 65.37.1 TRINPsite comprises 917 public files, of which approximately
715 different or 'unique' ones: 122 *.htm (not *Txt.htm), 6 *.html,
443 *.HTM, 1 *Txt.htm, 6 style sheets, 9 JavaScript files, 85
pictures, 4 ikons and 39 sound files.
In the 34th week a new format was introduced, with the code F7.
While F7 is the latest format, all previous formats are used
as well for the time being.
They are, in reverse chronological order:
| HTML FILE FORMATS |
| CODE |
DATE |
NEW CHARACTERISTIC |
| F7 | 65.34.6 | heart/whole body option |
| -- | 64.42.5 | surfing/reading/printing options |
| -- | 60.40.7 | inline frames on the right |
| F6 | 59.48.1 | suitable for non-JS browsing |
| F5 | 59.01.1 | with external file truth values |
| F4 | 58.11.1 | features rainbow objects |
| F3 | 57.45.2 | allows VBScript |
| F2 | -- | makes use of HeadObjs.js |
| F1 | -- | with correct resizing |
| M2 | 56.45.4 | -- |
| M1 | 56.15.7 | with floating menus |
| V | -- | with validated HTML |
| J | -- | with JavaScript script(s) |
In this context a format is a source code scheme which applies to each
page in a collection of pages.
A change of format usually does, but need not, entail a change of
presentation, while the presentation of a page or a collection of pages
may change considerably without a change of format.
Thus, the introduction of inline frames on the right in cases in which the
viewing window was wide enough, altered the appearance of the pages in
wide windows a great deal, but the format remained the same (F6).
The is because the changes were made in the external Javascript (JS)
and Cascading Style-Sheet (CSS) files, and not in the HTML code of the
pages themselves.
The main reason for introducing a new format, format F7, was to make it
possible to present pages in inline frames in a much simpler form than in
the whole window.
Usually (first-order) inline frames are too narrow to allow pages to have
(second-order) inline frames in turn, but even without such inline frames
they normally still need horizontal scrolling to read their contents.
In the new format it is possible that a page which has been designed on the
first level for a (type page) width of 600 pixels, can be read without any
horizontal scrolling at a width of 200 to 300 pixels, while not much more
than the text and pictures incorporated into the text are made visible.
Such an inline frame does, then, not show the whole body of the web page,
but only 'the heart of the matter', that is, its heart.
Meanwhile, it has turned out that this heart/whole body option can also be
very useful for the main document (on the left) itself.
The presentation of the heart is the simplest presentation available and
very suitable for reading, at least as long as one does not work with too
wide a widow (since any built-in type page dimension is missing in this
case).
The heart display is accessed from the whole-body display by means of
outward pointing arrows, and the whole-body display from the heart display
by means of inward pointing arrows.
This required one original picture (say, HeartTL.gif) and three derivative
ones (HeartTR.gif, HeartBL.gif and HeartBR.gif).
Apart from reading, in a wide window the heart display may give a good
overview of the page one is visiting.
With the introduction of the new F7 format an up-to-date TRINPsite web page
has now the clearest structure possible: a top part, a middle part and a
bottom part with their own external JS files programmed to 'write' these
parts.
MidPart.js is a new ANSI Javascript file especially created for this
purpose, together with MidPart_UC.js, a Unicode copy.
The bottom frame contents of the old FramSub.js, which was a standard
external file until F6, were moved to BotPart.js.
(For the top frame contents there never was such a separate file.
They always formed part of TopPart.js.)
Before the top part there is a 'pre-page' part, and after the bottom part a
'post-page' part, again with their own JS files for building and writing
what precedes the page and what follows it after it has been developed.
In addition there is a general JS file for head-related functions and a
general one for body-related functions.
The total F7 scheme with the standard external JS files looks therefore
as follows:
| HEAD | | HeadObjs.js |
| BODY | | BodyObjs.js |
| | PRE-PAGE | | PrePage.js |
| | | TOP | | TopPart.js |
| | | MIDDLE | | MidPart.js |
| | | BOTTOM | | BotPart.js |
| | POST-PAGE | | PostPage.js |
It is precisely because of this very logical structure that more and more
of the presentation of pages can be handled at a central point (one or
more of the external JS and/or CSS files) without having to touch the
separate HTML pages themselves at all.
Unfortunately, a web page design which works perfectly today in a
particular browser may not work perfectly tomorrow in the same browser.
Thus, pictures were always rendered correctly when using Internet Explorer,
but from version (7 or) 8 Internet Explorer somehow developed the sudden
need to make everything below a picture 'fall down' a few pixels when
moving a cursor over the picture.
This irritating phenomenon can still be seen in standard TRINPsite pages
with an F6 or older format, when using Internet Explorer 8, that is.
In the new F7 format the scripting of the images has been changed to get
around this silly problem.
In the Northern Months and Equatorial
On 65.29.1 TRINPsite comprises 901 public files, of which approximately
713 different or 'unique' ones: 122 *.htm (not *Txt.htm), 6 *.html,
443 *.HTM, 1 *Txt.htm, 6 style sheets, 8 JavaScript files, 84
pictures, 4 ikons and 39 sound files.
Altogether only three new documents were created in this period, all of
them in Equatorial Month.
They are three new *.HTM letter files for the
Spelling and Stress Dictionary, which is
still under construction, but contains more and more lemmas of the
Vocabulary of Alliteration every month.
The letters added to the dictionary folder were:
B,
G and
R.
This means that 13 out of 26 letters are now being presented in
separate documents, rather than in the main document itself.
|
