Page 実験（する）d for 同意／服従 with INDUSTRY (not MS-only) 基準s, using the 解放する／自由な, 公然と accessible validator at validator.w3.orgMostly passes. There were two "unknown せいにするs" in Google+ button code. Sigh.|
このページはEtoJ逐語翻訳フィルタによって翻訳生成されました。 |
Bookmark this on Delicious
Recommend toStumbleUpon
You may find that the database 含むd in OpenOffice delights you as much as it has me. This page tries to help you use it.
Remember that Open Office, 含むing ooBase, is 解放する／自由な. Don't let that fool you, though. Big organizations, 政治の and 非軍事の, have 可決する・採択するd it as their 基準 office 控訴... and saving million$, but still Getting The 職業 Done. And making things 平易な for 使用者s on different 壇・綱領・公約s... Linux, Mac, Windows all spoken here!
There's more about ooBase in the main 索引 to this 構成要素. Adabas? 星／主役にする Office? 古代の history.
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 fully explained, and there are more tips, at my 力／強力にする Browsing page.)
Page contents © TK Boyd, Sheepdog ソフトウェア, 3/06- 12/12.
I was playing about with these, and this tutorial relates what I have discovered so far.
I accidentally wrote another tutorial which covers much of what this covers. If you want more "手渡す 持つ／拘留するing", more "now type..." stuff, try the other tutorial. If in 疑問, continue with the one you are reading.
In fact, I've written several tutorials with "関係s" (as in "relational database") at their 核心, and so have produced a sub-menu page for these 関係のある essays.
The に引き続いて may seem like an awful lot of work... a bit of an elephant gun for the mouse in my sights. However, remember it is just to illustrate something... and that something entails important 概念s. One quickly しっかり掴むd advantage of doing this sort of thing the way I'm going to show you, the "hard" way, is that, for instance, if you mistype Bach's 指名する, it will be obvious... every 言及／関連 to Bach will be wrong, AND you only have to 直す／買収する，八百長をする one 入ること／参加（者） to 直す／買収する，八百長をする all of the manifestations of the error. Also, you can ESSENTIALLY (without 現実に) "type" "Wolfgang Amadeus Mozart" dozens of times, 簡単に by typing just "wamo" those many times.
By the way... did you know that Mozart was also known as WG Mozart? More on this later, when you've puzzled on it.
Turning 支援する to forms 陳列する，発揮するing data from 多重の （米）棚上げする／（英）提議するs...
Imagine a world where every 音声部の CD consisted of music by just one 作曲家. (Many 作曲家s, but only one on any given CD.) Imagine also that each CD has a unique code, a bit like an ISBN, but much shorter!
始める，決める up two （米）棚上げする／（英）提議するs:
First （米）棚上げする／（英）提議する: "CompNam" 作曲家's 指名するs.
Fields:
CompNameID- 4 characters, text (Abbreviated 指名する. 始める，決める as 最初の／主要な 重要な) CompName- 20 characters. (Human friendly 見解／翻訳／版 of 作曲家's 指名する)
見本 data... but don't enter it into the computer before you are told to...
bach / JS Bach wamo / WA Mozart ..etc...2
Second （米）棚上げする／（英）提議する: "Albums".
Fields:
AlbumID- 8 characters, text (始める，決める as 最初の／主要な 重要な) ComposerByCode- 4 characters, text AlbumName- 30 chars, text.
(Returning to the 転換: WA/ WG Mozart? 人物／姿／数字 it out? Hint: The G was for Gottlieb. Why two middle 指名するs?)
支援する to work! There's just one tricky bit in the way we've built the （米）棚上げする／（英）提議するs and how we'll use some fields.....
（米）棚上げする／（英）提議する 1 ("CompName") has the field 指名するd "CompNameID". In （米）棚上げする／（英）提議する 1, each 作曲家 appears only once and the values in the CompNameID field are be unique, i.e. no two 記録，記録的な／記録するs will ever have the same value in the CompNameID field. That field is the （米）棚上げする／（英）提議する's 最初の／主要な 重要な, so you will not be 許すd to enter the same value in that field in two 記録，記録的な／記録するs.
（米）棚上げする／（英）提議する 2 ("Albums") has the ComposerByCode field. This field should only ever have something in it which ALREADY appears in the first （米）棚上げする／（英）提議する's "CompNameID" field. I've given those fields different 指名するs in this example to make things easier, but in real databases, it would not be unusual for them to have the same 指名する. A shorthand for The "CompNameID" field", in the first （米）棚上げする／（英）提議する, i.e. in "CompNam", is: CompNam.CompNameID: The （米）棚上げする／（英）提議する's 指名する, a dot, the field's 指名する. いつかs you need to give the field 指名する in 十分な, but not often. It doesn't 事柄 if you do use the 十分な 指名する, so if in 疑問, use it!
As a 明確な／細部 example of something important, 公式文書，認める that in （米）棚上げする／（英）提議する 2, "wamo", say, can appear as many times as you like. (Remember, however, that it can appear only once in the first （米）棚上げする／（英）提議する.)
(By the way: The 権利 terminology for "The way we've built the （米）棚上げする／（英）提議するs" is "the database's schema". Two databases have the same schema if they have the same （米）棚上げする／（英）提議するs, and those （米）棚上げする／（英）提議するs have the same fields, and the corresponding fields all are all 始める，決める to 同一の types. Learn the 権利 条件 for things, and you'll make much better 進歩 with Google and 手動式の's 索引s!)
Second （米）棚上げする／（英）提議する 見本 data... don't enter it into the computer before you are told to...
Album ID/ 作曲家 / Album 指名する
bob1 / bach / Best of Johann Bach
bfc1 / bach / Bach Flute Concertos
mmot / wamo / Marvelous Mozart
mreq / wamo / Mozart Requiem
mvc / wamo / Violin Concertos by WA Mozart
... etc...
==============
So far so good? Now we come to a major part of the point of all this... a chance to 論証する a 関係.
Before you put any 見本 data in those （米）棚上げする／（英）提議するs, tell the database about a 関係 that you want 施行するd.
In the ooBase main 事業／計画（する） 経営者／支配人 window's menu, click "道具s", and from the sub-menu "関係s".
An empty "Relation Design" window should open. From its menu, "挿入する"/"追加する （米）棚上げする／（英）提議するs", and 追加する both the database's （米）棚上げする／（英）提議するs to the Relation Design window.
Create a line between CompName.CompNameID and Albums.ComposerByCode as follows. (It is 平易な and intuitive, but half way through it, it may seem it "isn't working".)
That should give you a line between the two fields, with a "1" at the CompName.CompNameID end and an "n" at the Albums.ComposerByCode end.
If you have trouble creating the 関係, it may be that you didn't notice my 警告 about not putting data in the （米）棚上げする／（英）提議するs yet. You can put data in the （米）棚上げする／（英）提議するs before setting up the 関係... but if there are data which break the 支配するs of the 関係, the "bad" data will 封鎖する the 創造 of the 関係. Go 支援する to the （米）棚上げする／（英）提議するs, edit out the problem data. Be sure to "commit" (save) the final data change, and try again to create the 関係. (You "commit" changes by moving the insertion point out of the 記録，記録的な／記録する you just altered.)
Be sure to SAVE the 関係. It doesn't need a filename, as it is saved "inside" the database, along with all the database's （米）棚上げする／（英）提議するs, etc. But do save it, by using the "disk" icon on the toolbar, or invoking the main 事業／計画（する） 経営者／支配人 window's "とじ込み／提出する | Save". If you try to の近くに the window without saving, the system will help you... but if you leave the window open, go off to the next thing without saving, the new 関係 will not yet be in 影響 across the database.
The "1" says that only one 記録，記録的な／記録する in this （米）棚上げする／（英）提議する can have a 明確な／細部 value in the CompNameID field. The "n" at the other end of the line says that many 記録，記録的な／記録するs in the Albums （米）棚上げする／（英）提議する can have the same value in the ComposerByCode field.
The "only one 記録，記録的な／記録する..." 支配する will be 施行するd by the database because CompName.CompNameID is a 最初の／主要な 重要な on the （米）棚上げする／（英）提議する.
Why have you gone to all that bother?
An 即座の 利益 of all that is that you cannot now enter a value in Albums.ComposerByCode unless that value appears in a 記録，記録的な／記録する in the CompName （米）棚上げする／（英）提議する.
This means that you have to do 入ること／参加（者）s in CompName before using a new 作曲家 in the Albums （米）棚上げする／（英）提議する... but this is a very small price to 支払う／賃金 for the "robustness" you have 追加するd to your database. You can still, say, enter "bach" when you should have entered wamo... but you cannot enter "bcah"... unless that's someone else's CompNameId. Good coding of your data can 減ずる the chance of such coincidences.
(There's more on 関係s and joins in a short(er) page I've done talking about these important 概念s in general 条件. They are not the same thing, but the differences 絶えず blur in my mind, and I hope to help you fight that problem.
==============
Now enter the 示唆するd 見本 data into your （米）棚上げする／（英）提議するs. You might want to 実験 with a few 審議する／熟考する mistakes, to see the 関係 保護するing you.
==============
Once you have 始める，決める up those （米）棚上げする／（英）提議するs and the 関係, you can make a query draw just the things you need from the two of them. I'll show you how in a moment.
As you learn more about relational databases you'll continue to learn about （米）棚上げする／（英）提議するs, queries, forms and 報告（する）／憶測s. It would be possible... not a good idea, as I hope I will explain for you... but possible to 始める，決める up a 選び出す／独身 （米）棚上げする／（英）提議する like...
Album ID / Album 指名する / 作曲家 bob1 / Best of Johann Bach / JS Bach bfc1 / Bach Flute Concertos / JS Bach mmot / Marvelous Mozart / WA Mozart
When you see something "long" and 柔軟な like "JS Bach" (it could be written like that, or "Johann Bach", "Bach, JS", "J.S. Bach", etc... 特に if the same value appears more than once, start thinking... "two （米）棚上げする／（英）提議するs".
That doesn't mean we can't pull something like the above out of our database. After all...
Album ID / Album 指名する / 作曲家 bob1 / Best of Johann Bach / bach bfc1 / Bach Flute Concertos / bach mmot / Marvelous Mozart / wamo
... isn't going to be very 満足な, is it? (Look at the last column. (And we can を取り引きする the first one, too, if we wish.)
The answer is to use a query to, in essence, 生成する a "（米）棚上げする／（英）提議する". It will be a （米）棚上げする／（英）提議する in most 尊敬（する）・点s... but will be a 一時的な （米）棚上げする／（英）提議する, a "scratch" （米）棚上げする／（英）提議する which will go almost as soon as it has been created. But not so quickly that we won't have a chance to use what the query has put into it. The 一時的な （米）棚上げする／（英）提議する can, for instance, and often is, used to fill the elements of a form. We'll see how, and why we would want that, その上の 負かす／撃墜する the page.
The form 陳列する，発揮するs what you need to know, 経由で a "hidden under the hood" 機械装置 which is a better way of 扱うing the data, in this 事例／患者, in particular, the 作曲家's 指名するs.
I 選び出す／独身d them out for special 扱うing because, without the special 扱うing, the 使用者 would have to enter the same thing over and over... the 作曲家's 指名する in 十分な. Admittedly, the 使用者 now has to enter the code for the 作曲家 over and over... but at least the code for the 作曲家 is shorter.
Also, if in the "Albums" （米）棚上げする／（英）提議する, you use the 作曲家's 指名する where I'm using my "code" inconsistencies would creep in: "JS Bach", "J.S. Bach", "Bach", etc. Computer-managed 職業s 栄える when inconsistencies are 除去するd.
Remember: This is just an illustration, so I would not 推定する／予想する that you would やむを得ず do this 職業 正確に／まさに this way.
===
So! How do we make the query and the form to 遂行する what I show in the example?
After you've created the two （米）棚上げする／（英）提議するs, the 関係, and put the 見本 data in the （米）棚上げする／（英）提議するs, go to the main ooBase 事業／計画（する） 管理／経営 window. Select "Queries" in the left 手渡す pane. Then click on "Create Query In Design 見解（をとる）" from the 仕事s pane. (You can also make this query with the Wizard, if you would rather... but I recommend, for most 仕事s, learning how to use the design window. いつかs the wizard is helpful for making a quick, rough start... いつかs it is more hinderance than help. You need to go to the design 道具 結局 anyway, for "tweaking" work.)
A small "追加する （米）棚上げする／（英）提議する To Query" dialog should pop up 名簿（に載せる）／表（にあげる）ing the 指名するs of the （米）棚上げする／（英）提議するs 利用できる. Select "Albums", click 追加する. Select "CompNam", click 追加する. And now you can の近くに the "追加する （米）棚上げする／（英）提議する To Query" dialog.
In the workspace of the Query Designer, you should now have a small box for each （米）棚上げする／（英）提議する, and in the box you should see the 指名するs of the （米）棚上げする／（英）提議する's fields. And the line 示すing the 関係 should be 現在の. That line is very 誤って導くing! It is not just 代表するing the 関係 which you 始める，決める up earlier. It comes from the 関係, it is true. But it is not "just" the 関係. More on this in a moment.
I WANT TO STRESS SOME THINGS.... Very すぐに after 存在 in the "はうing" 行う／開催する／段階 of using databases, you should start to find yourself making databases with more than one （米）棚上げする／（英）提議する. As soon as you do, you should find yourself using RELATIONSHIPS. (They are 述べるd at length どこかよそで in this tutorial, and discussed in others) SIMILAR BUT NOT THE SAME are "JOINS". You use joins when building queries (or 報告（する）／憶測s) 伴う／関わるing more than one （米）棚上げする／（英）提議する. I am a little new to joins myself, but am trying to build up the 構成要素 in these tutorials about what joins are, how you use them. If you see "joins": 支払う／賃金 attention. And remember that even though they are somewhat "connected" to realtionships, they are not the same as 関係s. Be careful when looking at a "think" to be 権利 about whether it is a 関係 or a join.
In the 底（に届く） of the Query Design window is something that looks a bit like a spreadsheet. The result of a query is always just another （米）棚上げする／（英）提議する: 無 or more lines, each a 記録，記録的な／記録する, each made up of fields.
The "spreadsheet" at the 底（に届く） of the Query Design window is where you 明示する what fields are going to be in the （米）棚上げする／（英）提議する that results from the query. Each column of the "spreadsheet" is about one of the fields. Each 列／漕ぐ／騒動 is one of the 所有物／資産／財産s of that field's 外見 in the result （米）棚上げする／（英）提議する. The field 指名するs go across the page, as they would in a （米）棚上げする／（英）提議する, but the 列／漕ぐ／騒動s below the 指名するs are not 記録，記録的な／記録するs in the database. Don't be fooled by the similarity between the two 陳列する，発揮するs.
The first 列／漕ぐ／騒動 明示するs what field is going to be in the result （米）棚上げする／（英）提議する. Use the pull 負かす／撃墜する to 始める，決める the "Field" 列／漕ぐ／騒動 of the first three columns to.....
Albums.AlbumID Albums.AlbumName CompNam.CompName
(As soon as you move away from the 独房 you are filling, the （米）棚上げする／（英）提議する 指名する will disappear. It would remain if any ambiguity 存在するd, e.g. if we had an Albums.CompID and a CompNam.CompID, which we might 井戸／弁護士席 have.)
That's pretty 井戸／弁護士席 all we need, but just to take care of a "frill": Fill in the 偽名，通称 列／漕ぐ／騒動 with....
"Album ID" and "Album 指名する" and "作曲家"
Those values will 決定する the 陳列する，発揮するd column headings.
Click とじ込み／提出する | Save (or use the button), and save the query as "ListAlbums"
You could 二塁打 click on the "ListAlbums" 入ること／参加（者） in the ooBase main 事業／計画（する） 管理／経営 window at this point, even before you の近くに the Query Designer. That "should" work. Long ago, I think that was behind some 衝突，墜落s I got. If you get 衝突，墜落s, try the "Run Query" button on the toolbar (green tick 示す). There are さまざまな advantages to doing so while getting the query "just so", anyway, and you may prefer that method of running the query anyway. (It was a long time ago that I got the 衝突，墜落s. Much work has been done on ooBase since. I'll be 利益／興味d to hear from you if you are getting 衝突，墜落s today... and are pretty sure you've done everything else 適切に!)
If you get every 記録，記録的な／記録する twice, look to see in the query designer whether you have the line between CompNam.CompNameID and Albums.ComposerByCode.
If it is not there, create it, rather like you were supposed to create the 関係, which was 類似の, but is not the same as the query 's "join". Here, the line... which was probably created automatically for you... 代表するs a join. Joins are important to queries.
One you have the line, signifying the join, you can 権利 click on it, select edit, and learn some things about your join. For now, do not tick the "natural" box. 公式文書，認める that the join is a "left join"... which is all you need to know about for the moment.
Once it is working 適切に, by all means invoke the query by 二塁打 clicking on the "ListAlbums" 入ること／参加（者） in the ooBase main 事業／計画（する） 管理／経営 window. Having the Query Designer window の近くにd may be part of the 衝突，墜落 avoidance 手続き.
So! That gives us a pretty good way to see the data in our （米）棚上げする／（英）提議するs in a human friendly way. However, for just a little more work, we can get an even better result.
の近くに the Query Designer. On the ooBase main 事業／計画（する） 管理／経営 window, in the left 手渡す pane ("Database"), select "報告（する）／憶測s". In the newly changed 仕事s pane, click on "Use Wizard to Create 報告（する）／憶測".
Step 1: Field 選択: Select "Query: ListAlbums
--- Use the >> button to move all of the fields in the query from the "利用できる fields" to the "Fields in 報告（する）／憶測" 覚え書きs. Click Next.
Step 2: Labeling. You can leave things as they are, so just click Next.
Step 3: 配合. You can leave things as they are, so just click Next.
Step 4: Sort 選択s: You can have the 報告（する）／憶測 sorted by 作曲家, or Album, or AlbumID... you choose! And then click Next.
Step 5: Layout. Again, you can leave things as they are, so just click Next. (You might want to 明示する "Portrait" layout.)
Step 6: Create 報告（する）／憶測. You can leave things as they are, so just click Finish.
You should get a special ooWriter 文書, with the （警察などへの）密告，告訴（状） you 推定する／予想する!
An aside: Just now, I didn't get what I hope you will. I got something の近くに, but with just one line, and that was pseudo-Latin gibberish. Why did this happen? I'm not sure. After a bit of "wiggling things", I DID get the 権利 result. Nothing extreme. I didn't 再開する Windows, or even ooBase. I went off and looked to see if a Java RTE was in place. (Main 事業／計画（する） 経営者／支配人 window menu "道具s"/"選択s"/"OpenOffice.org"/"Java" (1.7.0_07)). I tried doing a 報告（する）／憶測 on just a 選び出す／独身 （米）棚上げする／（英）提議する. That worked first time. Ran the query a few times. Worked 罰金. After both of those, I remade my 報告（する）／憶測- from- query again... and this time it worked. If anyone can 位置／汚点／見つけ出す why it DIDN'T work the first time, I'd be delighted to know. (The little "whoopsie" arose at the end of a long editing 開会／開廷／会期, and was distinctly unwelcome, I can tell you!) (The ooBase was in a 3.4.1 OO, recently 任命する／導入するd on a Windows 7 machine.)
いつかs the "stuff in Latin" result arises because although the 報告（する）／憶測 is "okay", there's some problem with the 関係 between the 報告（する）／憶測, and the data is it meant to be 現在のing. Maybe a field's 指名する was changed in the （米）棚上げする／（英）提議する's 鮮明度／定義 AFTER the 報告（する）／憶測 was 始める，決める up? Etc. It may be that if a database isn't "登録（する）d" you will get the "Latin" result. Not sure.
End of aside... getting 支援する to using our 報告（する）／憶測...
If you の近くに it, and go 支援する to the ooBase main 事業／計画（する） 管理／経営 window and 権利 click on the 報告（する）／憶測's 指名する, and select the "Edit" 選択, you'll open ooWriter again, but this time with the design of your 報告（する）／憶測 負担d. In that, you can adjust column widths and do all manner of things. Save it. の近くに it. Re-run the 報告（する）／憶測. Happy? You should be! Imagine doing a CD 在庫 事業／計画（する） for real, and 存在 able to 追加する/ 除去する/ edit 記録，記録的な／記録するs, and then re-print a neat, tidy, （疑いを）晴らす 名簿（に載せる）／表（にあげる） of the CDs in the collection so easily. Care to imagine doing the 職業 another way? (You can't, by the way, as far as I am aware, 追加する fields to the 報告（する）／憶測. Go 支援する. Re-do things from the start, if you want to make that sort of change to the 報告（する）／憶測.)
===================
The 報告（する）／憶測 Wizard is far from perfect, but it does do a reasonable 職業 of everyday things. However, don't wait long before starting to use the 報告（する）／憶測 建設業者. (Once called "the Sun 報告（する）／憶測 建設業者". No 疑問 a new 指名する this week. "Oracle 報告（する）／憶測 建設業者"? "Apache 報告（する）／憶測 建設業者"?) It is fabulous, by whatever 指名する. It is also the 推薦 of my "年上のs and betters". I've done an introduction to 任命する／導入するing and using it.
I hope the above has been useful......
結論するing the 転換: Gottlieb? Amadeus? Both say "beloved of God." One in Wolfie's native tongue, one in Latin, の近くに to the Italian, in which it is Amadeo, which, so I'm told, he also used in his most prolific correspondence. He even used a French form: Amédé! (That should be Amede with 激烈な／緊急の accents on the e's.) Italy was in vogue as a source of good music, culture, etc. (My thanks to an OpenOffice.Org 会議 関係者 who 訂正するd an 不確かの earlier 見解／翻訳／版 of this 転換!)
A 詳細（に述べる）: In our example, the 作曲家 code in the 作曲家s （米）棚上げする／（英）提議する was in the field of that （米）棚上げする／（英）提議する's 最初の／主要な 重要な. When you want to 協議する a （米）棚上げする／（英）提議する by a 関係 through something like the 作曲家 code, that datum will often be in the （米）棚上げする／（英）提議する's 最初の／主要な 重要な. If it isn't, I 嫌疑者，容疑者／疑う that the field may need to be 索引d... a story for another time!
===
Nota Bene: A 報告（する）／憶測 is for looking at your data. If you want to edit what is in the database, you use a form. どこかよそで, I 演説（する）／住所 setting up one form to work on data from 多重の （米）棚上げする／（英）提議するs.
I accidentally wrote another tutorial covering almost the same ground as the one you are reading now. The one you are reading is probably better, but consider reading the other, just to 二塁打 check your しっかり掴む of the 構成要素? It also ends わずかに 異なって.
In fact, I've written several tutorials with "関係s" (as in "relational database") at their 核心, and so have produced a sub-menu page for these 関係のある essays.
I dislike 'fancy' websites more 関心d with a flashy 外見 than for good content. For a pretty picture, I can go to an art gallery. Not everyone has 急速な／放蕩な broadband.
I 現在の this 構成要素 in a 判型 目的（とする）d at to helping you USE it. There are two 面s to that: The way it is 分裂（する） up, and the way it is 地位，任命するd. 詳細（に述べる）s at my page about how the 構成要素 is 分裂（する） up and how it is 地位，任命するd.
Please remember the 構成要素 is copyright. (TK Boyd, 2006 and later) The 手続きs in the page just 特記する／引用するd are 示唆するd only for convenient personal use of the 構成要素, however, also....
Feel 解放する／自由な to use this （警察などへの）密告，告訴（状） in computer courses, etc, but a credit of the source, 引用するing the URL, would be 高く評価する／（相場などが）上がるd. If you 簡単に copy the pages to other web pages you will do your readers a disservice: Your copies won't stay 現在の. Far better to link to the 初めの pages, and then your readers will see up-to-date 見解／翻訳／版s. For those who care- thank you. I have 地位，任命するd a page with more （警察などへの）密告，告訴（状） on what copyright 権利放棄s I 延長する, and suggestions for those who wish to put this 構成要素 on CDs, etc. (There is at least one 刑務所，拘置所 using the 構成要素 for inmate education. 状況／情勢s do 存在する where good internet 関係s are not possible!)
Translations are welcomed. Tell me about yours, so I can 地位，任命する links to it. (More （警察などへの）密告，告訴（状） at the page about copyright 権利放棄s.)
PLEASE >>> Click here to visit editor's Sheepdog ソフトウェア (tm) freeware, shareware pages <<< PLEASE
If you liked this ooBase tutorial, see the main 索引 for （警察などへの）密告，告訴（状） other help from the same author.
Editor's email 演説（する）／住所. Suggestions welcomed! - - - Want a 場所／位置 hosted, or email? I like 1&1's services.
Page 実験（する）d for 同意／服従 with INDUSTRY (not MS-only) 基準s, using the 解放する／自由な, 公然と accessible validator at validator.w3.orgMostly passes. There were two "unknown せいにするs" in Google+ button code. Sigh.
. . . . . P a g e . . . E n d s . . . . .