an_art_experiment_localized_into_English.pdf (11.7 KB)
LOCSE031.TTF (116 KB)
William Overington
27 October 2012
The Localizable Sentences 031 font includes, as well as all of the mapped glyphs in the Localizable Sentences 028 font and all the mapped glyphs for the art experiment, two other mapped glyphs.
Here is some transcript.
Start of transcript
25 August 2012
Open LOCSE028.TTF
Save as LOCSE029.TTF Localizable Sentences 029
Signs for stadium visual display screens
Add two glyphs, mapped to U+ED00 Alt 60672 and U+ED01 Alt 60673.
Set the advance with to 2048 font units.
U+ED00 If you are able to stand, could you please stand.
U+ED01 Please be seated.
End of transcript
The design of these two glyphs was an interesting situation.
All of the previous glyphs for localizable sentences each encoded as a single character in this experiment in communication through the language barrier had been in a cell with an advance width of 6144 font units (=24 x 256) and had a glyph width of 5888 font units (= 23 x 256) with a structure built around sections, of widths, in units of 256 font units, of 7, 1, 7, 1, 7. This has proved useful for being able to have the leftmost section indicating to which group of related glyphs the particular glyph belongs, with detail being in the centre and righmost wider sections.
However, I thought that such quite complicated design glyphs, which would usually not be analysed by an end user of an implemented system (if such an implementation is ever built), would not be best for symbols that would be displayed with the intention that people would know their meaning by looking at them. So I made these two glyphs 1792 font units wide (= 7 x 256) in a cell with an advance width of 2048 font units (=8 * 256 font units).
This allowed simpler designs to be used for these two glyphs.
William Overington
1 November 2012
Supplementary note of 25 April 2013
This post contains a font. The next post in this thread contains a later version of the font.
If experimenting please use the later font. No mappings have changed, just the glyph designs of the ten localizable digits for use solely within localizable sentence markup bubbles so as to make them more readable by humans.
The original post is after this supplementary note.
William Overington
25 April 2013
End of supplementary note of 25 April 2013
Some readers may have noticed the thread on Encoding Localizable Sentences that is running in the Unicode mailing list at the present time.
The posts are archived and the archive can be accessed on the web.
My post from earlier today is as follows.
In that post, which as it happens includes a link to a post earlier in this present thread, I wrote as follows.
quote
I am hoping to prepare Simulation 6 to show a simulation where the localizable sentences could be encoded within a plain text message using localizable sentence markup bubbles and Simulation 7 where there is a mixture of the two encoding methods. This will need first of all a new version of the font so as to have symbols for the localizable sentence markup bubble brackets and ten localizable digits for use solely within localizable sentence markup bubbles.
end quote
I have now produced the new version of the font to which I referred.
Here is the font.
LOCSE032.TTF (117 KB)
The ten localizable digits for use solely within localizable sentence markup bubbles are encoded from U+ED80 through to U+ED89 with Alt codes from Alt 60800 through to Alt 60809.
The localizable sentence markup bubble brackets are encoded at U+ED90 and U+ED91 with Alt codes of Alt 60816 and Alt 60817.
I have made the designs for the two localizable sentence markup bubble brackets deliberately not horizontal mirror images of each other in case that might cause problems if intermixing them within right to left scripts. I do not know enough of right to left scripts to know if there would be a problem, so I thought that I would seek to design the glyphs so as to avoid any problems that might arise.
William Overington
22 April 2013
I tried using the Localizable Sentences 032 font in the production of documents for simulation 6 and simulation 7.
Although the font worked well, nevertheless I found the results somewhat hard to read. I was trying to have a ‘computer-look’ effect.
So I have redesigned the glyphs for the ten localizable digits for use solely within localizable sentence markup bubbles. They are not so wide now. Hopefully they are now easier to read yet still have a ‘computer-look’ effect. The mappings are unchanged.
There has been no change at all to the glyphs or the mappings of the two localizable sentence markup bubble brackets.
This means that the brackets and the digits do not have the same advance width anymore.
I particularly want the brackets to have square glyphs.
Here is the new font.
LOCSE034.TTF (119 KB)
William Overington
25 April 2013
I have now produced Simulation 6.
locse034_simulation_six.pdf (32.7 KB)
William Overington
25 April 2013
In the event, research has progressed and Simulation 7 does not, in fact, simulate the scenario that I had in mind at the time that I wrote the above note.
Simulation 7 is now a more advanced scenario involving a simulation where the localizable sentences could be encoded within a plain text message using localizable sentence markup bubbles and the original glyphs, for display only in situations where display of them were desired, would not be mapped directly but would each be accessed using glyph substitution from a localizable sentence markup bubble using an advanced format font.
locse034_simulation_seven.pdf (34.9 KB)
William Overington
25 April 2013
I have submitted a proposal to the Unicode Technical Committee with the following title.
A proposal for encoding twelve localizable sentence markup bubble characters, together with a request for action to set up an encoding infrastructure for the encoding in a separate standardization document of complete localizable sentence markup bubbles using those twelve characters
The document is available from a link labelled L2/13-079 on the following web page.
The meeting of the Unicode Technical Committee is due to take place from 6 May 2013 through to 10 May 2013 at San José in California.
A person can send in comments on the proposal and request if he or she so chooses. I think that comments will be listed in the Current UTC Document Register 2013 page and be available for public viewing. The first page linked below lists an email address to which one may send an email with a pdf as an attachment to the email. The second page linked below includes a form and is for typed text only.
William Overington
1 May 2013
Here is a new research publication.
Communication_through_the_language_barrier_in_some_particular_circumstances_by_means_of_encoded_localizable_sentences.pdf (47.8 KB)
William Overington
17 February 2014
Here is another new research publication.
The_format_of_the_sentence.dat_file_used_for_automated_localization_of_encoded_localizable_sentences.pdf (57.5 KB)
The following has been of great value in my research.
William Overington
19 February 2014
The ubiquitous IrfanView includes a feature named HEXView (accessed via the F3 function key) but it’s nice to see an ‘in-house’ solution. 
Reference:
William Overington
22 February 2014
It is now 9:29 am United Kingdom time as I write.
This morning I have tried making a font for the first time since I got my new laptop computer, running Windows 8, following the break down of the Windows xp computer that had served well for many years.
This went very well.
Here are the notes that I made as I went along.
====
Saturday 5 September 2015
This is the producing of a font relating to the following Unicode mailing list forum post.
8:11 am
Experimental font LOCSE701.TTF
Start by opening LOCSE034.TTF
Save as a new project LOCSE701
Except for the two localizable sentence markup bubble brackets and the associated digits, remove the Private Use Area glyphs as this is just to be a minimum font for the purpose.
Rename the font as Localizable Sentences 701 and set export names as LOCSE701
Insert code points for U+EE30..U+EE39 and for U+EFFF.
The code for the Insert characters facility is
$EE30-$EE39,$EFFF
Copy just the glyphs of the digits still in the Private Use Area to U+EE30..U+EE39.
Delete the originals.
Adapt and combine the glyphs of the two localizable sentence markup bubble brackets to produce a glyph for the base character.
Delete the originals.
The glyphs for the base character and the digits will only show when there is no automated localization in action.
Now, as these are experimental glyphs in a Private Use Area, add an E below the base line so that if the base glyph is ever encoded into regular Unicode there will be no confusion.
Validate the font.
Test the font using the preview panel.
Export the font.
8:56 am
8:59 am
Change version string to show the date as I like it, day month year style.
Export the font.
Close the project file.
9:06 am.
Open the font.
Install the font.
Test the font using PagePlus X7.
====
Here are graphics exported from PagePlus X7.
Here is the font.
LOCSE701.TTF (12.5 KB)
William Overington
5 September 2015
Readers who would like to try the font yet who do not have any software that has an Insert Symbol facility may find the following useful.
I have typeset the eleven characters from the plane 0 Private Use Area within Serif PagePlus X7 and I have produced eleven lines of text, each of which consists of a note of the Unicode code point that I have used for the character together with the character itself between two = signs.
This use of the = signs is because in some browsers the characters may be shown as a black rectangle, or as a black square with the hexadecimal code within it, or just show nothing, just leaving what looks like a space.
The = signs will hopefully be useful guides if, for example, trying to copy from a web page and paste into WordPad.
To display the glyphs in WordPad the font would need to be installed, perhaps only temporarily, and then the characters formatted using the font. It is sometimes necessary to only open the application program once the font has been installed.
Anyway, in the hope that they will be useful, here are the eleven lines of text.
U+EE30==
U+EE31==
U+EE32==
U+EE33==
U+EE34==
U+EE35==
U+EE36==
U+EE37==
U+EE38==
U+EE39==
U+EFFF==
If you have any questions, please feel free to ask.
William
Please know that I have now added an additional page to our family webspace.
It is a web page about one possible way of encoding localizable sentences: each localizable sentence encoded using a base character followed by a sequence of tag characters, the same base character for each encoded localizable sentence.
The page has transcripts of the two previous posts of this thread, listed after transcripts, in chronological order, of my two posts to the Unicode mailing list about the possibility of encoding a localizable sentence using a base character followed by a sequence of tag characters.
The page is linked from the following web page.
William
Some readers might enjoy the following.
William Overington
5 October 2015
Here is a font with LOCSE702.TTF as the file name and Localizable Sentences 702 as the font name.
LOCSE702.TTF (12.6 KB)
The font is based on the Localizable Sentences 701 font and adds an experimental glyph for PANLEX BASE CHARACTER at U+EF70 for concept proving experiments.
The glyph design for this Private Use Area mapping has an E below it so as to seek to avoid confusion in case the glyph itself ever becomes encoded into regular Unicode.
The character is at U+EF70 for which the Alt code is Alt 61296 in case readers would like to use that entry method in the WordPad program.
The character is available to be copied onto the clipboard of a PC from between the equals signs in the following line.
U+EF70==
William Overington
7 October 2015
Here is a pdf document that I produced yesterday.
two_tagspaces.pdf (53.8 KB)
William Overington
8 October 2015
Here is a document that I produced on Monday 19 October 2015
a_preliminary_proposal_to_encode_two_base_characters.pdf (56.3 KB)
William Overington
21 October 2015
Recently I tried an experiment learning about using tag characters on a web page.
There is a link on that web page to a font that I produced in 2009 that has visible glyphs for the tag characters.
At that time the tag characters had been deprecated in Unicode, yet most of them are now no longer deprecated.
Two files (namely tagtests.htm and a pdf linked from within tagtests.htm) are linked directly from the following web page, the links are currently at the lower end of the page.
An interesting note is that I found the font file from a post in this forum.
I remembered that I had made a font with tag characters in it but I did not remember why I had made it.
I downloaded the font file from this forum, tested it, installed it on my computer and then uploaded it to my family webspace.
In the event, although I am now using tag characters for a different purpose than the purpose for which I made the font, the font, unaltered, has now been of great usefulness to me in my research.
William Overington
13 January 2016
This morning I tried a further experiment.
The experiment is inspired by the following document.
William Overington
6 February 2016