「d dur」を含む日記 RSS

はてなキーワード: d durとは

2024-03-26

米津玄師がLemonのPVヒールの靴を履いている理由

Everyone been wondering why Yonezu (last name) Kenshi (first name) is wearing the heeled shoes. In one of his interviews he said that once he dreamed a funeral. Everyone was sad, but suddenly someone in the first line started to whistle loudly, in a way that annoyed the other people. They all started to say that he wasn't respecting the dead person because he wasn't being in silence for him, but Kenshi knew that the man whistling was communicating with the dead one. That was their own unique way to recognize each other. Maybe the others will think you're crazy or something negative, but it won't change the love that the whistling man has for his dead friend. Turns out that Kenshi got inspired by this dream so in the sing he wore heeled shoes, because he wants to let us know that he doesn't care what others say, it's his special way to express himself, because Kenshi was affected by High-functioning Autism which brought him to be smarter than the average, but he couldn't handle with social relationships, that's why he never had many friends since a young age and everyone made fun of him because of his character.

米津(姓)ケンシ(名)がなぜヒールの靴を履いているのか、誰もが不思議に思っていることだろう。

彼はあるインタビューで、葬式の夢を見たことがあると言っていた。みんな悲しんでいたのに、突然一列目の誰かが、他の人たちを困らせるような大きな口笛を吹き始めた。

彼らは皆、口笛を吹いているのは死者に敬意を払っていない、死者のために黙っているのではない、と言い始めた。それが彼ら独自認識方法だったのだ。

しかしたら、他の人からは頭がおかしいとか否定的見方をされるかもしれないが、口笛を吹いている男が死んだ友人を愛していることに変わりはない。

というのも、ケンシは高機能自閉症の影響を受けていて、平均よりも頭がいいのだが、社会的人間関係をうまくこなすことができなかった。

This made Kenshi very sad and from then on he started to hate himself because of his very uncommon name (in Japan there aren't many people that have Yonezu as last name and no one, but Yonezu Kenshi, is called Kenshi or the spelling is similar, plus it sounds like a stage name as well) he thought he was strange and weird, an uncommon person who shouldn't have existed (in fact in Japan there is a very strong will to follow the mass, which means if the greater part of girls have bangs, then the girls without bangs will try to have them or if they remain what they are, they might be isolated because different from the rest of the population). But Kenshi to make us, his fans, satisfied, he decided to collaborate with many people in the 2017 like the animators for MHA, DAOKO and Suda Masaki.

このことがケンシをとても悲しくさせ、それ以来ケンシは自分名前の珍しさ(日本では米津を名字に持つ人は少ないし、米津ケンシ以外はケンシと呼ばないし、スペルも似ていない、 存在しないはずの珍しい人(実際、日本では大衆に従おうとする意志が非常に強い。つまり、前髪のある女の子が多ければ、前髪のない女の子も前髪を作ろうとするし、前髪のないままだと、他の人とは違うという理由孤立するかもしれない)。しかし、ケンシは私たちファンを満足させるために、MHAのアニメーターDAOKO菅田将暉など、2017年活躍した多くの人々とのコラボレーションを決めた。

He changed during his musical career, like the time he was still Hachi (ハチ) and he felt somehow lost in all of his fame, so he made this song wearing heeled shoes and then the next song, Flamingo, is very different from Lemon because many people started to listen and to know him after Lemon, but he wanted to know what they would think if Kenshi changed the rhythm and the kind, turns out that many of them were attracted by Lemon and they didn't like Flamingo, but they still subbed to Kenshi's YouTube channel. Thank you for reading all of this, English isn't my mother language so I'm sorry for the mistakes and as always, have a nice day :D

彼は音楽活動の中で変わっていった。例えば、彼がまだハチだった頃、有名になることにどこか迷いを感じて、ヒールのある靴を履いてこの曲を作った、 というのも、多くの人がLemonの後にKenshiを聴き始め、知るようになったからだ。しかし、彼はKenshiがリズムや種類を変えたらどう思うかを知りたかった。英語母国語ではないので、間違いがあってごめんなさい。

Edit: You can find a video summary of Yonezu Kenshi's life and all of his interviews, it's in Mandarin tho. I hope you have a good translator to understand what he's saying.

米津建志の人生インタビューの要約ビデオを見ることができます。彼が何を言っているのか理解するために、良い翻訳者がいることを願う。

2023-11-15

Dehradun Call Girls | skokkacallgirl

Are you tired of searching all around Dehradun for attractive and alluring call girls? If so, you've come to the correct place. We provide the best hotel Dehradun Call Girls. Our housewives are attractive and beautiful. They'll enhance your day with even more unique touches. Therefore, if you'd like to spend time with someone who is so beautiful, you should employ our services. You can reserve our Dehradun call women whenever you want, from anywhere. Utilising our services is quite easy. To submit the form, simply fill it out and email it to the address provided. After submitting the form, an SMS containing a confirmation link will be sent to you.

Once you've clicked this link, complete the payment. Your booking info will be sent to your mobile device in a matter of minutes. Greetings from Skokka Call Girls, from Dehradun call girls. Strong bonds between couples are forged during meaningful and enjoyable sex encounters, which also help people transition smoothly through life. However, we want to eliminate stressful marriages, arguments about not having enough time for one another, pressure from the workplace or authority, and relationships that are under duress in this new setting. Relationship stress is causing men's personal lives to deteriorate daily. These days, finding a partner that fits your needs, tastes, and personality is challenging.

Very few people nowadays are lucky enough to have a thoughtful, kind, and compatible companion. People who are unhappy and don't value relationships are the ones looking for independent Dehradun call girls. Everyone is capable of and has an innate yearning for happy, fulfilling sexual experiences; they are not entitled to a life filled with tension, hopelessness, and a lack of love and pleasure.

Call Girls Chandigarh

Call Girls Amritsar

Call Girls Agra

Call Girls Ahmedabad

Call Girls Ajmer

Call Girls Ambala

Call Girls Aerocity

Call Girls Bangalore

Call Girls Chennai

Call Girls Coimbatore

Call Girls Delhi

Call Girls Dwarka

Call Girls Dehradun

Call Girls Goa

Call Girls Guwahati

Call Girls Gurgaon

Call Girls Ghaziabad

Call Girls Haridwar

Call Girls Hyderabad

Call Girls Faridabad

Call Girls Indore

Call Girls Jalandhar

Call Girls Jaipur

Call Girls Jaisalmer

Call Girls Jodhpur

Call Girls Kolkata

Call Girls Kharar

Call Girls Ludhiana

Call Girls Lucknow

Call Girls Mumbai

Call Girls Manali

Call Girls Mussoorie

Call Girls Mahipalpur

Call Girls Mohali

Call Girls Mysore

Call Girls Noida

Call Girls Nagpur

Call Girls Panchkula

Call Girls Patiala

Call Girls Patna

Call Girls Pune

Call Girls Rishikesh

Call Girls Rohini

Call Girls Surat

Call Girls Udaipur

Call Girls Varanasi

Call Girls Vadodara

Call Girls Zirakpur

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

backlink

2023-10-20

Refuting the “Israeli” Claims Regarding Evading their responsibility for the Massacre of the Gaza Baptist Hospital

Today, the “Israeli” Occupation Entity is trying to evade their responsibility for the crime of bombarding the “Baptist” Arab National Hospital in Gaza City, which the Israeli” Occupation Forces (IOF) committed on the evening of Tuesday, 17 October 2023. This heinous crime was committed against innocent Palestinian civilians while taking the hospital as a shelter from the flames of the “Israeli” brutal aggression, which left nowhere safe in the besieged enclave. It is necessary to affirm that, the Baptist Hospital belongs to the Anglican Episcopal Church in Jerusalem, and was built before the occupation of Palestine.

It is obvious that the “Israeli” enemy has been spreading lies since the very beginning of his destructive war on our people, when he with no single evidence claimed that the Palestinian resistance killed children, cut off heads and raped women. In continuation of this series of lies, they tried to evade their crime, attributing it to one of the resistance factions. Accordingly, we present some of the conclusive evidence to prove the “Israeli” Occupation Entity responsible for this heinous crime:

1) It is no secret that the IOF, several days ago, threatened several hospitals in the Gaza Strip, contacting each hospital separately and requesting their evacuation and holding the hospitals directors responsible for the consequences of neglecting the threats. In fact, there are dozens of clear statements from the IOF spokespersons in this regard.

2) Since the beginning of the ongoing aggression, the “Israeli” army has ignored the principle of distinguishing between civilian and military targets. Thus, the bombardment has systematically targeted emergency services, ambulances, civil defense facilities, schools, mosques, and churches.

