flash flv player code

1
2
3
4
5
6
7
8
9
10

<script type="text/javascript" src="http://web80s.net/jw_player/swfobject.js">
</script>
<div id="player2">beiguonvsheng.flv</div>
<script type="text/javascript">
var so = new SWFObject('http://www.web80s.net/jw_player/player.swf','mpl','470','320','9');
so.addParam('allowscriptaccess','always');
so.addParam('allowfullscreen','true');
so.addParam('flashvars','&file=http://zhipeng-zhang.com/temp/music/beiguonvsheng.flv');
so.write('player2');
</script>

]]> http://zhipeng-zhang.com/blog/?feed=rss2&p=346 http://zhipeng-zhang.com/blog/?p=321 http://zhipeng-zhang.com/blog/?p=321#comments Sat, 17 Jan 2009 11:43:21 +0000 admin http://zhipeng-zhang.com/blog/?p=321

Geisha pics

13 Photos

FirstGallery

23 Photos

xianjian4

8 Photos

fourth

12 Photos

Mobile phones and the Japanese, originally uploaded by Cocoarmani.

“Uchi” and “Soto” concept binds the Japanese at all time. In order to keep being in “uchi group” i.e. inner circle of your group, you have to keep your eyes on your mobile and text each other otherwise you are in danger of exclusion. It has been very well known that the Japanese text far lot faster and more often than the Europeans do. You will notice that the Japanese are very busy texting/e-mailing.
Now there is a question. Why on earth they do not ring each other instead? “Real voice” must be better, isn’t it? Or are they worried about their phone bills?
This can be explained that the Japanese fear that communication without non-verbal aspects is more easily misunderstood. Thus they feel safer to use loads of “smile”, “sorry”, “happy” etc. marks to add their “correct” facial expressions. These marks are called “e-moji” i.e. picture letterings”, which is particularly very well developed in this society. Thus text messages that tend to look very “dry” or “lack of emotion” on their own will “sound” and “look” friendlier with the e-moji. The receivers of the messages are then expected to use their full “imagination” and “empathy” to feel the senders’ intention and emotion when the texts were composed. It demands very hard work in sending and receiving texts in Japan. Texting in Japan is more than just sending information.

People who would like to further discuss the photo, please also compair this with:
www.flickr.com/photos/cocoarmani/2120868475/
It was taken in London.

Uploaded by Cocoarmani on 4 Sep 07, 7.12AM EST.

Japan: Girls eating noodles in lecture theatre, originally uploaded by Cocoarmani.

Japan: Girls eating noodles in lecture theatre
It was a culture shock for me to see this scene. The girls brought in hot noodles in soup and started eating in a lecture theatre and making this slurping noise just before a lecture started. I asked whether they minded me taking a photo and they did not, so there it is. As they are really nice girls who are very friendly, I enjoyed having a conversation with them. The older generations always get upset by seeing youths doing something that they conisder unsophisticated, but the innocence of these girls made me think that it is in a way immature of the older generation to conclude it unmannered.

I was fascinated to see Japanese university students keep on bringing in their lunches and drinks into the lecture theatre and eat before the lecture starts. There used be a boundary that people are not expected to bring things into the public area in Japan but it does not seem the case anymore. It is uncommon in the UK that students eat and drink even during the lectures as long as it is not in the middle of discussion, of course there is no slurping going on, so I was not offended to see this what so ever but I wonder since when this has been a common practice in Japan. If you know, please let me know.

Uploaded by Cocoarmani on 16 Nov 07, 7.32PM EST.

陈瑞 - 白狐我是一只爱了千年的狐
千年爱恋千年孤独
长夜里你可知我的红妆为谁补
红尘中你可知我的秀发为谁梳
我是一只守候千年的狐
千年守候千年无助
情到深处看我用美丽为你起舞
爱到痛时听我用歌声为你倾诉
寒窗苦读 你我海誓山盟铭心刻骨
金榜花烛 却是天涯漫漫陌路殊途
能不能让我为爱哭一哭
我还是千百年前爱你的白狐
多少春去春来，朝朝暮暮
生生世世都是你的狐
能不能让我为爱哭一哭
我还是千百年来不变的白狐
多少春去春来，朝朝暮暮
来生来世还做你的狐

