|
このページはEtoJ逐語翻訳フィルタによって翻訳生成されました。 |
This page is "browser friendly". Make your browser window as wide as you want it. The text will flow nicely for you. It is easier to read in a 狭くする window. With most browsers, 圧力（をかける）ing 加える, minus or 無 while the 支配（する）／統制する 重要な (ctrl) is held 負かす／撃墜する will change the texts size. (大きくする, 減ずる, 回復する to default, それぞれ.) (This is more fully explained, and there's another tip, at my 力／強力にする Browsing page.)
The style of this tutorial is a little unusual. It doesn't explain "everything" in the 使用／適用 it 会談 about, it only covers some of the 最高潮の場面s. The tutorial is also unusual in that it rarely if ever 引用するs the code for doing things. For that, you will have to 協議する the sourcecode, which, you can download in a .zip 古記録, along with a 収集するd copy of the 使用／適用.
I 現実に needed an 使用／適用 to do something for me, and while I was 令状ing it, I made some 公式文書，認めるs which 結局 made their way to the web in the form of the page you are reading.
What did I need the computer to do for me?
I 手配中の，お尋ね者 to enter a date, a one letter "serial", and a short description of a 調書をとる／予約する. The computer's 職業 was to create "bookplates" (slips, at this 行う／開催する／段階, really) with the （警察などへの）密告，告訴（状） I'd entered 減ずるd to a 基準 判型 and 補足（する）d with a one letter checksum.
The window in the screenshot may seem コンビナート／複合体, but using it is really 平易な... 特に as the date may stay the same for several 調書をとる／予約するs, with only the serial needing changing.
The program uses an ini とじ込み／提出する to keep 跡をつける of the size and position of the window when the 使用／適用 is の近くにd.
The 使用者 can create several "bookplates", and then print them as a （製品，工事材料の）一回分, on one piece of paper, to be 削減（する） up to derive a slip for each 調書をとる／予約する.
The page you are reading now concentrates on how you would create a program, using Lazarus (or Delphi), to help you with the chore of cataloging some items of a collection, cataloging them with a database.
In my tutorials about using the OpenOffice database, I have done a more 完全にする discussion of how the unique identifier was designed.
For a new page discussing easily managed short, computer friendly, unique identifiers, written when I had 8 years more experience in producing this ort of thing, see the page the link takes you to. It is HTML5 friendly, in 新規加入 to it's other 長所s.
Given that you have 設立する your way to this page, you might alos be 利益／興味d in some work I did in 2020 with creating bookplates with barcodes on them. (There's nothing about the 事業／計画（する） that 特に 関係 it to managing 調書をとる／予約するs. That work 伴う／関わるd その上の checksums, の中で other things. (Barcodes often have their own checksums, in 新規加入 to the checksums discussed below.)
As I said... the 使用者 will enter some data. For my wants, it happens to be about a 調書をとる／予約する, but it could be an instance of another class of 反対する. And the 使用／適用 will 生成する a short (ish) string of characters which should be 満足な as a unique identifier for that 調書をとる／予約する. If you know about databases, you will understand what I mean if I tell you that the ID will be the 最初の／主要な 重要な for the 調書をとる／予約する's 記録，記録的な／記録する in my database 述べるing my collection. If you don't know about databases, you might find them useful, and I can help! I have a 一連の tutorials to get you started with the wonderful database which is part of the 解放する／自由な, multi 壇・綱領・公約 OpenOffice.
どこかよそで, I've written in 詳細（に述べる） about why I chose the 計画／陰謀 I used for producing the unique identifiers. (A 草案 is written... when I get THIS essay out the door...)
There is a method in the madness(!). For now, here's what I （機の）カム up with:
The unique identifier will be a string of seven characters. It will be made up as follows....
... in which L is a letter (a-z, A-Z), D is a digit (0-9), and X is either a letter or a digit. No letter carries an accent. No punctuation 示すs are used.
The ID may also be 述べるd by....
cyymdds
(P.S.: The "c" part will 現実に usually be a "f".. this is 予定 to a change from defining "a" as 18 to defining it as "15"... a change in the 早期に 行う／開催する／段階s of the programming, but after the 本体，大部分／ばら積みの of the documentation was done. At this point, the 残り／休憩（する） of this 文書 反映するs the old 計画（する）... "c"=20)
Any string of characters can be 変えるd to a string of digits, and a string of digits can be 扱う／治療するd as a number. One you have a number, there are 平易な ways to derive a checksum. So after the 使用／適用 has collected the 成分s for the unique identifier, inside the machine the ID is 変えるd into a number, and from that a checksum is derived. We are now going to go into the 詳細（に述べる）s a 使用者 is spared.
I also 申し込む／申し出 a short "basic 概念s" 公式文書，認める on checksums, if you are 利益／興味d.
As an example for our checksum calculating 演習, we are going to use "c12a07d"
That, 明白に, isn't a number. Do do checksums, life is a lot easier if we have numbers.
Even a string just of digits isn't やむを得ず, in fact, a number. If I have a three digit combination on my briefcase lock, and it is 始める，決める to "420", then that's just a string of characters. The fact that 420 is twice 210 is irrelevant... to my needs as the owner of the briefcase. The 420 is just a string of digits.
The string of characters we want to create a checksum for does 含む／封じ込める a human-readable （警察などへの）密告，告訴（状）.
The "c12" stands for the year 2012.
The "a" stands for October. (1-9 were used for January to September, but a choice was made to keep the code for the month to one character, hence a, b, c for October, November, December.)
The "07" stands for the seventh day of October 2012.
Don't worry about the "d", just take on board that it is part of the ID string we need to do a checksum for.
The ID string, in the form c12a07d, has its uses. We're going to start our 旅行 the checksum by changing it to something いっそう少なく readable, but more arithmetic friendly:
WHERE DID THAT COME FROM???
c-12-a-07-d
02-12-11-07-03
All we did was to turn any letters into digits, using in every 事例／患者 two digits for each letter.
For the first and last letters, we used: make "a" 00, "b" 01, "c" 02, etc.
If there is a letter in the middle of the string, 取って代わる it with 10 if it is "a". 11 if it is "b", 12 if it is "c". If there is a digit in the 4th position in the string, 変える it to itself に先行するd by a 無. (e.g. c12807d would become 0212080703
As we have been 約束d that only digits and lower 事例／患者 letters will occur, the simple 計画／陰謀 is all that we need.
So! That gives us a string of digits. If we 扱う／治療する them as a number, what is the biggest number which can arise? (as long, as we were also 約束d, that the biggest letter at the start of the string will never be more than "j")
(Yes... we "count from" 0 when changing the first or 終点 letter to a number, 0 for "a", 1 for "b", etc.... hence 25 for "z". the 半端物 coding for the 内部の letter arises because that character is for a month: "1" for Jan, "2" for Feb... "a" for Oct (10th month, if not counting from 無) "b" for month 11, "c" for month 12.)
All of that may seem very 複雑にするd... but remember: All of the tricky bits will be 扱うd by a computer program.
So! "c12a07d" became "0212000703"... which can be 扱う／治療するd as a number
And, if you 適用する the same 支配するs to the unique identifier, and 扱う／治療する the resultant string of digits as a number, and you choose your unique identifier with care, the biggest number you can get is...
.... which, of course, we would usually 令状 as...
Why do I care?
Remember when you were 6 years old, and "the biggest number possible" was an exciting idea?
Computers aren't as clever as six year olds, and can't (easily) just 追加する another 無, trumping...
100000000000 with...
1000000000000
I'm trying to do my checksum work in both the 大型の language of Open Office's excellent, 解放する／自由な, multi 壇・綱領・公約 database, and the 解放する／自由な, multi 壇・綱領・公約 Delphi-like language "Lazarus".
Happily, both languages have a data type which can を取り引きする unsigned integers of 6 decimal places... the LongWord type (0 .. 4,294,967,295, four bytes) in the 事例／患者 of Lazarus, and Integer in the 事例／患者 of OpenOffice (all modules). (Integer 許すs 消極的な 2,147,483,648 to 肯定的な 2,147,483,647, OO not having a large unsigned datatype, we'll use this. It is still big enough.)
What was that all about? You do need to look at this sort of thing before you start to 令状 programs. Sorry! (What if your unique identifier had so many characters in it that it resulted in a number that was too big to work in with the usual arithmetic 機能（する）／行事s of the language you were using? You would get a "範囲 Check Error". Tedious.)
Whole 調書をとる／予約するs have been written on 計画／陰謀s for 生成するing checksums.
A really simple 計画／陰謀 would be as follows...
To create a checksum for "758", you could 追加する the three digits together: 7+5+8: 20. If you 手配中の，お尋ね者 just one digit for the checksum, you could use just the 部隊s. In other words, "throw away" the "2" of the "20".
A major problem with that too simple answer is that you get the same checksum for "785", which may very 井戸／弁護士席 be what some careless person will enter when they try for 758. Sigh.
For my needs, there is something which will catch transpositions, but isn't hard to 器具／実施する. It is using the "mod" 機能（する）／行事.
0 mod 3 is 0 1 mod 3 is 1 2 mod 3 is 2 3 mod 3 is 0 4 mod 3 is 1 5 mod 3 is 2 6 mod 3 is 0 7 mod 3 is 1 8 mod 3 is 2 9 mod 3 is 0 10 mod 3 is 1 11 mod 3 is 2 12 mod 3 is 0 13 mod 3 is 1 14 mod 3 is 2 15 mod 3 is 0... etc
The answer to x mod y is always no more than y-1
Now... if we use "mod 3" as the 支配する for making our checksum, then only three checksums arise: 0, 1 and 2. So, just by (広告) luck, we have a 1 in 3 chance of getting the "権利" checksum to the wrong number. The checksum is the same for both 11 and 14. This is always a problem, in 原則, with checksums....
But we can make the practice useable... with a bigger "y".
If we were 用意が出来ている to use a two digit checksum, we could do the number-to-be-checksumed mod 100, and get checksums from 00 to 99. Now there's only a one in a hundred chance of the wrong number having the same checksum as the number we are trying to 保護する.
But I want it all! I want short unique identifiers (含むing the checksum) and 強健な checksums.
The first step is to use a character for the checksum, and 扱う／治療する it as a number. "a" for 00, "b" for 01, etc.... gives us a way to 令状 0 to 25 as our checksum for the cost of only one character.
And we'll get a little fancier. I want to leave out "oh" and "ell" (o and l), because it is so 平易な to 混乱させる them for 無 and one (0 and 1).
Not a problem. I'll just make a 名簿（に載せる）／表（にあげる） of the characters I am 用意が出来ている to use.... and the "value" of a given character will be it's position in the 名簿（に載せる）／表（にあげる）....
a b c d... j k m n p... 00 01 02 03...09 10 11 12 13
AND, as long as 使用者s understand that the checksum character is 事例／患者 極度の慎重さを要する, I can go on....
A B C D... 22 23 24 25...
Why was "A" 割り当てるd to 22? Surely it would be 27? Ah! But some of the letters from a-z were left out, weren't they? (Whether in the final program "A" ends up at 22, or at some other number nearby I don't at this 行う／開催する／段階 know or care. I know that I can 代表する about 50 numbers with a 選び出す／独身 letter, if 事例／患者 counts, even if I leave out things like "oh" and "ell". WHICH get left out, and how things are done, you can see for yourself by looking inside the program's code.
So that's it, for the 必須のs of how the checksum will be calculated and 代表するd. The 残り／休憩（する） of this tutorial 演説（する）／住所s 問題／発行するs of 使用者 interface.
Let's just be （疑いを）晴らす about what it is for. Always important, and not just if you are 令状ing a tutorial, like this one. Even if you are the only person 伴う／関わるd in the 開発 of a new 使用／適用, you need to be （疑いを）晴らす about what is it for long before you do any programming.
When the 使用／適用 is finished, I 想像する myself sitting 負かす／撃墜する at my desk with some uncatalogued 調書をとる／予約するs. I will 記録，記録的な／記録する some basic data about each on a data 逮捕（する） form... and 署名／調印する-on-paper first "home" of the data. When... not if... the computer 衝突，墜落s, and I have to 再構築する the database, I will have what I need.
For our 目的s, we can imagine that the database 単に 持つ／拘留するs each 調書をとる／予約する's unique identifier, author 指名する, 肩書を与える. We'll also 調査する managing the invoices which go with the 調書をとる／予約するs. Each invoice will get a unique identifier, of a わずかに different design than that for the 調書をとる／予約する, and the database will 持つ／拘留する その上の さまざまな things, tied to that ID. For our 目的s just the date on the invoice and the 販売人's 指名する will give us enough "grist" for our "mill".
If you are new to databases, it may surprise you, but there will be two "（米）棚上げする／（英）提議するs", two things a bit like spreadsheets. One line per 調書をとる／予約する or invoice (these are the "記録，記録的な／記録するs"), one column per "thing" we are 跡をつけるing... ID, 肩書を与える, author, etc. (These are the "fields".) You might think that this 暗示するs "two databases". Not at all. Many databases have 多重の （米）棚上げする／（英）提議するs. It will, however, mean two data collection 文書s, one for the 調書をとる／予約するs, one for the invoices.
Why I について言及する the に引き続いて will become （疑いを）晴らす as we go along.
All of my databases have unique identifiers. More 最近の ones are in the form "FDBxxx" where FDB stands for FreeDataBase, for the database which is part of Open Office, and xxx is a three digit serial number. I have a sheet of paper telling me that FDB001 持つ／拘留するs my friends' birthdays, and FDB015 is a database of 調書をとる／予約するs I've read, etc. The FDB 索引 for my 調書をとる／予約する collection is 016
While I'm 現実に working within a given database, I don't have to continually repeat the appropriate "FDBxxx"... it is 暗示するd. When I do use it will become （疑いを）晴らす...
I'd start a data 入ること／参加（者） 開会／開廷／会期 by 記録，記録的な／記録するing the first invoice. I'd create a new line on the "Invoices" （米）棚上げする／（英）提議する's data collection 文書. An ID would be created for the invoice, and that and the invoice date and the 販売人's 指名する would be 記録，記録的な／記録するd, "単に" handwritten paper, for now. The database's ID for the invoice would be written on it, prefixed "FDB016". Anyone with just the invoice in their 手渡す deserves some help with what the string of characters in the upper corner is about.
Next I would turn to the first 調書をとる／予約する 名簿（に載せる）／表（にあげる）d on that invoice. I would （不足などを）補う an ID for the 調書をとる／予約する, によれば the 支配するs discussed どこかよそで. On the "調書をとる／予約するs" data collection form, the 調書をとる／予約する's unique identifier, apart from the checksum, would be entered. A blank-for-now column would 存在する for the checksum. The author's 指名する and the 調書をとる／予約する's 肩書を与える would be entered. And the database's unique identifier for the 関連した invoice.
... and then I would do the same for the 残り／休憩（する） of the 調書をとる／予約するs on that invoice, then 過程 the next invoice and its 調書をとる／予約するs, and so on until all the 調書をとる／予約するs and invoices to be 過程d have been entered on the pencil-or-署名／調印する-on-paper data collection sheets.
And we 港／避難所't yet touched the computer! Whew! Good!
Now, 式のs, we do have to turn the computer on.
I'd bring up the database, filling most of my 審査する, and CD93 (the 使用／適用 this essay is about!) in a corner of the 審査する.
I'd then start entering the data from the data collection sheets into the computer. More on the 詳細（に述べる）s of that in a moment.
As I （機の）カム to each 調書をとる／予約する, I would enter the 関連した 詳細（に述べる）s into CD93, which would give me the 権利 checksum for them, along with the unique identifier in 正確に the 権利 form... 主要な 無s not omitted. "November" coded as "b", etc.
I'd 令状 the checksum in on the data collection sheet, in 事例／患者 it was needed later. I would either 令状 (pencil!) the 調書をとる／予約する's unique identifier, with checksum, in the 調書をとる／予約する, or get the computer to print it on a slip of paper to be put with the 調書をとる／予約する. The ID would be prefixed "FDB016". You find all sorts of things written in the flyleaves of 調書をとる／予約するs... The "FDB016" should be a help to 認めるing the 権利 string of characters for tying the 調書をとる／予約する to the （警察などへの）密告，告訴（状） about it in the database.
That's it! That's the overview of the heart of my 調書をとる／予約する collection 目録ing system.
Now for a few 詳細（に述べる）s of the ID/ checksum 生成するing program.
A lesson in program design: All of the text above was pretty 井戸／弁護士席 finished before I started "令状ing the program", i.e. before I turned Lazarus on and put the first button on the form which would grow into CD93. In place of the screenshot you see below, I 挿入するd a placeholder. And, not until then, I did a sketch, 署名／調印する-on-paper, of what the 審査する would look like. Did all of that take time? Of course! Did the text flow from the brow of Zeus, or Minerva, or whoever, 権利 first time? Of course not. But, to 改訂する elements of the above was really やめる simple. I considered さまざまな 判型s for the unique identifier, in particular... and each time I changed my 計画（する） for how to do it, parts of the text had to be altered. But making those alterations was a lot easier than making changes in a growing program. And the text will serve as my documentation for What The 使用／適用 Does, 必須の documentation which I would have needed to 令状 と一緒に 令状ing the program, if I were not doing this tutorial.
計画（する） first. In the sort of 詳細（に述べる） you see above.
Believe it or not, I've left out of what you see above many elements of my planning! (There could be more???) Things that I know I can carry in my 長，率いる about how I am going to do things. Unless I've made a bad mistake, I do know what I am going to do, and that I know how to do that. Any 疑問s in those areas? Get the "whats" and the "hows" written 負かす／撃墜する in your documentation. いつかs it will 支払う／賃金 you to do a little "実験（する）" program, just to check that one of the things you want to do can be done. If you were new to the "mod" ("modulo") 機能（する）／行事, which is going to be at the heart of the checksum, you might want to do a little program which would let you put in some "x"s and "y"s and see what the computer gives you for "x mod y".)
A human enters the necessary data. The ID field is filled in by the computer. It will 持つ／拘留する "無効の" if anything in the data is amiss. (It is hard, but not impossible to put 無効の data in. For instance, if you say the 調書をとる／予約する was acquired on the 30th of February, the ID field will 陳列する，発揮する "無効の".)
At any time there is valid data in the form, a checksum for that data will appear in the "checksum" box, a place that only the computer can 令状 to.
Many data are entered by clicking 無線で通信する buttons, for instance the month of 取得／買収.
When all of the data for a given 調書をとる／予約する has been entered, the 使用者 will copy, by 手渡す, from the 審査する to the 署名／調印する-on-paper data collection form the checksum for that data.
使用者s availing themselves of the hardcopy 選択 will click the "追加する" button, which will 追加する that 調書をとる／予約する's ID string to the 文書 存在 用意が出来ている in the computer. 結局, I hope that this "文書" may consist of nice bookplates, one per 調書をとる／予約する, of course. In the 早期に days, the 文書 will consist of many lines, with 幅の広い vertical gaps, one line per 調書をとる／予約する.
When done... or when worried about losing 蓄積するd work!... the 使用者 will click the "Print" button, and the 文書(s) 蓄積するd so far will be printed out.
The "追加する"/"Print" 複雑化s arise because of our "modern" "page oriented" printers. "When I was a boy", it was no hassle to 生成する a 文書 a line or five at a time. The first 調書をとる／予約する's 挿入する could be printed at the 最高の，を越す of the first page, then the second 調書をとる／予約するs data entered, and then that 調書をとる／予約する's 挿入する printed on the next part of the same sheet, and so on. But that would be too simple, I suppose. (To be fair... it also 課すd 重要な 制限s on what we could do!)
Whew! That's it, I think! AT LAST I can turn to the fun stuff.... 令状ing the program. (Which I did! Almost all of the text above was written before I turned on my Lazarus. But I 港／避難所't recounted the blow by blow events of the "底（に届く） up 開発" here as I 普通は do in a tutorial. Sorry.)
We've talked extensively about what CD93 does. Here follow some 公式文書，認めるs on how the programming 遂行するs those 機能（する）／行事s.
-----------
It may be counterintuitive, and not the way we, as humans would do the 職業, but the program will continually re-calculate the checksum, doing it again and again, every time even one character of one of the 成分s of the ID string changes. In some 事例／患者s we will use the "hidden" path of the event handler for a change in the 支配（する）／統制する. どこかよそで, we will just call the 手続き "UpdateIDString" "by 手渡す".
For the sake of understanding the whole 過程, we will look at 牽引する of the "成分s" of the 過程.
The first 成分 is the "Century" box, laCentury, which continually 反映するs the contents of bCentury. Because of the way the program is written, it is (should be, anyway!) impossible to 割り当てる an 無効の value to bCentury. It can only be changed by clicking an "Up" button or a "負かす／撃墜する" button, and the program just ignores you if you try to go outside the valid 範囲.
The second 成分 is the edit box, eLSDYear, which should 持つ／拘留する two characters, and show something between 00 and 99. However, 存在 an edit box, 使用者s can type anything into it, even if our program can 速く "erase" unwelcome 入ること／参加（者）s.
--------
Besides the さまざまな obvious things on the 審査する, the program also 持続するs a 始める，決める of boolean variables for any 成分 of the ID string and checksum which can ever get into an 無効の 明言する／公表する, for instance the value in eLSDYear.text. Those booleans are 始める，決める to true if there is a 現在の valid value for the 成分, to 誤った さもなければ.
A 手続き called "UpDateIDString" will be called, every time that what is in an 成分 of the ID string is changed. It will 一般に recompose the unique identifier and attach the 権利 checksum. However, at the start of the code within UpDateIDString, a 実験（する） is made to see if any of the booleans 持つ／拘留する "誤った", in which 事例／患者 UpDateIDString 単に...
Oh yes... I forgot to について言及する!...
Each time a new ID string is 生成するd, it is copied to the clipboard, as if I had selected the string, by 手渡す, and 圧力（をかける）d ctrl-C. (Or used any of the other "copy" 誘発する／引き起こすs.) Because the 使用／適用 has this feature, you can easily use "paste" to fill in the appropriate field over on the database data 入ること／参加（者） 審査する.
Making the 使用／適用 do that is trivial, the 詳細（に述べる）s are in my tutorial on programmatic "copy to clipboard"; "paste from clipboard".
"All" I had to do was design the program 井戸／弁護士席 in the first place, and then find the 権利 place to 挿入する something like "copy it to clipboard"... and 供給する the necessary 組織／基盤／下部構造 for the "copy... to clipboard".
Search the sourcecode for "Copy CS+ ID to clipboard", and you'll find the one line that was "all" (apart from 組織／基盤／下部構造) that was needed to 供給（する） my want. Whew.
The line of code I 挿入するd was...
Clipboard.AsText:=(sCheckSum+sIDString);
Working from the "inside" out....
What was 供給するd by "sCheckSum+sIDString" in this 事例／患者 can be 取って代わるd by whatever text you want to send to the clipboard, either as literals...
Clipboard.AsText:=('Send these words');
... or using variables. No ロケット／急騰する science there.
The "AsText" is the 指名する of a 所有物／資産／財産 of the Clipboard 反対する. Again... this may be a new 所有物／資産／財産 to you, but it is no more "strange" than, say, the "caption" 所有物／資産／財産 of a label.
Things do get strange when it comes to the 反対する, "Clipboard". Usually, we 宣言する instances of types, e.g. we create an edit box called "eDay", of the type "TEdit".
For working with the system's clipboard, things are done just a little 異なって.
First, you 追加する "ClipBrd" to the 事業／計画（する）'s "uses" 条項.... and then you are done! And you have, whenever you want to use it, an 反対する 指名するd "Clipboard", with an AsText 所有物／資産／財産 that you can 割り当てる things to. 遂行する／発効させる "Clipboard.AsText:='Fred';", and すぐに, anything in the system clipboard is 取って代わるd with "Fred".
It is only 混乱させるing because it is 類似の to other things, but different. It is like using an edit box, and "playing" with what さまざまな 所有物／資産／財産s are 始める，決める to. However, it is different in that you can only have one "Clipboard", and that is the 指名する of the instance of the type of 反対する. And you don't have to "始める，決める up" the "Clipboard" 反対する. It is just there. But you can't use a different 指名する for it. Simple... really... even if it doesn't sit 井戸／弁護士席 until you've slept on it. Sigh.
Maybe this will help, not only your しっかり掴む of "Clipboard", but perhaps also with 人物／姿／数字ing out how the printing code 作品: The "Clipboard" 反対する is a bit like the "Printer" 反対する used within the program. Both are mostly ordinary 反対するs. They are a little strange in where they come from.
End of "blow- by- blow"!
===But I 港／避難所't forgotten to create the .zip you can download with the 使用／適用 and sourcecode!
|
|
If you visit 1&1's 場所／位置 from here, it helps me. They host my website, and I wouldn't put this link up for them if I wasn't happy with their service. They 申し込む／申し出 things for the beginner and the 会社／団体.
Page 実験（する）d for 同意／服従 with INDUSTRY (not MS-only) 基準s, using the 解放する／自由な, 公然と accessible validator at validator.w3.org. Mostly passes. There were two "unknown せいにするs" in Google+ button code. Sigh.
....... P a g e . . . E n d s .....