3) The IOF contacted the directors of 21 hospitals in the Gaza Strip, especially those are located in the Gaza and the North of Gaza governorates, most notably: (Al-Awda, the Indonesian, Kamal Adwan, the Kuwaiti, Al-Quds, and Al-Mamadani), asking them to evacuate immediately, given that the hospitals are located within the geographical scope of “Israeli” military operations. In this regard, the official spokespersons for the IOF plus a number of hospital directors conducted interviews live on Al Jazeera, revealing the premeditated intention of the IOF to target hospitals in the Gaza Strip.

4) On 14 October, 2023, at 20:30, the IOF fired two shells towards the Baptist Hospital, and the next morning they called the hospital director, Dr. Maher الصفحة 2 من 3

Ayyad, saying to him: “We warned you last evening with two shells, so why have you not evacuated the hospital until this moment?!” Following that call, The hospital director contacted the bishop of the Evangelical Church in Britain and informed him of the incident, who in turn contacted international organizations before sending the hospital a message reassuring them that they could remain in the hospital. Yet with no warning, the IOF airstrikes returned, on Tuesday evening, to carry out the massacre against the hospital and the shelter-seekers of the displaced innocent Palestinian civilians.

5) Immediately after the massacre, the IOF spokesperson quickly published a statement on his page on the “X” and “Telegram” platforms at 21:17, which stated, “We had warned the evacuation of the Baptist Hospital and five other hospitals so that the Hamas terrorist organization would not take as a safe haven”. That statement is a clear claim of this massacre, and it is documented with a “screenshot” image attached to his page on Telegram, but he quickly deleted the post after seeing the massive scale of the massacre for the large number of victims, and the angry responses of the Arab, regional and international communities. Later on, he disavowed it, publish another

statement denying that he had issued the first statement.

6) Before and during the event, the resistance factions did not fire any missiles at the occupied territories, the “Israeli” sirens did not activate, and the Iron Dome missiles were not launched. Moreover, dozens of reconnaissance drones do not leave the sky of the Gaza Strip (365 km2 ), photographing and monitoring every inch around the clock. If the massacre was due to the resistance’s missiles, as the “Israeli” Occupation Entity falsely claim, why would not they show one picture their claims?!

7) The “Israeli” Occupation Entity claimed that this massacre was caused by a missile launched by the Islamic Jihad. However, we would wonder how they could identify and distinguish between the missiles of the resistance factions immediately after they were launched?!

8) The IOF military system documents and records all their operations by day, hour, minute and second, and in all previous times their media outlets came out to announce or deny much less severe massacres than this massacre, so what made them wait more than 4 hours before declaring their irresponsibility other than weaving scenarios of falsification, lies and deception?!