Jane Eyre

http://dev.mysql.com/doc/refman/5.0/en/internationalization-localization.html

Chapter 9. Internationalization and Localization

Table of Contents

9.1. Character Set Support

9.1.1. Character Sets and Collations in General

9.1.2. Character Sets and Collations in MySQL

9.1.3. Specifying Character Sets and Collations

9.1.4. Connection Character Sets and Collations

9.1.5. Collation Issues

9.1.6. String Repertoire

9.1.7. Operations Affected by Character Set Support

9.1.8. Unicode Support

9.1.9. UTF-8 for Metadata

9.1.10. Column Character Set Conversion

9.1.11. Character Sets and Collations That MySQL Supports

9.2. The Character Set Used for Data and Sorting

9.2.1. Using the German Character Set

9.3. Setting the Error Message Language

9.4. Adding a New Character Set

9.5. The Character Definition Arrays

9.6. String Collating Support

9.7. Multi-Byte Character Support

9.8. Problems With Character Sets

9.9. MySQL Server Time Zone Support

9.10. MySQL Server Locale Support

This chapter covers issues of internationalization (MySQL’s capabilities for adapting to local use) and localization (selecting particular local conventions):

• MySQL support for character sets in SQL statements.
• How to configure the server to support different character sets.
• Selecting the language for error messages.
• How to set the server’s time zone and enable per-connection time zone support.
• Selecting the locale for day and month names

9.1.3. Specifying Character Sets and Collations

9.1.3.1. Server Character Set and Collation

9.1.3.2. Database Character Set and Collation

9.1.3.3. Table Character Set and Collation

9.1.3.4. Column Character Set and Collation

9.1.3.5. Character String Literal Character Set and Collation

9.1.3.6. National Character Set

9.1.3.7. Examples of Character Set and Collation Assignment

9.1.3.8. Compatibility with Other DBMSs

There are default settings for character sets and collations at four levels: server, database, table, and column. The description in the following sections may appear complex, but it has been found in practice that multiple-level defaulting leads to natural and obvious results.

CHARACTER SET is used in clauses that specify a character set. CHARSET may be used as a synonym for CHARACTER SET.

Character set issues affect not only data storage, but also communication between client programs and the MySQL server. If you want the client program to communicate with the server using a character set different from the default, you’ll need to indicate which one. For example, to use the utf8 Unicode character set, issue this statement after connecting to the server:

SET NAMES 'utf8';

For more information about character set-related issues in client/server communication, see Section 9.1.4, “Connection Character Sets and Collations”.

9.1.3.1. Server Character Set and Collation

MySQL Server has a server character set and a server collation. These can be set at server startup on the command line or in an option file and changed at runtime.

Initially, the server character set and collation depend on the options that you use when you start mysqld. You can use --character-set-server for the character set. Along with it, you can add --collation-server for the collation. If you don’t specify a character set, that is the same as saying --character-set-server=latin1. If you specify only a character set (for example, latin1) but not a collation, that is the same as saying --character-set-server=latin1 --collation-server=latin1_swedish_ci because latin1_swedish_ci is the default collation for latin1. Therefore, the following three commands all have the same effect:

shell> mysqld

shell> mysqld --character-set-server=latin1

shell> mysqld --character-set-server=latin1 \

           --collation-server=latin1_swedish_ci

One way to change the settings is by recompiling. If you want to change the default server character set and collation when building from sources, use: --with-charset and --with-collation as arguments for configure. For example:

shell> ./configure --with-charset=latin1

Or:

shell> ./configure --with-charset=latin1 \

           --with-collation=latin1_german1_ci