9) It is obviously known that the resistance’s missiles are somewhat “primitive” and do not have the destructive power that kills hundreds at one time. And throughout the history of previous confrontations and the current confrontation, no resistance missile has caused a tenth of this number of “Israeli” deaths.

10) The only video scene documenting the moment of the explosion reveals that the mass of flame and the sound of the explosion are identical to other “Israeli” bombs throughout the days of the ongoing aggression, which with no doubt proves that the “Israeli” origin of the missile.

الصفحة 3 من 3

The deliberate attack on hospitals is a war crime, stipulated in Article (8, 2, b, 9) of the Statute of the International Criminal Court. Accordingly, Hamas officially calls on the Prosecutor of the International Criminal Court to open an investigation into this crime, which falls within the framework of a genocidal war, in accordance with the provisions of Article 6 of the Basic Law. These bloody acts are also based on the policy of denial pursued by the “Israeli” Occupation Entity, as they deny the existence of the Palestinian people.

There is no doubt that impunity fuels crime, and investigating crimes is a way to protect people. Furthermore, if a legal and judicial response is necessary, it is above all that the response to this crime must be humanitarian and global. Such actions must shock the conscience of the world, or else there would no longer be a reliable international community if the “Israeli” Occupation government free to decide to bomb hospitals!

In conclusion, we are facing a genocidal massacre committed by IOF against children, women, and the elderly. The “Israeli” Occupation Entity is the only responsible for the crime, no matter how much they try to weave lies and fabrications to get away with it, as they always do.

The Islamic Resistance Movement

HAMAS-Palestine

Wednesday, 18 October 2023

本日ハマスpdf形式でテレグラムにアップしたやつの全文

ガザ・バプテスト病院虐殺責任回避に関するイスラエルの主張に反論する」

って題名

2023-06-02

日英エロゲ女性翻訳者による翻訳tipsおもしろ

https://twitter.com/merumeruchann/status/1663878494336458753?s=20

3. Choose your words wisely; AKA consider what is SEXY

"Wriggling" is a pretty standard translation of 藻掻く but in English it's associated with worms. WORMS! 🪱 "Undulating" is much nicer. e.g. A pussy doesn't wriggle, it undulates or ripples, or it convulses around his cock.

A woman doesn't wriggle her hips, she bucks them or she writhes. Your MC doesn't rock his hips he thrusts or pumps or rides. His hips aren't "moving on their own" he "can't control himself".

「もがく、身悶えする」はふつう"Wriggling"と訳されるが、これは虫を連想させるのでダメ。"Undulating"のほうがよい。

まんこがうねる」と言いたいときも、wriggleではなく、undulate や ripple

あるいは"it convulses around his cock."

同様に、女が尻をくねらせるとき wriggle her hips とは言わない。she bucks them or she writhesなどと言う。

男が腰を振るときrock his hipsではなくhe thrusts or pumps or rides

意識的に腰を振るのではなく自分コントロールできず振ってしまう感が大事

Sometimes a woman's skin may be described as 白魚. This is sexy in the original cultural and linguistic context. In many English-speaking cultures, fish are used for negative comparisons. Something like translucent or dewy would be an appropriate equivalent.

In JP a man going wild during sex is often likened to a monkey, but this has a more comical sound in English, where comparisons to simply a "wild animal" work better.

女の肌を「白魚」と形容することがあるが、英語では魚はネガティブ意味合いになってしま

translucent (透き通るような)やdew(つややかな)と言い換えると良い

また、激しいセックス最中、「猿のように」と形容することがあるが、英語ではコミカルに響いてしまうのでwild animal野生動物、獣)などと言いかえるとよい

Consider the virgin "He put his penis in her vagina" vs the chad "He slid his cock into her pussy".

These sentences describe the same action, but one says "I fuck" and the other says "I've only ever seen sex in the bio textbooks my model was trained on".

On the other hand, don't throw in porny words where there shouldn't be any; if your heroine is a shy virgin and the source text is using coy words like あそこ, don't have her shouting FUCK MY TIGHT LITTLE PUSSY in English.

挿入するシーンでは

"He put his penis in her vagina"

とするのではなく、

"He slid his cock into her pussy".

と訳すべき

後者は「ヤる」という感じだが、前者は「私はAIなので性行為については生物学教科書知識しかありません」みたいに聞こえてしま

とはいえヒロインシャイ処女で、「あそこ」と控えめに言っているのに”FUCK MY TIGHT LITTLE PUSSY”(私のキツキツオマンコを犯して!)などと絶叫させてはいけない

2023-02-19

打上げ成功/失敗のWikipedia定義

https://en.wikipedia.org/wiki/Comparison_of_orbital_launcher_families

Launches reaching...

Total: Flights which lift-off, or where the vehicle is destroyed during the terminal count

Note: only includes orbital launches (flights launched with the intention of reaching orbit). Suborbital tests launches are not included in this listing.

Space (regardless of outcome): Flights which reach approximately 100 km or more above Earth's surface.

Any orbit (regardless of outcome): Flights which achieve at least one complete orbit even if the orbit differs from the targeted orbit.

Target orbit (without damage to the payload)

この部分が、成功率比較するための項目と言って良いと思う。成功率のものはこの記事では述べていないが

成功率="Target orbit"÷"Total"

と見ればよい。

で、Total定義としては、「離陸するか、または最終カウントダウン中に破壊された数」。なお、衛星軌道への打ち上げのみをカウントし、弾道飛行テストカウントしない。

H3は今回、離陸も破壊もしなかったので、Totalは0のまま。

2021-01-06

anond:20210106141407

アジア圏では反社証明なので・・・で終わるし

反社証明じゃないもんな国でもこんなモンだが?

 

タトゥーだって軍人とかならばともかくそれ以外は教会悪口を言われた云々とかやってるし

クラブとか海ならなんも言わんだろうけどそれ以外は場所シチュエーション次第なんだが?

Tattoos, Piercings, and Credibility

Of the nearly 2,700 people we surveyed, 12% reported having a visible tattoo that can be seen by managers and co-workers during the workday. Only 3% reported having a visible body piercing (other than an earring).

The biggest takeaways from our survey include a whopping 76% of respondents feel tattoos and piercings hurt an applicant’s chances of being hired during a job interview. And more than one-third – 39% of those surveyed – believe employees with tattoos and piercings reflect poorly on their employers. Furthermore, 42% feel visible tattoos are always inappropriate at work, with 55% reporting the same thing about body piercings.

Fortunately, only 4% of those with tattoos and piercings report having faced actual discrimination because of their ink and body art.

 

刺青ピアス・信用度

調査対象となった約2,700人のうち、12%の人が、勤務中に上司や同僚に見られるようなタトゥーを入れていると報告しています

ピアスイヤリング以外)をつけていると答えたのはわずか3%でした。

調査から得られた最大の収穫は、回答者の76%が、タトゥーピアス面接採用に悪影響を与える可能性を感じているとのことです。

また、3分の1以上(調査対象者の39%)が、タトゥーピアスをしている従業員は、雇用主に悪い印象を与えると考えています

さらに、42%は、目に見えるタトゥーは常に職場では不適切だと感じており、55%はボディピアスについても同様のことを報告しています

幸いなことに、タトゥーピアスをしている人のうち、インクやボディアートが原因で実際に差別に直面したことがあると報告しているのは、

わずか4%に過ぎません。

 

Tattoos Hurt Your Chances of Getting a Job

https://www.salary.com/articles/tattoos-hurt-chances-getting-job/

 

お上記はカンザス州企業。でも保守的地域でなくともドレスコードで見えるところは禁止ってやってるとこ少なくないよ

最近は緩和されてきたみたいだが

ヨーロッパも同じ印象というか更に保守的イメージあるけどな

 

2020-10-22

anond:20201022143258 anond:20201103113726

海外日本以上にTPO異装に厳しぞ

タトゥーだって軍人とかならばともかくそれ以外は教会悪口を言われた云々とかやってるし

クラブとか海ならなんも言わんだろうけどそれ以外は場所シチュエーション次第なんだが?

Tattoos, Piercings, and Credibility

Of the nearly 2,700 people we surveyed, 12% reported having a visible tattoo that can be seen by managers and co-workers during the workday. Only 3% reported having a visible body piercing (other than an earring).

The biggest takeaways from our survey include a whopping 76% of respondents feel tattoos and piercings hurt an applicant’s chances of being hired during a job interview. And more than one-third – 39% of those surveyed – believe employees with tattoos and piercings reflect poorly on their employers. Furthermore, 42% feel visible tattoos are always inappropriate at work, with 55% reporting the same thing about body piercings.

Fortunately, only 4% of those with tattoos and piercings report having faced actual discrimination because of their ink and body art.

 

刺青ピアス・信用度

調査対象となった約2,700人のうち、12%の人が、勤務中に上司や同僚に見られるようなタトゥーを入れていると報告しています

ピアスイヤリング以外)をつけていると答えたのはわずか3%でした。

調査から得られた最大の収穫は、回答者の76%が、タトゥーピアス面接採用に悪影響を与える可能性を感じているとのことです。

また、3分の1以上(調査対象者の39%)が、タトゥーピアスをしている従業員は、雇用主に悪い印象を与えると考えています

さらに、42%は、目に見えるタトゥーは常に職場では不適切だと感じており、55%はボディピアスについても同様のことを報告しています

幸いなことに、タトゥーピアスをしている人のうち、インクやボディアートが原因で実際に差別に直面したことがあると報告しているのは、

わずか4%に過ぎません。

 

Tattoos Hurt Your Chances of Getting a Job

https://www.salary.com/articles/tattoos-hurt-chances-getting-job/

 

お上記はカンザス州企業。でも保守的地域でなくともドレスコードで見えるところは禁止ってやってるとこ少なくないよ

最近は緩和されてきたみたいだが

ヨーロッパも同じ印象というか更に保守的イメージあるけどな

2020-05-20

翻訳サービス比較

原文

The Tokugawa Shogunate was established by Tokugawa Ieyasu after victory at the Battle of Sekigahara, ending the civil wars of the Sengoku period following the collapse of the Ashikaga Shogunate. Ieyasu became the Shōgun and the Tokugawa clan governed Japan from Edo Castle in the eastern city of Edo (Tokyo) along with the daimyō lords of the samurai class. The Tokugawa Shogunate organized Japanese society under the strict Tokugawa class system and banned most foreigners under the isolationist policies of Sakoku to promote political stability. The Tokugawa and daimyō de facto administered Japan through their system of han (feudal domains) alongside the de jure Imperial provinces. The Tokugawa Shogunate saw rapid economic growth and urbanization in Japan which led to the rise of the merchant class and Ukiyo culture. The Tokugawa Shogunate declined during the Bakumatsu ("Opening of Japan") period from 1853 and was overthrown by supporters of the Imperial Court in the Meiji Restoration in 1868. The Empire of Japan was established under the Meiji government and Tokugawa loyalists continued to fight in the Boshin War until the defeat of the Republic of Ezo at the Battle of Hakodate in June 1869.

Google翻訳