Both mysqld and configure verify that the character set/collation combination is valid. If not, each program displays an error message and terminates.

The server character set and collation are used as default values if the database character set and collation are not specified in CREATE DATABASE statements. They have no other purpose.

The current server character set and collation can be determined from the values of the character_set_server and collation_server system variables. These variables can be changed at runtime.

9.1.3.2. Database Character Set and Collation

Every database has a database character set and a database collation. The CREATE DATABASE and ALTER DATABASE statements have optional clauses for specifying the database character set and collation:

CREATE DATABASE db_name

    [[DEFAULT] CHARACTER SET charset_name]

    [[DEFAULT] COLLATE collation_name]ALTER DATABASE db_name

    [[DEFAULT] CHARACTER SET charset_name]

    [[DEFAULT] COLLATE collation_name]

The keyword SCHEMA can be used instead of DATABASE.

All database options are stored in a text file named db.opt that can be found in the database directory.

The CHARACTER SET and COLLATE clauses make it possible to create databases with different character sets and collations on the same MySQL server.

Example:

CREATE DATABASE db_name CHARACTER SET latin1 COLLATE latin1_swedish_ci;

MySQL chooses the database character set and database collation in the following manner:

• If both CHARACTER SET X and COLLATE Y were specified, then character set X and collation Y.
• If CHARACTER SET X was specified without COLLATE, then character set X and its default collation.
• If COLLATE Y was specified without CHARACTER SET, then the character set associated with Y and collation Y.
• Otherwise, the server character set and server collation.

The database character set and collation are used as default values if the table character set and collation are not specified in CREATE TABLE statements. The database character set also is used by LOAD DATA INFILE. The character set and collation have no other purposes.

The character set and collation for the default database can be determined from the values of the character_set_database and collation_database system variables. The server sets these variables whenever the default database changes. If there is no default database, the variables have the same value as the corresponding server-level system variables, character_set_server and collation_server.

9.1.3.3. Table Character Set and Collation

Every table has a table character set and a table collation. The CREATE TABLE and ALTER TABLE statements have optional clauses for specifying the table character set and collation:

CREATE TABLE tbl_name (column_list)
    [[DEFAULT] CHARACTER SET charset_name] [COLLATE collation_name]]

9.1.3.4. Column Character Set and Collation

Every “character” column (that is, a column of type CHAR, VARCHAR, or TEXT) has a column character set and a column collation. Column definition syntax has optional clauses for specifying the column character set and collation:

col_name {CHAR | VARCHAR | TEXT} (col_length) [CHARACTER SET charset_name] [COLLATE collation_name]Example:

CREATE TABLE Table1 ( column1 VARCHAR(5) CHARACTER SET latin1 COLLATE latin1_german1_ci );MySQL chooses the column character set and collation in the following manner:

• If both CHARACTER SET X and COLLATE Y were specified, then character set X and collation Y are used.
• If CHARACTER SET X was specified without COLLATE, then character set X and its default collation are used.
• If COLLATE Y was specified without CHARACTER SET, then the character set associated with Y and collation Y.
• Otherwise, the table character set and collation are used.

The CHARACTER SET and COLLATE clauses are standard SQL.

ALTER TABLE tbl_name
    [[DEFAULT] CHARACTER SET charset_name] [COLLATE collation_name]

Example:

CREATE TABLE t1 ( ... ) CHARACTER SET latin1 COLLATE latin1_danish_ci;

MySQL chooses the table character set and collation in the following manner:

• If both CHARACTER SET X and COLLATE Y were specified, then character set X and collation Y.
• If CHARACTER SET X was specified without COLLATE, then character set X and its default collation.
• If COLLATE Y was specified without CHARACTER SET, then the character set associated with Y and collation Y.
• Otherwise, the database character set and collation.

The table character set and collation are used as default values if the column character set and collation are not specified in individual column definitions. The table character set and collation are MySQL extensions; there are no such things in standard SQL.