徳川幕府は、関ヶ原の戦いでの勝利後に徳川家康によって設立され、足利幕府崩壊に続く戦国時代内戦を終わらせました。家康将軍になり、徳川藩は江戸の東の都市東京)にある江戸から武士大名領主とともに日本統治しました。徳川幕府は厳格な徳川階級制度の下で日本社会組織し、政治的安定を促進するために、サコクの孤立主義政策の下でほとんどの外国人禁止しました。徳川と大明の事実上日本は、ジュール帝国領土とともに、藩(藩)のシステムを通じて管理されました。徳川幕府は、日本の急速な経済成長都市化を見て、商人階級と浮世文化の台頭をもたらしました。幕末には幕末に幕を下ろし、明治維新により皇室の支持者たちにより打倒されました。明治政府のもと日本帝国樹立され、徳川忠誠は1869年6月函館の戦いでのエゾ共和国の敗北までのぼしん戦争

Excite翻訳

徳川幕府関ヶ原の戦い勝利の後に徳川家康により設立されて、足利幕府崩壊に続いている戦国時代内戦を終えた。家康は、サムライクラスのdaimyō君主とともに江戸東京)の東の都市江戸からShōgun徳川一族管理日本になった。徳川幕府は、厳密な徳川クラスシステムの下の日本社会組織し、政治的な安定性を促進するために、Sakokuの孤立主義方針の下のほとんどの外国人禁止した。徳川とdaimyō事実上は、正当な帝国地方そばのhan(封建制度ドメイン)のそれらのシステムを通して日本管理した。徳川幕府は、マーチャントのクラスとUkiyo文化の上昇に通じていた日本の急速な経済成長都市化を見た。徳川幕府は、Bakumatsu(「日本の冒頭」)期間の間に1853から傾き、1868年明治維新宮中サポーターにより倒された。大日本帝国は、1869年6月に忠臣が函館戦争でエゾウの共和国の失敗までボシン戦争において戦い続けた明治政府徳川の下で設立された。

DeepL翻訳

徳川幕府は、足利幕府崩壊に伴う戦国時代内乱終結させ、関ヶ原の戦い勝利した徳川家康によって成立しました。家康将軍となり、徳川家は江戸城を拠点武家大名とともに日本統治しました。徳川幕府は、厳格な徳川階級制度の下で日本社会組織し、佐国の鎖国政策の下で外国人入国禁止して政治の安定を図りました。徳川大名は、事実上日本行政を、事実上皇国と並んで藩制度で行っていた。徳川幕府は急速な経済成長都市化を遂げ、商人階級や浮世文化の台頭をもたらしました。徳川幕府1853年から幕末開国時代に衰退し、1868年明治維新朝廷の支持者によって倒されました。明治政府の下で大日本帝国樹立され、戊辰戦争では、1869年6月函館の戦いで蝦夷共和国が敗北するまで徳川家臣たちが戦い続けました。

みらい翻訳

関ヶ原の戦い勝利した徳川家康によって徳川幕府が成立し、足利幕府崩壊に伴う戦国時代内乱終結した。家康将軍となり、徳川氏は武家大名とともに江戸 (東京) 東部江戸から日本を治めた。徳川幕府は、政治の安定を図るため、厳格な徳川階級の下で日本社会組織し、鎖国政策の下ではほとんどの外国人禁止しました。徳川事実上大名は、日本を藩制(藩)で実質的支配した。日本徳川幕府による高度経済成長都市化が進み、町人階級や浮世文化が興った。1853年から幕末(「日本開国」)の間に徳川幕府は衰退し、1868年明治維新で勤皇志士たちによって倒され、明治政府のもとに大日本帝国が成立し、1869年6月箱館戦争蝦夷共和国が敗れるまで戊辰戦争を戦った。

2020-03-26

attracting commerce. Conditions on the island improved during the Taiping Rebellion in the 1850s, when many Chinese refugees, including wealthy merchants, fled mainland turbulence and settled in the colony.[16] Further tensions between the British and Qing over the opium trade escalated into

https://youtubecomhelp.zendesk.com/hc/pl/community/posts/360007743759-26-03-2020-Патриот-11-серия-канал-ТНТ-все-серии-сезона-от-26-марта-

https://youtubecomhelp.zendesk.com/hc/en/community/posts/360007743959--Отречение-25-серия-украина-ТРК-26-03-2020-в-хорошем-качестве-

https://youtubecomhelp.zendesk.com/hc/en/community/posts/360007744939--В-шаге-от-рая-17-серия-Россия-1-26-03-2020-качество-HD-от-26-марта-

https://youtubecomhelp.zendesk.com/hc/ru/community/posts/360007745060-26-03-2020-В-шаге-от-рая-17-серия-Россия-1-качество-HD-от-26-марта-

https://youtubecomhelp.zendesk.com/hc/ru/community/posts/360007745040--Заступники-5-серия-26-03-2020-смотреть-бесплатно-в-хорошем-качестве-от-26-марта-

https://youtubecomhelp.zendesk.com/hc/ru/community/posts/360007744019--Жизнь-после-жизни-10-серия-26-03-2020-последние-серии-смотреть-от-26-марта-

https://youtubecomhelp.zendesk.com/hc/ru/community/posts/360007745940-26-03-2020-Корни-12-серия-СТС-все-серии-сезона-от-26-марта

https://youtubecomhelp.zendesk.com/hc/pl/community/posts/360007744920-26-03-2020-Заступники-4-серия-последние-серии-смотреть-от-26-марта-

https://youtubecomhelp.zendesk.com/hc/pl/community/posts/360007745960-26-03-2020-В-шаге-от-рая-13-серия-Россия-1-все-серии-сезона-

ngkong until 1926, when the government officially adopted the two-word name.[40] Some corporations founded during the early colonial era still keep this name, including Hongkong Land, Hongkong Electric Company, Hongkong and Shanghai Hotels and the Hongkong and Shanghai Banking Corporation (HSBC).[41][42] History

https://youtubecomhelp.zendesk.com/hc/pl/community/posts/360007744139-26-03-2020-Последний-герой-Зрители-против-звезд-2-сезон-8-серия-все-серии-сезона-

https://youtubecomhelp.zendesk.com/hc/ru/community/posts/360007743779-26-03-2020-Отречение-21-серия-украина-ТРК-смотреть-в-хорошем-качестве-от-26-марта

https://youtubecomhelp.zendesk.com/hc/ru/community/posts/360007743859-26-03-2020-Любовь-на-выживание-9-серия-канал-пятница-смотреть-качество-HD-от-26-марта

https://youtubecomhelp.zendesk.com/hc/pl/community/posts/360007744980--Заступники-3-серия-26-03-2020-качество-HD-

https://youtubecomhelp.zendesk.com/hc/pl/community/posts/360007745200-26-03-2020-Холостяк-7-сезон-5-серия-тнт-смотреть-в-хорошем-качестве-

https://youtubecomhelp.zendesk.com/hc/pl/community/posts/360007744779-26-03-2020-Проспект-обороны-13-серия-на-канале-НТВ-смотреть-в-хорошем-качестве-от-26-марта-

https://youtubecomhelp.zendesk.com/hc/en/community/posts/360007743719-26-03-2020-Корни-13-серия-стс-в-хорошем-качестве-от-26-марта-

https://youtubecomhelp.zendesk.com/hc/en/community/posts/360007744959--Проспект-обороны-11-серия-НТВ-26-03-2020-онлайн-сериал-смотреть-от-26-марта-

https://youtubecomhelp.zendesk.com/hc/en/community/posts/360007746460--Доктор-Вера-13-серия-26-03-2020-смотреть-онлайн-в-хорошем-качестве-от-26-марта-

2018-05-25

anond:20180525141754

これやな

"I have spoken to South Korea and Japan and they are not only ready should foolish or reckless acts be taken by North Korea, but they are willing to shoulder much of the cost of any financial burden — any of the costs associated by the United States in operations, if such an unfortunate situation is forced upon us," he said during an event at which he signed a bill rolling back bank regulations.


韓国日本との話はついてる。北朝鮮がアホで無謀な行動をとった場合の準備ができているって言ってるし、それだけじゃなくて、カネの面でも負担する用意があると言ってる。もしもそういった不幸な事態が避けられない場合合衆国作戦行動に関連する費用の一切をもつって」

そんなん知らんがな。

2017-02-03

clang: warning: argument unused during compilation: '-e xport-dynamic'

久しぶりにvim更新たらこんなエラーが出たけどなんだこれ

2016-10-17

vimをtinyでmakeするとエラーが大量に出るんだが

インストール出来てるし起動もできてるから無視していいのかな

clang: warning: argument unused during compilation: '-I .'

clang: warning: argument unused during compilation: '-I proto'

clang: warning: argument unused during compilation: '-U _FORTIFY_SOURCE'

screen.c:1513:17: warning: self-comparison always evaluates to true [-Wtautological-compare]

if (curwin == curwin)

^

screen.c:5676:19: warning: self-comparison always evaluates to true [-Wtautological-compare]

&& Columns == Columns)

regexp.c:3790:24: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:3790:24: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:3790:24: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

regexp.c:4052:24: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:4052:24: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:4052:24: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

regexp.c:5276:25: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:5276:25: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:5276:25: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

regexp.c:5337:24: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

{ if ((rex.reg_match == ((void*)0))) *(&rex.reg_startpos[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.pos; else *(&rex.reg_startp[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.ptr; };

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:5337:24: note: remove extraneous parentheses around the comparison to silence this warning

{ if ((rex.reg_match == ((void*)0))) *(&rex.reg_startpos[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.pos; else *(&rex.reg_startp[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.ptr; };

~ ^ ~

regexp.c:5337:24: note: use '=' to turn this equality comparison into an assignment

{ if ((rex.reg_match == ((void*)0))) *(&rex.reg_startpos[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.pos; else *(&rex.reg_startp[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.ptr; };

^~

=

regexp.c:5355:24: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

{ if ((rex.reg_match == ((void*)0))) *(&rex.reg_endpos[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.pos; else *(&rex.reg_endp[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.ptr; };

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:5355:24: note: remove extraneous parentheses around the comparison to silence this warning

{ if ((rex.reg_match == ((void*)0))) *(&rex.reg_endpos[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.pos; else *(&rex.reg_endp[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.ptr; };

~ ^ ~

regexp.c:5355:24: note: use '=' to turn this equality comparison into an assignment

{ if ((rex.reg_match == ((void*)0))) *(&rex.reg_endpos[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.pos; else *(&rex.reg_endp[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.ptr; };

^~

=

regexp.c:5516:22: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:5516:22: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:5516:22: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

regexp.c:6213:21: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:6213:21: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:6213:21: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

regexp.c:6266:25: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:6266:25: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:6266:25: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

regexp.c:6294:25: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:6294:25: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:6294:25: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

regexp.c:6325:24: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:6325:24: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:6325:24: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

regexp.c:6341:24: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:6341:24: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:6341:24: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

regexp.c:6363:24: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:6363:24: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:6363:24: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

regexp.c:7711:25: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:7711:25: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:7711:25: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

regexp.c:7740:23: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:7740:23: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:7740:23: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

In file included from regexp.c:8043:

./regexp_nfa.c:3995:24: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:3995:24: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:3995:24: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

./regexp_nfa.c:4014:21: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:4014:21: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:4014:21: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

./regexp_nfa.c:4036:21: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:4036:21: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:4036:21: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

./regexp_nfa.c:4055:21: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:4055:21: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:4055:21: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

./regexp_nfa.c:4086:24: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:4086:24: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:4086:24: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

./regexp_nfa.c:4227:24: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:4227:24: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:4227:24: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

./regexp_nfa.c:4609:25: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:4609:25: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:4609:25: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

./regexp_nfa.c:4670:22: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:4670:22: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:4670:22: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

./regexp_nfa.c:4733:25: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:4733:25: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:4733:25: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

./regexp_nfa.c:4767:25: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:4767:25: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:4767:25: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

./regexp_nfa.c:4954:24: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:4954:24: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:4954:24: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

./regexp_nfa.c:5106:21: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:5106:21: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:5106:21: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

./regexp_nfa.c:5120:21: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:5120:21: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:5120:21: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

./regexp_nfa.c:5144:25: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:5144:25: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:5144:25: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

./regexp_nfa.c:5231:24: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:5231:24: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:5231:24: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

./regexp_nfa.c:5486:25: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:5486:25: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:5486:25: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

./regexp_nfa.c:5608:21: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:5608:21: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:5608:21: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

./regexp_nfa.c:5897:23: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:5897:23: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:5897:23: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

./regexp_nfa.c:5987:26: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:5987:26: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:5987:26: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

./regexp_nfa.c:6873:26: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:6873:26: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:6873:26: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

./regexp_nfa.c:6997:24: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:6997:24: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:6997:24: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

./regexp_nfa.c:7095:24: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:7095:24: note: remove extraneous parentheses around the comparison to silence this warning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:7095:24: note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

^~

=

2014-04-28

戦後韓国慰安婦制度の使用」に関する海外研究

韓国訪問したオバマが「慰安婦はとんでもない人権侵害だ」と発言した。

それに対して安倍総理は「筆舌に尽くしがたい思いをされた慰安婦の方々のことを思うと本当に胸が痛む思い」だとし、

「20世紀は女性を始め、多くの人権侵害された世紀であった。人権侵害が起こらない21世紀にするため、日本も大きな貢献をしたい」と述べた。

これはちょっと意外な発言で、日韓メディア右派左派ともにちょっと戸惑った感じがしたように思える。

安部首相の真意がどういうものなのか、これからの行動を見ないと分からないが、

これは、慰安婦に対する人権侵害を認めつつ、「慰安婦制度をやっていたのは日本だけでなかった」という文脈を作ろうとしているのかなと思えた。

それはオバマの発言に対して、「米軍慰安婦はどうなんだ」「朴正煕韓国軍慰安婦管理はどうなんだ」という反応が多く見られたものを反映していると思う。

20世紀」という一般化といい、正直なかなかうまい手というか、慰安婦問題に対して右左をなだめる、これまでにないスタンスになるかもと思った。

そうなってくると、戦後韓国慰安婦制度本当にあったのかという話になってくる。あったなら、慰安婦像海外に建てるキャンペーンが別の意味を持ってくる。

別にあいつらもやってから、俺らは悪くない」という意図ではなく、

実際問題として、日本謝罪もし、アジア女性基金設立した一方で、韓国自身が実は同じ問題を抱えていたのに黙殺するという事態は、事実を明らかにする上でも好ましくないと思う。

まとめサイトではソースあいまいものも含めてよく目にするが、いくら内輪で盛り上がっても意味は皆無で

海外でどのようにどのように研究されているか、というのが重要になると思う。

残念ながら、メディアという点では海外では概して「20万人の韓国人日本性奴隷にされた」「日本はその歴史を否定しようとしている」という文脈で報じられているのがほとんどだ。

しかし、アカデミズムの分野では、ここ最近韓国自身の慰安婦制度に目を向けられているものも増えているように見受けられる。

おおよそ中立的立場であると見受けられるC.Sarah Sohという研究者2009年出版された"The Comfort Women"という本は海外でも評判が高いようなので、色々調べようと思った。

http://www.goodreads.com/book/show/6068978-the-comfort-women

検索すると、Google Readersで一部内容が見ることができ、その部分にちょうど韓国慰安婦制度について記述しているところがあったので、メモ代わりに引用しておく。

もちろん、この本は、日本慰安婦制度、および人権侵害にも厳しい目を向けているが、

この部分の結論としては、韓国慰安婦生存者を日本の抵抗のシンボルとして英雄扱いする一方で、韓国自身の慰安婦制度含む性の人権侵害には目を向けてこなかったということを言っている。

韓国戦後慰安婦制度を使用してきた」という事実は、単なるネット右翼デマではなく、海外研究者にも裏付けられている事実であり、もっと注目されるべきではないかなと思う。

"The Comfort Women: Sexual Violence and Postcolonial Memory in Korea and Japan" by C.Sarah Soh

(p:211~)

After its liberation from Japanese rule in August 1945,the Korean Peninsula was divided into two: Soviet troops occupied the northern half and the US military the southern half. The ongoing US military presence in South Korea led to the formation and maintenance of “Camp towns” (kijich’on, in Korean) around the military bases, a development that has had a striking social impact on Korean communities. Kijich’on (literally, base or camp [kiji] village [ch’on]) refers to the civilian world of commercial establishments and residential buildings that have sprung up around the US military bases and cater to the needs of the American GI’s. It is “ a place where Koreans and Americans- mostly male military personnel- meet in an economic and emotional marriage of convenience”. As of the end of 1996, 37,000 American troops supported the economies of ninety-six kijich’on. The estimated number of kijich’on prostitutes over the first four decades of the American presence ranges between 250,000 and 300,000.

(中略)

The kijich'on sex trade consolidated and expanded during the second phase, which began with the Korean War. In her testimony, Pak Sun-i who had laboured at three different comfort startions in Japan 1944 to the end of the war, recalled:

"At twenty-seven years of age, I was having a hard time making ends meet in Tongduch'on (the largest kijich'on just outside Seoul). I ended up cohabiting with a staff sergeant of the USArmy for about two years... One of my friends from the days at a comfort station in Japan also worked as yang-gonju, but she passed away."

An American veteran who served in Korea in the 1950s after the end of the Korean War recounted that on Friday nights half-ton trucks would bring into the base a few hundred women to stay the night or the weekend with the soldiers. In 1958, five years after the armistice, the majority of about 300,000 prostitutes in Korea reportedly served American soldiers. Some of them, like their earlier Japanese counterparts(RAA), married and emigrated to the United States as wives of servicemen.

The fact that the Korean military also availed themselves of the "special comfort unit" during the Korean War has received little public attention even after the Korean women's movement in support of the "comfort women" began in the 1990s. Only piecemeal anecdotal materials on it had come to light from memoirs written by retired generals and generals and the testimony of soldiers who fought in the war.

(中略)

Characterizing the Korean military comfort system as an "unfortunate offspring" of the Japanese colonial legacy, Kim Kwi-ok called for victimized women, civic organizations, and scholars to come together and confront the unresolved issues of this historical injustice. The media reports of Kim's work, however, have generated little response. There has been no public outcry regarding the Korean military's use of "comfort women" during the Korean War or its violation of women's human rights. Korean silence over these issues is reminiscent of earlier societal indifference toward survivors of imperial Japan's comfort system, It mirrors the reticence of many Japanese to come to terms with the history of their country's wartime comfort system. As in the case of Japan, many in Korea, including retired military leaders, apparently regard the women's sexual labour simply as the performance of gendered customary sex labour in order to meet the needs of fighting men. It is noteworthy that military authorities have acknowledged that the system of special comfort units contradicts the national policy of banning licensed prostitution. Nonetheless, they have insisted that the special units were created to fulfill an important strategic end.

(中略)

(日本人韓国への売春ツアー、及び韓国人東南アジアへの売春ツアーは看過されてきたが、という話の後)

However, when it comes to the issue of Japan's wartime "comfort women" system, which has been redefined by the international community as a prominent case of violence against women in armed conflict, no social critic or public intellectual in Korea would dare to take the customary masculinist position that such a system benefits the economy or promotes national security. This is because the comfort women issue has been redefiend as military sexual slavery and a war crime by the international community owing largely to women's collaborative movement for redress in Japan and Korea.

Still, little critical public discourse has occurred on the legacies of that historical institution or the social structural dimension of Korea'S comfort women tragedy. Few are willing to consider the unsavoury fact that, accustomed to indigenous public institutions that have granted customary sex rights to men, and licensed by the colonial government, many Koreans did not hesitate to collaborate in recruiting and runing comfort stations by trafficking in girls and young women. Rather than deal with the messy and unpleasant complications of the historical record, Korean public discourse has simplistically elevated the survivors to heroic symbols of national suffering under Japanese colonialism and its imperialist war of aggression.

By contrast, Japan, which is unavoidably seen as the perpetrator nation, has been in turmoil over contested representations of the comfort women phenomenon and its responsibility in the matter. Meanwhile, the international - as well as domestic - trade in public sex prospers in capitalist economies of Japan and Korea despite endless incidents of criminal abuse of women so employed by both foreigners and compatriots. The social historical legacies of masculinist sexual culture and political economic realities in the two countries continue to help construct women'S sexual labour as stigmatized yet customary care labour for masculine "need".

2013-02-24

渋い

The publication in France of our book Impostures Intellectuelles [1] appears to have created a small storm in certain intellectual circles. According to Jon Henley in The Guardian, we have shown that ``modern French philosophy is a load of old tosh.''[2] According to Robert Maggiori in Libération, we are humourless scientistic pedants who correct grammatical errors in love letters.[3] We shall try to explain here why neither is the case.

Some commentators go farther, attacking not our arguments but our alleged motivations for writing the book. Julia Kristeva, writing in Le Nouvel Observateur, accuses us of spreading ``disinformation'' as part of an anti-French politico-economic campaign[4]; she was even quoted (we hope misquoted) by the Italian daily Corriere della Sera as saying that we should undergo psychiatric treatment.[5] Vincent Fleury and Yun Sun Limet, again in Libération, accuse us of seeking to divert research funds from the social to the natural sciences.[6] These defences are curious: for even if our motivations were indeed as ascribed (and they most certainly aren't), how would that affect the validity or invalidity of our arguments? We have the modest hope that calmer heads will soon prevail among both our supporters and our critics, so that the debate can focus on the substantive content of our book.

Which is what? The book grew out of the now-famous hoax in which one of us published, in the American cultural-studies journal Social Text, a parody article chock-full of nonsensical, but unfortunately authentic, quotes about physics and mathematics by prominent French and American intellectuals.[7] However, only a small fraction of the ``dossier'' discovered during Sokal's library research could be included in the parody. After showing this larger dossier to scientist and non-scientist friends, we became (slowly) convinced that it might be worth making it available to a wider audience. We wanted to explain, in non-technical terms, why the quotes are absurd or, in many cases, simply meaningless; and we wanted also to discuss the cultural circumstances that enabled these discourses to achieve such prominence and to remain, thus far, unexposed. Hence our book, the noise and the furore.

 
ログイン ユーザー登録
ようこそ ゲスト さん