毋忘五大訴求 公民抗命有理
—10‧20九龍遊行陳情書
(案件編號:DCCC 535/2020)
——————————————————
「毋忘初衷,活在愛和真實之中」
撐阿銘,即訂閱Patreon:
patreon.com/raphaelwong
—————————————————
胡法官雅文閣下:
2012年,我第一次站在法庭上承認違反「公安惡法」,述說對普選的盼望,批評公安惡法不義,並因公民抗命的緣故,甘心樂意接受刑罰。當年我說,如果小圈子選舉沒有被廢除,惡法沒有消失,我依然會一如故我,公民抗命,並且我相信將會有更多學生和市民加入這個行列。想不到時至今日,普選仍然遙遙無期,我亦再次被帶到法庭接受審判,但只是短短7年,已經有數十萬計的群眾公民抗命,反對暴政。今日,我承認違反「未經批准的政府」所訂立「未經批准的惡法」之下的「未經批准集結」罪,我不打算尋求法庭的憐憫,但請容許我佔用法庭些微時間陳情,讓法庭在判刑前有全面考慮。
暴力之濫觴
在整個反修例運動如火如荼之際,我正承擔另一宗公民抗命案件的刑責。雖然身在獄中,但仍然心繫手足。我在獄中電視機前見證6月9日、6月16日及8月18日三次百萬港人大遊行,幾多熱愛和平的港人冒天雨冒彈雨走上街頭,抗議不義惡法,今日關於10月20日的案件,亦是如此。可能有人會問,政府已在6月暫緩修例,更在9月正式撤回修例,我等仍然繼續示威,豈非無理取鬧?我相信法官閣下肯定聽過「遲來的正義並非正義」(Justice delayed is justice denied)這句格言。當過百萬群眾走上街頭,和平表達不滿的時候,林鄭政府沒有理睬,反而獨行獨斷,粗暴踐踏港人的意願,結果製造出後來連綿不絕的爭拗,甚至你死我活的對抗。經歷眾多衝突痛苦之後,所謂暫緩撤回,已經微不足道,我們只是更加清楚:沒有民主,就連基本人權都不會擁有!
在本案之中,雖然我們都沒有鼓動或作出暴力行為,但根據早前8‧18及10‧1兩宗案件,相信在控方及法庭眼中,案發當日的暴力事件仍然可以算在我們頭上,如此,我有必要問:如果香港有一個公平正義的普及選舉,人民可以在立法會直接否決他們不認可的法律,試問2019年的暴力衝突可以從何而來呢?如果我們眼見的暴力是如此十惡不赦,那麼我們又如何看待百萬人遊行後仍然堅持推行惡法的制度暴力呢?如果我們不能接受人民暴力反抗,那麼我們是否更加不能對更巨大更壓逼的制度暴力沈默不言?真正且經常發生的暴力,是漠視人民訴求的暴力,是踐踏人民意見的暴力,是剝奪人民表達權利的暴力。真正憎恨暴力,痛恨暴力的人,不可能一方面指摘暴力反抗,又容忍制度暴力。如果我需要承擔和平遊行引發出來的暴力事件的刑責,那麼誰應該承擔施政失敗所引發出來的社會騷亂的罪責呢?
社會之病根
對於法庭而言,可能2019年所發生的事情只是一場社會騷亂,務必追究違法者個人責任。然而,治亂治其本源,醫病醫其病根,我雖然公民抗命,刻意違法,控方把我帶上法庭,但我卻不應被理解為一個「犯罪個體」。2019年所發生的事情,並不是我一個人或我們這幾位被告可以促成,社會問題的癥結不是「犯罪份子」本身,而是「犯罪原因」。我明白「治亂世用重典」的道理,但如果「殺雞儆猴」是解決方法,就不會在2016年發生旺角騷亂及2017年上訴庭對示威者施以重刑後,2019年仍然會爆發出更大規模的暴力反抗。
如果不希望社會動亂,就必須正本清源,逐步落實「五大訴求」,從根本上改革,挽回民心。2019年反修例運動,其實只是2014年雨傘運動的延續而已,縱使法庭可能認為兩個運動皆是「一股歪風」所引起,但我必須澄清,兩個運動的核心就是追求民主普選,人民當家作主。在2019年11月24日區議會選舉這個最類近全民普選的選舉中,接近300萬人投票,民主派大勝,奪得17個區議會主導權,這就是整個反修例運動的民意,民意就是反對政府決策,反對制度暴力,反對推行惡法,不容爭辯,不辯自明。我們作為礦場裡的金絲雀,多次提醒政府撤回修法,並從根本上改革制度,而在10月20日的九龍遊行當然是反映民意的平台契機。如今,法庭對我們施加重刑,其實只不過是懲罰民意,將金絲雀困在鳥籠之內,甚至扼殺於鼓掌之中,窒礙表達自由。
堅持之重要
大運動過後的大鎮壓,使我們失去《蘋果日報》,失去教協,失去民陣,不少民主派領袖以及曾為運動付出的手足戰友都囚於獄中,不少曾經熱情投入運動的朋友亦因《國安法》的威脅轉為低調,新聞自由示威自由日漸萎縮,公民社會受到沈重打擊,我亦失去不少摯友,有感傷孤獨的時候,但我仍然相信,2019年香港人的信念,以及所展現人類的光輝持久未變。我不會忘記百萬人民冒雨捱熱抗拒暴政,抵制惡法,展現我們眾志成城;我不會忘記人潮紅海,讓道救護車,展現我們文明精神;我不會忘記年青志士直接行動反對苛政,捨身成仁,展現我們膽色勇氣;我不會忘記銀髮一族走上街頭保護年青人,展現我們彼此關懷;我不會忘記「五大訴求」,不會忘記2019年區議會選舉,展現我們有理有節。
法官閣下,我對於當日的所作所為,不感羞恥,毫無悔意。我能夠在出獄後與群眾同行一路,與戰友同繫一獄,實是莫大榮幸。若法治失去民主基石,將使法庭無奈地接受專制政權所訂立解釋的法律限制,隨時變成政治工具掃除異見,因此爭取民主普選,建設真正法治,追求公平正義,仍然是我的理想。在這條路上,如有必要,我仍然會公民抗命,正如終審法院海外非常任法官賀輔明(Lord Hoffmann)所言,發自良知的公民抗命有悠久及光榮的傳統,歷史將證明我們是正確的。我期望,曾與我一起遊行抗命的手足戰友要堅持信念,在艱難歲月裡毋忘初衷,活在愛和真實之中。
最後,如9年前一樣,我想借用美國民權領袖馬丁路德金牧師的一番話對我們的反對者說:「我們將以自己忍受苦難的能力,來較量你們製造苦難的能力。我們將用我們靈魂的力量,來抵禦你們物質的暴力。對我們做你們想做的事吧,我們仍然愛你們。我們不能憑良心服從你們不公正的法律,因為拒惡與為善一樣是道德責任。將我們送入監獄吧,我們仍然愛你們。」(We shall match your capacity to inflict suffering by our capacity to endure suffering. We shall meet your physical force with soul force. Do to us what you will, and we shall continue to love you. We cannot in all good conscience obey your unjust laws because noncooperation with evil is as much a moral obligation as is cooperation with good. Throw us in jail and we shall still love you.)
願慈愛的主耶穌賜我們平安,與我和我一家同在,與法官閣下同在,與香港人同在。沒有暴徒,只有暴政;五大訴求,缺一不可!願榮耀歸上帝,榮光歸人民!
第五被告
黃浩銘
二零二一年八月十九日
Lest we forget the five demands: civil disobedience is morally justified
- Statement on 10‧20 Kowloon Rally
(Case No.: DCCC 535/2020)
Your Honour Judge Woodcock
In 2012, I stood before the court and admitted to violating the "Public Security Evil Law". I expressed my hope for universal suffrage, criticized the evil law as unjust, and willingly accepted the penalty for civil disobedience. Back then, I said that if the small-circle election had not been abolished and the draconian law had not disappeared, I would still be as determined as I was, and I believe that more students and citizens would join this movement. Today, universal suffrage is still a long way off, and I have been brought before the court again for trial. But in just seven years, hundreds of thousands of people have already risen up in civil disobedience against tyranny. Today, I plead guilty to "unauthorised assembly" under an unapproved evil law enacted by an unauthorised government. I do not intend to seek the court's mercy, but please allow me to take up a little time in court to present my case so that the court can consider all aspects before sentencing me.
The roots of violence
At the time when the whole anti-extradition law movement was in full-swing, I was taking responsibility for another civil disobedience case. Although I was in prison, my heart was still with the people. I witnessed the three million-person rallies on 9 June, 16 June and 18 August on television in prison, when many peace-loving people took to the streets despite the rain and bullets, to protest against unjust laws. Some people may ask, "The Government has already suspended the legislative amendments in June and formally withdrew the bill in September, but we are still demonstrating, are we not being unreasonable?" I am sure your Honour has heard of the adage "Justice delayed is justice denied". When more than a million people took to the streets to express their discontent peacefully, the Lam administration ignored them and instead acted arbitrarily, brutally trampling on the wishes of the people of Hong Kong, resulting in endless arguments and even confrontations. After so many conflicts and painful experiences, the so-called moratorium is no longer meaningful. We only know better: without democracy, we cannot even have basic human rights!
In this case, although we did not instigate or commit acts of violence, I believe that in the eyes of the prosecution and the court, the violence on the day of the incident can still be counted against us, based on the August 18 and October 1 case. And now I must ask - If Hong Kong had a fair and just universal election, and the public could directly veto laws they did not approve of at the Legislative Council, then how could the violent clashes of 2019 have come about? If the violence we see is so heinous, how do we feel about the institutional violence that insists on the imposition of draconian laws even after millions of people have taken to the streets? If we cannot accept violent rebellion, how can we remain silent in the face of even greater and more oppressive institutional violence? The true and frequent violence is the kind of violence that ignores people's demands, that tramples on their opinions, that deprives them of their right to express themselves. People who truly hate violence and abhor it cannot accuse violent resistance on the one hand and tolerate institutional violence on the other. If I have to bear the criminal responsibility for the violence caused by the peaceful demonstration, then who should bear the criminal responsibility for the social unrest caused by failed administration?
The roots of society's problems
From a court's point of view, it may be that what happened in 2019 was just a series of social unrest, and that those who broke the law must be held personally accountable. What happened in 2019 was not something that I alone or the defendants could have made possible, and the crux of the social problem was not the 'criminals' but the 'causes of crime'. I understand the concept of " applying severe punishment to a troubled world", but if "decimation" was really the solution, there would not have been more violent rebellions in 2019 after the Mongkok "riot" in 2016 and the heavy sentences handed down to protesters by the Court of Appeal in 2017.
If we do not want social unrest, we must get to the root of the problem and implement the "five demands" step by step, so as to achieve fundamental reforms and win back the hearts of the people. 2019's anti-revision movement is indeed a continuation of 2014's Umbrella Movement, and even though the court may think that both movements are caused by a "perverse wind", I must clarify that the core of both movements is the pursuit of democracy and universal suffrage, and the people being the masters of their own house. In the District Council election on 24 November 2019, which is the closest thing to universal suffrage, nearly 3 million people voted, and the democratic camp won a huge victory, winning majority in 17 District Councils. As canaries in the monetary coal mine, we have repeatedly reminded the government to withdraw the extradition bill and fundamentally reform the system, and the march in Kowloon on 20 October was certainly an opportunity to reflect public opinion. Now, by imposing heavy penalties on us, the court is only punishing public opinion, trapping the canaries in a birdcage, or even stifling them in the palm of their hands, suffocating the freedom of expression.
The importance of persistence
As a result of the crackdown after the mass movement, we lost Apple Daily, the Hong Kong Professional Teachers' Union, and the Civil Human Rights Front. Many of our democratic leaders and comrades who had contributed to the movement were imprisoned, and many of our friends who had been passionately involved in the movement had been forced to lay low under the threat of the National Security Law. I still believe that the faith of Hong Kong people and the glory of humanity seen in 2019 will remain unchanged. I will never forget the millions of people who braved the rain and the heat to resist tyranny and evil laws, demonstrating our unity of purpose; I will never forget the crowds of people who gave way to ambulances, demonstrating our civility; I will never forget the young people who sacrificed their lives, demonstrating our courage and bravery; I will never forget the silver-haired who took to the streets to protect the youth, demonstrating our care for each other; I will never forget the "five demands" and the 2019 District Council election, demonstrating our rationality and decency.
Your Honour, I have nothing to be ashamed of and no remorse for what I did on that day. It is my great honour to be in prison with my comrades and to be able to walk with the public after my release. If the rule of law were to lose its democratic foundation, the courts would have no choice but to accept the legal restrictions set by the autocratic regime and become a political tool to eliminate dissent at any time. As Lord Hoffmann, a non-permanent overseas judge of the Court of Final Appeal, said, civil disobedience from the conscience has a long and honourable tradition, and history will prove us right. I hope that my comrades in arms who walked with me in protests will keep their faith and live in love and truth in the midst of this difficult time.
Finally, as I did nine years ago, I would like to say something to those who oppose us, borrowing the words of American civil rights leader Reverend Martin Luther King: "We shall match your capacity to inflict suffering by our capacity to endure suffering. We shall meet your physical force with soul force. Do to us what you will, and we shall continue to love you. We cannot in all good conscience obey your unjust laws because noncooperation with evil is as much a moral obligation as is cooperation with good. Throw us in jail and we shall still love you."
Peace be with me and my family, with Your Honour, and with the people of Hong Kong. There are no thugs, only tyranny; five demands, not one less! To god be the glory and to people be the glory!
The Fifth Defendant
Wong Ho Ming
19 August 2021
同時也有1部Youtube影片,追蹤數超過18萬的網紅SGD LOL - TOP,也在其Youtube影片中提到,背景音樂:影片片尾備註 ----------------------------------------------------------------------------------------------------------- Video Clip Sources: https://ww...
「it would be better用法」的推薦目錄:
- 關於it would be better用法 在 黃浩銘 Raphael Wong Facebook 的最佳解答
- 關於it would be better用法 在 Hapa Eikaiwa Facebook 的最佳貼文
- 關於it would be better用法 在 竹科大小事 Facebook 的精選貼文
- 關於it would be better用法 在 SGD LOL - TOP Youtube 的最讚貼文
- 關於it would be better用法 在 better and better用法的推薦與評價,FACEBOOK、YOUTUBE ... 的評價
- 關於it would be better用法 在 better and better用法的推薦與評價,FACEBOOK、YOUTUBE ... 的評價
- 關於it would be better用法 在 『be better off』是什麼意思? be... - 每日一句學英文- Daily ... 的評價
- 關於it would be better用法 在 GitHub - f/awesome-chatgpt-prompts 的評價
- 關於it would be better用法 在 YouTube Data API Overview - Google for Developers 的評價
it would be better用法 在 Hapa Eikaiwa Facebook 的最佳貼文
=================================
「Would」の活用法(総まとめ)
=================================
これまで私が生徒さんから最もよくされた質問の一つが「would」の使い方でしょう。wouldを用いた表現は本当に沢山あり、それら全てを説明するのは容易ではありません。そこで今回、過去の記事でも紹介した用法を含め、日常会話において基本となるwouldの用法を、4つの状況毎になるべく分かりやすくまとめてみました。長くなりますが、どうぞ最後まで読んでみて下さい。
~過去の話をする時~
--------------------------------------------------
1) I thought it would rain.
→「雨が降ると思っていました」
--------------------------------------------------
過去のある時点で、その先に起こることを予め予測や推測をしていたことを示す言い方です。例えば、「I thought it would rain so I brought an umbrella.(雨が降ると思っていたので、傘を持ってきました)」や「Since I was a kid, I knew I would become a teacher.(私は子供の時から先生になると分かっていました)」のように表現できます。
また、「He said he would _____.(彼が〜すると言っていました)」のように誰かが(過去に)言ったことを他の誰かに伝える状況でも使われます。ポイントは、誰かが何かをすると約束したり、何かをすると意思を述べたことを、他の誰かに伝える状況で用いるのが一般的です。例えば、「He said he would buy coffee for us.(彼は私たちにコーヒーを買うと言っていました。)」や「She said she would talk to him about that issue.(その問題について、彼女は彼に話すと言っていました)」という具合に使われます。
✔Wouldの後は動詞の原形がフォロー。
<例文>
When I met my wife 5 years ago, I knew I would marry her one day.
(5年前に妻と出会った当初から、私たちは結婚すると思っていました。)
I never thought this proposal would go through.
(この提案が通らないことは最初から分かっていました。)
She said she would come to the party.
(彼女はパーティーに来ると言っていました。)
--------------------------------------------------
2) She would not help me.
→「彼女は手伝ってくれようとしませんでした」
--------------------------------------------------
Wouldの後にnotを付け、否定文(Would not)にすることで「〜しようとしなかった」という意味になります。基本的に何かしらの依頼や申し出に対し、乗り気じゃない、協力的じゃない、積極的に応える意欲がない、などのニュアンスで断ったことを表します。例えば、親に何度も仕送りをして欲しいと頼んでるが、いっこうにしてくれない状況では「My parents would not send me money.(私の両親は、仕送りをしようとしてくれない)」と言うことができます。
また、人に限らずテレビやパソコン、車などの機能に対してもwould notを使うことができます。例えば、「今朝、車のエンジンがかかりませんでした」は「My car would not start this morning.」となります。
✔肯定文にしても「〜してくれた」とはならず、意味が変わってしまうので注意。「My parents would send me money」と言うと「両親が仕送りをしてくれた」とはならずに、「両親が(何度も)送金した」を意味する。詳しくは下記の3)の解説を参照。
<例文>
I asked him many times but he would not tell me what happened.
(彼に何回も聞きましたが、何が起こったのか教えてくれませんでした。)
My girlfriend is really upset with me. She would not talk to me.
(彼女は私に怒っていて口をきいてくれませんでした。)
I charged my phone but it would not turn on.
(携帯を充電したけど電源が入らなかった。)
--------------------------------------------------
3) In the summer, I would go camping with my friends.
→「夏によく友達とキャンピングに行っていました」
--------------------------------------------------
過去によくやっていた行動パターンや習慣を表す際にもwouldが使われ、used to(よく~したものだ)と似たような役割を果たします。しかし、used toの場合は、習慣となっている行動がより高頻度なもので、且つ“今はもうしていない”ということを強調するニュアンスがあるのに対し、wouldの場合は、習慣となっていた行動頻度が週1回であろうと年1回であろうと、その頻度には関係なく「よく〜した」ということが話の趣旨となります。例えば、「When I was a kid, my grandmother would bake cookies.(子供の頃、私の祖母はよくクッキーを焼いてくれていました)」と言うと、クッキーを作る頻度ではなく、祖母がクッキーを作ってくれていたことが要点になります。それに対し、「私は高校生の頃、毎日サッカーの練習をしていました」と言いたいのであれば、used toを使って、「I used to practice soccer every day in high school.」と言うのが適切です。“毎日練習していた”ことが強調され、且つ“今はもう練習をしていない”ことが相手に伝わります。
✔過去の“状態”を表す場合はwouldではなくused toを使う。例えば「過去にオートバイを持っていました」は「I used to have a motorocycle.」と言い、「I would have a motorcycle」とは言わない。
<例文>
When I lived in Japan, I would go out drinking almost every week.
(日本に住んでいた頃、ほぼ毎週飲みに行っていました。)
Sometimes she would come over and cook Mexican food for us.
(時々、彼女はうちにきてメキシカン料理を作ってくれました。)
During the winter, I would get together with my friends and do a nabe party.
(冬に友達とよく鍋パーティーをしていました。)
~仮定の話をする時~
--------------------------------------------------
1) If I won the lottery I would buy a house.
→「もし宝くじが当たったら家を買います」
架空の話や実際には起こり得ない出来事について話す時にもwouldを使います。一般的に「If _____, I would _____.(〜だったら〜する)」の形式で表現します。例えば、「世界中のどこにでも住めるとしたら、ハワイに住みます」は「If I could live anywhere in the world, I would live in Hawaii.」と言います。
✔文末に「if I knew」に付け足してもOK。
<例文>
If you could date a celebrity, who would it be?
(もし、芸能人と付き合えるとしたら、誰と付き合う?)
I would tell you where she was if I knew.
(彼女がどこにいるか知っていたら教えているよ。)
If I found a hundred dollars on the ground, I would take it to the police station.
(もし100ドルを拾ったら交番に届けます。)
--------------------------------------------------
2) Would you try online dating?
→「あなただったら出会い系サイトを試してみますか?」
--------------------------------------------------
相手に“もしも”の質問を投げかける時は「Would you _____?」と表現するのが定番で「あなただったら〜しますか?」を意味します。相手の意見やアドバイスを尋ねる場合は「What would you _____?」と表現します。例えば、「あなただったらどうしますか?」と聞くなら「What would you do?」、販売員に「あなただったら何をお勧めしますか?」と尋ねるなら「What would you recommend?」となります。
<例文>
Would you date someone older than you?
(あなただったら年上の人とお付き合いしますか?)
What would you do? Would you apologize?
(あなただったらどうしますか?謝りますか?)
Would you be open to living abroad?
(あなただったら外国に住むのはありですか?)
--------------------------------------------------
3) If I were you I would apologize.
→「私だったら謝ります」
--------------------------------------------------
「私だったら〜する」と相手の立場になって何かしらのアドバイスや提案をする場合に使われる表現です。shouldを使った表現よりも控えめに助言したい場合にピッタリの言い回しです。例えば、東京で給料の良い仕事のオファーが入ったが、家族の不幸で地元に引っ越さないといけなくなってしまったと友達に相談され、「私だったら仕事のオファーを断るかな」と言うなら「If I were you I would turn down the offer.」となります。
✔日常会話では「If I were you」を省いて、「I would _____」と直接言うことも一般的。
✔「If I were in your shoes, I would ______.(私があなたの立場だったら、〜をします」という言い方もある。
<例文>
If I were you I wouldn't go.
(私だったら行かないね。)
This milk expired 5 days ago. I wouldn't drink that if I were you.
(この牛乳の消費期限、5日前じゃん。私だったら飲まないよ。)
I would call them and ask for a refund.
(私だったら電話して返金を求めるけど。)
~丁寧・控えめな発言をする時~
--------------------------------------------------
1) Would you turn down the volume?
→「音量を下げてくれますか?」
--------------------------------------------------
人に何かをリクエストや依頼をする際に「Can you _____?(〜してくれる?)」よりも丁寧にお願いする場合は「Would you _____?(〜してくれますか?)」と表現します。例えば、「この用紙に記入してくれますか?」と丁寧に言いたいなら「Would you fill out this form?」になります。
✔より丁寧な言い方が「Would you mind _____?(〜してくれますか?)」。相手に気を使ったとても優しい質問の仕方。
<例文>
Would you close that window?
(あの窓を閉めてもらえますか?)
Would you be able to help?
(手伝っていただけないでしょうか?)
Would you mind changing seats?
(席を変わっていただけませんか?)
--------------------------------------------------
2) Would you like a drink?
→「お飲物はいかがですか?」
--------------------------------------------------
相手に「〜はいかがですか?」と何かを丁寧にオファーする際にピッタリの表現が「Would you like _____?」です。顧客や年上の人、または面識のない人に対して何かオファーする場合は、この表現を使うのが最も無難でしょう。例えば、会社に訪れた顧客に「熱いお茶はいかがですか?」と聞く場合は「Would you like some hot tea?」と言います。
✔友達や家族など、仲の良い人に対してこの表現はちょっと丁寧過ぎる。親しい関係であれば「Do you want _____?」でOK。
<例文>
Would you like a refill?
(飲み物のお代わりはいかがですか?)
Would you like to join us?
(よかったら一緒にどうですか?)
Would you like me to drive?
(私が運転しましょうか?)
--------------------------------------------------
3) I would say _____.
→「〜だと思う」
--------------------------------------------------
この言い方は自分の意見を述べたり何かを推定する時に使われ「〜だと思う」や「恐らく〜だろう」「〜かな」などに相当する表現です。ハッキリと言い切る感じではなく、物腰柔らかく控えめに発言している印象があります。例えば、「彼女、何歳だと思いますか?」と聞かれた際、相手に失礼ないよう謙虚に意見を述べる場合、「I’d say early thirties. Maybe 32.(30代前半だと思う。32歳くらいかな)」という具合に使います。
✔日常会話では「I would say」を「I’d say」と省略して言うことが多い。
✔大抵の場合、「I think」の代わりに「I’d say」が使える。「I think」よりも控えめな響き。
✔必ず答えが求めらるような質問をされた際、決定的な発言や返答を和らげる言い方として「I would have to say _____(〜と言わざるを得ない)」がある。
<例文>
I'd say it's a four to five hour drive.
(車で4時間から5時間くらいかかるかな。)
I'd say this logo looks the best. I like the color and simplicity.
(私はこのロゴが一番だと思います。色とシンプルさがいいと思います。)
Both speeches were excellent but I would have to say Adam's speech was better.
(二人ともスピーチは素晴らしかったですが、私はアダムのスピーチの方が良かったと思います。)
~自分の願望を述べる時~
--------------------------------------------------
1) I would love to go.
→「是非行きたいです」
--------------------------------------------------
「I would love to」は「I want to」と似た意味で「〜を(が)したい」といった強い願望を伝える時に使われれます。「I want to」の気持ちをより強調した言い方です。例えば、同僚に食事を一緒にしないかと誘われた際、「I would love to join you guys for dinner.」と言います。
✔相手の誘いを快く受け入れるときに使われる定番フレーズが「I’d love to!(喜んで!)」
✔その他、相手の誘いを丁寧に断るときに使われる決まり文句でもあり、「I’d love to ____ but _____(〜したいのは山々なのですが、〜)」が定番フレーズになる。
<例文>
I would love to meet with you next week.
(是非、来週お会いしたいと思います。)
I'd love to! What time should I be there?
(喜んで!何時に行けばいいですか?)
I'd love to stay and chat some more but I have to get going.
(残ってもっとお話をしたいのですが、そろそろ行かないといけません。)
--------------------------------------------------
2) I would like to think that ____.
→「〜であると考えたい」
--------------------------------------------------
この表現は「真相はわからないけど、そうであって欲しい・・・」のようなニュアンスとして使われます。例えば、Facebookの個人情報の取り扱いに対し、多少の疑いはあるものの情報はしっかり保護されていると信じたいといった気持ちを表す場合は「I would like to think that Facebook protects our personal information.」となります。また、自分の発言や意見を物腰柔らかく控えめなニュアンスにする役割もあります。例えば、「あなたは良い父親だと思いますか?」という質問に対し「I would like to think I’m a good father.」と答えると、「私は良い父親であると考えたいのですが・・・」といった具合に謙虚な響きになります。
✔日常会話では「I would」を「I'd」と短縮して言うことが多い。
✔「そうだと思いたい」は「I would like to think so.」
<例文>
I would like to think that hard work pays off.
(努力は報われると信じたいです。)
I would like to think professional athletes don't use drugs.
(プロスポーツ選手は、薬物を使用していないと信じたい。)
I would like to think my English is getting better.
(自分の英語力が上達してるって思いたいや〜ん。)
~~~~~~~~~~~~~~~~~~~
無料メルマガ『1日1フレーズ!生英語』配信中!
通勤・通学などのちょとした合間を利用して英語が学べるメルマガ『1日1フレーズ!生英語』を平日の毎朝6時に配信中!ただ単にフレーズを紹介しているだけではなく、音声を使った学習プロセスが組み込まれているので、メルマガを読むこと自体が学習方法!
https://hapaeikaiwa.com/mailmagazine/
~~~~~~~~~~~~~~~~~~~
it would be better用法 在 竹科大小事 Facebook 的精選貼文
好貨來了! 轉給要考試或要用到英文的人吧!-
如何短期內學好英文: 掌握文法要點用在讀到或聽到英文
筆者長期接待外賓,整理下面的文法要點,切記要多看電視的英文節目,每天看,看的時候嘴巴跟著唸,一年後就會有很顯著的效果。
英文法總整理:
About Sentences
1. 一個句子只能有一個動詞(兩個動詞在一起會打架), 當主詞和受詞的一定是名詞(或做名詞用) , 一定要形容詞或名詞才能當補語(補充語意)
2. 助動詞和 be 動詞的否定在後面直接加 not 即可
3. 有疑問詞的問句,疑問詞要擺最前面, 有助動詞和 be 動詞的疑問句,要把助動詞或 be 動詞移到主詞前
4. 用什麼助動詞問,就用什麼助動詞回答, 一般動詞的否定和疑問要用助動詞
5. 祈使句要用動詞原形, 祈使句的否定在前面加 Don't 或 never
6. 間接問句不是問句,如: I know what it is. what it is不是問句,是一個名詞子句,或想成一個大名詞組。
7. 關係子句多半是形容詞子句,形容前面的先行詞,如: I see a man who lives there.
11. 某處有某物要用“There is(are) ...”的句型
12.整句當名詞: 名詞子句 I think he is a nice man. (he is a nice man相當於it 這件事)
About Nouns.
1. 一個名詞在句中當主詞或受詞或補語
2. 普通名詞前面要有冠詞,要不然就是後面要加 -s 或 -es
3. 有特指的名詞前面要有定冠詞 the (特定或特指)/相對a或 an 用在沒有特指的東西上
4. 人稱代名詞的用法要熟悉,如: I my me mine 其中my 具形容詞特性。
About Verbs.
0. 動詞的種類包括: be (am is are, was were, been, be) has (has have had) do (does do did) 一般動詞 go, cut, walk ...
1. 及物動詞後一定要有受詞,不及物動詞後不能接受詞
2. 不完全的(及物和不及物)動詞後面,一定有補語
3. 助動詞後用原形動詞 Did he come here?
4. 連綴動詞後面要用形容詞 She looks beautiful.
5. 主詞第三人稱單數,現在式一般動詞要加 +s 或 +es -y+ies
6. 過去完成式要有過去式引導 He had come here since yesterday.
7. if 句型: if 子跟主要子句是相對應的,如:
A. if 現在式, 主要子句現在式或未來式
B. if 過去, 主要would have +過去分詞
C.if 過去完成 (would have pp), 主要子句 過去完成 (would have pp)
8. 使役動詞後面用原形動詞(受詞主動去做某事時) He makes her cry. 或,
使役動詞後面用過去分詞(受詞被....時) He makes it done.
9. 感官動詞後面用原形動詞或現在分詞(受詞主動去做某事時) He sees her go.
使役動詞後面用過去分詞(受詞具有被動語意)
About Adjectives.
1. 形容詞形容名詞
2. 形容詞如果只有一個字,放在名詞前面,顏色大小好壞..有順序性 a red good pen
3. 動詞的過去分詞可當形容詞用(放名詞後倒修飾名詞) He read a book written by Mr. Wang.
4. 所有格後面要 + 名詞 所有格+名詞可以用所有格代名詞來代替 my book=mine.
5. 現在分詞有主動和進行中的意思,過去分詞則有被動和已經完成的意思
6. 冠詞、指示性形容詞、所有格不能同時形容一名詞
7. a friend of mine = one of my friends
8. 定冠詞加形容詞等於那一類名詞的複數 the public = people
9. 形容詞的原級、比較級、最高級規律和不規律的變化要記得good//better//the best
About Adverbs.
1. 副詞修飾動詞、或形容詞或其他副詞
2. 頻率副詞的位置: be 動詞後、一般動詞前、助動詞和本動詞之間
About Prepositions.
1. 介系詞+名詞 形成介系詞片語 當 副詞片語用 修飾動詞 或 整句
2. 介系詞後面動詞要加 -ing,介系詞後面要加什麼樣的名詞是固定的 要背起來
About Conjunctions.
1. 對等連接詞連接的一定是兩個對等的東西 He and she are students.
2. 兩個句子不能用「,」連接
#學好英文的方法
#英文文法總整理
#快速學好英文
it would be better用法 在 SGD LOL - TOP Youtube 的最讚貼文
背景音樂:影片片尾備註
-----------------------------------------------------------------------------------------------------------
Video Clip Sources:
https://www.reddit.com/r/leagueoflegends/
https://medal.tv/league-of-legends
Fan contribution
music Sources:
youtube.com/user/NoCopyrightSounds
youtube.com/user/MonstercatMedia
youtube.com/user/freemusicwave
-----------------------------------------------------------------------------------------------------------
感謝你的觀看,歡迎分享,也可以訂閱我,隨時追蹤最新影片
剪輯好笑的每周VOD精華及噴笑嗑藥台式翻譯
希望能讓精華更有趣 翻譯並非正統可能有錯或超譯 請見諒
我們也經常剪輯英雄聯盟搞笑爆笑,技術,中文翻譯,實況主選手等的影片,也可以在下方留言,讓我幫你剪輯介紹給大家認識。
諮詢信箱:sgdlolhigh69@gmail.com
投稿信箱:sgdlolhigh69@gmail.com(絕地求生暫時停止投稿,僅接受英雄聯盟)
-----------------------------------------------------------------------------------------------------------
Video and music has the player's permission to feature their clip .was shared by the owner and allowed for use or we purchased.
-----------------------------------------------------------------------------------------------------------
COPYRIGHT ISSUES:
We make these videos with the intention of educating LoL players how to increase and improve own skills for better playing in some segments of the game, but to share those in quality compilation with other people.
One of our videos was shared by the owner and allowed for use or we purchased. These videos are made as a montage, consist of fragments from several different LoL matches. The content displayed in the video is recorded within the game, If any owner of clips, used in our compilation, has a copyright issue, feel free to contact us by gmail . We will remove the clip, video or come to an agreement. Thank you.
Using or sharing our compilations is allowed, so feel free to share it anywhere, but it would be nice, to use direct link of video, not of copies.
Thanks !
it would be better用法 在 GitHub - f/awesome-chatgpt-prompts 的推薦與評價
This repo includes ChatGPT prompt curation to use ChatGPT better. ... If it's adults then history-based tales might engage them better etc. ... <看更多>
it would be better用法 在 YouTube Data API Overview - Google for Developers 的推薦與評價
Introduction
This document is intended for developers who want to write applications that interact with YouTube. It explains basic concepts of YouTube and of the API itself. It also provides an overview of the different functions that the API supports.
Before you startYou need a Google Account to access the Google API Console, request an API key, and register your application.
Create a project in the Google Developers Console and obtain authorization credentials so your application can submit API requests.
After creating your project, make sure the YouTube Data API is one of the services that your application is registered to use:
Go to the API Console and select the project that you just registered.
Visit the Enabled APIs page.
In the list of APIs, make sure the status is ON for the YouTube Data API v3.
If your application will use any API methods that require user authorization, read the authentication guide to learn how to implement OAuth 2.0 authorization.
Select a client library to simplify your API implementation.
Familiarize yourself with the core concepts of the JSON (JavaScript Object Notation) data format. JSON is a common, language-independent data format that provides a simple text representation of arbitrary data structures. For more information, see json.org.
Resources and resource types
A resource is an individual data entity with a unique identifier. The table below describes the different types of resources that you can interact with using the API.
Resources
activity
Contains information about an action that a particular user has taken on the YouTube site. User actions that are reported in activity feeds include rating a video, sharing a video, marking a video as a favorite, and posting a channel bulletin, among others.
channel
Contains information about a single YouTube channel.
channelBanner
Identifies the URL to use to set a newly uploaded image as the banner image for a channel.
channelSection
Contains information about a set of videos that a channel has chosen to feature. For example, a section could feature a channel's latest uploads, most popular uploads, or videos from one or more playlists.
guideCategory
Identifies a category that YouTube associates with channels based on their content or other indicators, such as popularity. Guide categories seek to organize channels in a way that makes it easier for YouTube users to find the content they're looking for. While channels could be associated with one or more guide categories, they are not guaranteed to be in any guide categories.
i18nLanguage
Identifies an application language that the YouTube website supports. The application language can also be referred to as a UI language.
i18nRegion
Identifies a geographic area that a YouTube user can select as the preferred content region. The content region can also be referred to as a content locale.
playlist
Represents a single YouTube playlist. A playlist is a collection of videos that can be viewed sequentially and shared with other users.
playlistItem
Identifies a resource, such as a video, that is part of a playlist. The playlistItem resource also contains details that explain how the included resource is used in the playlist.
search result
Contains information about a YouTube video, channel, or playlist that matches the search parameters specified in an API request. While a search result points to a uniquely identifiable resource, like a video, it does not have its own persistent data.
subscription
Contains information about a YouTube user subscription. A subscription notifies a user when new videos are added to a channel or when another user takes one of several actions on YouTube, such as uploading a video, rating a video, or commenting on a video.
thumbnail
Identifies thumbnail images associated with a resource.
video
Represents a single YouTube video.
videoCategory
Identifies a category that has been or could be associated with uploaded videos.
watermark
Identifies an image that displays during playbacks of a specified channel's videos. The channel owner can also specify a target channel to which the image links as well as timing details that determine when the watermark appears during video playbacks and then length of time it is visible.
Note that, in many cases, a resource contains references to other resources. For example, a playlistItem
resource's snippet.resourceId.videoId
property identifies a video resource that, in turn, contains complete information about the video. As another example, a search result contains either a videoId
, playlistId
, or channelId
property that identifies a particular video, playlist, or channel resource.
The following table shows the most common methods that the API supports. Some resources also support other methods that perform functions more specific to those resources. For example, the videos.rate
method associates a user rating with a video, and the thumbnails.set
method uploads a video thumbnail image to YouTube and associates it with a video.
Operations
list
Retrieves (
GET
) a list of zero or more resources.insert
Creates (
POST
) a new resource.update
Modifies (
PUT
) an existing resource to reflect data in your request.delete
Removes (
DELETE
) a specific resource.The API currently supports methods to list each of the supported resource types, and it supports write operations for many resources as well.
The table below identifies the operations that are supported for different types of resources. Operations that insert, update, or delete resources always require user authorization. In some cases, list
methods support both authorized and unauthorized requests, where unauthorized requests only retrieve public data while authorized requests can also retrieve information about or private to the currently authenticated user.
Supported Operations
list
insert
update
delete
activity
caption
channel
channelBanner
channelSection
comment
commentThread
guideCategory
i18nLanguage
i18nRegion
playlist
playlistItem
search result
subscription
thumbnail
video
videoCategory
watermark
Quota usage
The YouTube Data API uses a quota to ensure that developers use the service as intended and do not create applications that unfairly reduce service quality or limit access for others. All API requests, including invalid requests, incur at least a one-point quota cost. You can find the quota available to your application in the API Console.
Projects that enable the YouTube Data API have a default quota allocation of 10,000 units per day, an amount sufficient for the overwhelming majority of our API users. Default quota, which is subject to change, helps us optimize quota allocations and scale our infrastructure in a way that is more meaningful to our API users. You can see your quota usage on the Quotas page in the API Console.
Note: If you reach the quota limit, you can request additional quota by
completing the Quota extension
request form for YouTube API Services.
Google calculates your quota usage by assigning a cost to each request. Different types of
operations have different quota costs. For example:
A read operation that retrieves a list of resources -- channels, videos, playlists -- usually
costs 1 unit.
A write operation that creates, updates, or deletes a resource usually has costs
50
units.A search request costs
100
units.A video upload costs
1600
units.The Quota costs for API requests table shows the
quota cost of each API method. With these rules in mind, you can estimate the number of requests
that your application could send per day without exceeding your quota.
The API allows, and actually requires, the retrieval of partial resources so that applications avoid transferring, parsing, and storing unneeded data. This approach also ensures that the API uses network, CPU, and memory resources more efficiently.
The API supports two request parameters, which are explained in the following sections, that enable you to identify the resource properties that should be included in API responses.
The part
parameter identifies groups of properties that should be returned for a resource.
The fields
parameter filters the API response to only return specific properties within the requested resource parts.
part
parameterThe part
parameter is a required parameter for any API request that retrieves or returns a resource. The parameter identifies one or more top-level (non-nested) resource properties that should be included in an API response. For example, a video
resource has the following parts:
snippet
contentDetails
fileDetails
player
processingDetails
recordingDetails
statistics
status
suggestions
topicDetails
All of these parts are objects that contain nested properties, and you can think of these objects as groups of metadata fields that the API server might (or might not) retrieve. As such, the part
parameter requires you to select the resource components that your application actually uses. This requirement serves two key purposes:
It reduces latency by preventing the API server from spending time retrieving metadata fields that your application doesn't use.
It reduces bandwidth usage by reducing (or eliminating) the amount of unnecessary data that your application might retrieve.
Over time, as resources add more parts, these benefits will only increase since your application will not be requesting newly introduced properties that it doesn't support.
How to use thefields
parameterThe fields
parameter filters the API response, which only contains the resource parts identified in the part
parameter value, so that the response only includes a specific set of fields. The fields
parameter lets you remove nested properties from an API response and thereby further reduce your bandwidth usage. (The part
parameter cannot be used to filter nested properties from a response.)
The following rules explain the supported syntax for the fields
parameter value, which is loosely based on XPath syntax:
Use a comma-separated list (fields=a,b
) to select multiple fields.
Use an asterisk (fields=*
) as a wildcard to identify all fields.
Use parentheses (fields=a(b,c)
) to specify a group of nested properties that will be included in the API response.
Use a forward slash (fields=a/b
) to identify a nested property.
In practice, these rules often allow several different fields
parameter values to retrieve the same API response. For example, if you want to retrieve the playlist item ID, title, and position for every item in a playlist, you could use any of the following values:
fields=items/id,playlistItems/snippet/title,playlistItems/snippet/position
fields=items(id,snippet/title,snippet/position)
fields=items(id,snippet(title,position))
Note: As with all query parameter values, the fields
parameter value must be URL encoded. For better readability, the examples in this document omit the encoding.
The examples below demonstrate how you can use the part
and fields
parameters to ensure that API responses only include the data that your application uses:
Example 1 returns a video resource that includes four parts as well as
kind
and etag
properties.Example 2 returns a video resource that includes two parts as well as
kind
and etag
properties.Example 3 returns a video resource that includes two parts but excludes
kind
and etag
properties.Example 4 returns a video resource that includes two parts but excludes
kind
and etag
as well as some nested properties in the resource's snippet
object.Example 1
URL: https://www.googleapis.com/youtube/v3/videos?id=7lCDEYXw3mM&key=YOUR_API_KEY
&part=snippet,contentDetails,statistics,statusDescription: This example retrieves avideo
resource and identifies several
resource parts that should be included in the API response.API response:
{
"kind": "youtube#videoListResponse",
"etag": "\"UCBpFjp2h75_b92t44sqraUcyu0/sDAlsG9NGKfr6v5AlPZKSEZdtqA\"",
"videos": [
{
"id": "7lCDEYXw3mM",
"kind": "youtube#video",
"etag": "\"UCBpFjp2h75_b92t44sqraUcyu0/iYynQR8AtacsFUwWmrVaw4Smb_Q\"",
"snippet": {
"publishedAt": "2012-06-20T22:45:24.000Z",
"channelId": "UC_x5XG1OV2P6uZZ5FSM9Ttw",
"title": "Google I/O 101: Q&A On Using Google APIs",
"description": "Antonio Fuentes speaks to us and takes questions on working with Google APIs and OAuth 2.0.",
"thumbnails": {
"default": {
"url": "https://i.ytimg.com/vi/7lCDEYXw3mM/default.jpg"
},
"medium": {
"url": "https://i.ytimg.com/vi/7lCDEYXw3mM/mqdefault.jpg"
},
"high": {
"url": "https://i.ytimg.com/vi/7lCDEYXw3mM/hqdefault.jpg"
}
},
"categoryId": "28"
},
"contentDetails": {
"duration": "PT15M51S",
"aspectRatio": "RATIO_16_9"
},
"statistics": {
"viewCount": "3057",
"likeCount": "25",
"dislikeCount": "0",
"favoriteCount": "17",
"commentCount": "12"
},
"status": {
"uploadStatus": "STATUS_PROCESSED",
"privacyStatus": "PRIVACY_PUBLIC"
}
}
]
}
Example 2
URL: https://www.googleapis.com/youtube/v3/videos?id=7lCDEYXw3mM&key=YOUR_API_KEY
&part=snippet,statisticsDescription: This example modifies thepart
parameter value so that the
contentDetails
andstatus
properties are not included
in the response.API response:
{
"kind": "youtube#videoListResponse",
"etag": "\"UCBpFjp2h75_b92t44sqraUcyu0/sDAlsG9NGKfr6v5AlPZKSEZdtqA\"",
"videos": [
{
"id": "7lCDEYXw3mM",
"kind": "youtube#video",
"etag": "\"UCBpFjp2h75_b92t44sqraUcyu0/iYynQR8AtacsFUwWmrVaw4Smb_Q\"",
"snippet": {
"publishedAt": "2012-06-20T22:45:24.000Z",
"channelId": "UC_x5XG1OV2P6uZZ5FSM9Ttw",
"title": "Google I/O 101: Q&A On Using Google APIs",
"description": "Antonio Fuentes speaks to us and takes questions on working with Google APIs and OAuth 2.0.",
"thumbnails": {
"default": {
"url": "https://i.ytimg.com/vi/7lCDEYXw3mM/default.jpg"
},
"medium": {
"url": "https://i.ytimg.com/vi/7lCDEYXw3mM/mqdefault.jpg"
},
"high": {
"url": "https://i.ytimg.com/vi/7lCDEYXw3mM/hqdefault.jpg"
}
},
"categoryId": "28"
},
"statistics": {
"viewCount": "3057",
"likeCount": "25",
"dislikeCount": "0",
"favoriteCount": "17",
"commentCount": "12"
}
}
]
}
Example 3
URL: https://www.googleapis.com/youtube/v3/videos?id=7lCDEYXw3mM&key=YOUR_API_KEY
&part=snippet,statistics&fields=items(id,snippet,statistics)Description: This example adds thefields
parameter to remove all
kind
andetag
properties from the API response.API response:
{
"videos": [
{
"id": "7lCDEYXw3mM",
"snippet": {
"publishedAt": "2012-06-20T22:45:24.000Z",
"channelId": "UC_x5XG1OV2P6uZZ5FSM9Ttw",
"title": "Google I/O 101: Q&A On Using Google APIs",
"description": "Antonio Fuentes speaks to us and takes questions on working with Google APIs and OAuth 2.0.",
"thumbnails": {
"default": {
"url": "https://i.ytimg.com/vi/7lCDEYXw3mM/default.jpg"
},
"medium": {
"url": "https://i.ytimg.com/vi/7lCDEYXw3mM/mqdefault.jpg"
},
"high": {
"url": "https://i.ytimg.com/vi/7lCDEYXw3mM/hqdefault.jpg"
}
},
"categoryId": "28"
},
"statistics": {
"viewCount": "3057",
"likeCount": "25",
"dislikeCount": "0",
"favoriteCount": "17",
"commentCount": "12"
}
}
]
}
Example 4
URL: https://www.googleapis.com/youtube/v3/videos?id=7lCDEYXw3mM&key=YOUR_API_KEY
&fields=items(id,snippet(channelId,title,categoryId),statistics)&part=snippet,statisticsDescription: This example modifies thefields
parameter from example 3
so that in the API response, each video resource'ssnippet
object only includes thechannelId
,title
,
andcategoryId
properties.API response:
{
"videos": [
{
"id": "7lCDEYXw3mM",
"snippet": {
"channelId": "UC_x5XG1OV2P6uZZ5FSM9Ttw",
"title": "Google I/O 101: Q&A On Using Google APIs",
"categoryId": "28"
},
"statistics": {
"viewCount": "3057",
"likeCount": "25",
"dislikeCount": "0",
"favoriteCount": "17",
"commentCount": "12"
}
}
]
}
Optimizing performance
Using ETags
ETags, a standard part of the HTTP protocol, allow applications to refer to a specific version of a particular API resource. The resource could be an entire feed or an item in that feed. This functionality supports the following use cases:
Caching and conditional retrieval – Your application can cache API resources and their ETags. Then, when your application requests a stored resource again, it specifies the ETag associated with that resource. If the resource has changed, the API returns the modified resource and the ETag associated with that version of the resource. If the resource has not changed, the API returns an HTTP 304 response (Not Modified
), which indicates that the resource has not changed. Your application can reduce latency and bandwidth usage by serving cached resources in this manner.
The client libraries for Google APIs differ in their support of ETags. For example, the JavaScript client library supports ETags via a whitelist for allowed request headers that includes If-Match
and If-None-Match
. The whitelist allows normal browser caching to occur so that if a resource's ETag has not changed, the resource can be served from the browser cache. The Obj-C client, on the other hand, does not support ETags.
Protecting against inadvertent overwrites of changes – ETags help to ensure that multiple API clients don't inadvertently overwrite each other's changes. When updating or deleting a resource, your application can specify the resource's ETag. If the ETag doesn't match the most recent version of that resource, then the API request fails.
Using ETags in your application provides several benefits:
The API responds more quickly to requests for cached but unchanged resources, yielding lower latency and lower bandwidth usage.Your application will not inadvertently overwrite changes to a resource that were made from another API client.
The Google APIs Client Library for JavaScript supports If-Match
and If-None-Match
HTTP request headers, thereby enabling ETags to work within the context of normal browser caching.
Using gzip
You can also reduce the bandwidth needed for each API response by enabling gzip compression. While your application will need additional CPU time to uncompress API responses, the benefit of consuming fewer network resources usually outweighs that cost.
To receive a gzip-encoded response you must do two things:
Set the Accept-Encoding
HTTP request header to gzip
.
Modify your user agent to contain the string gzip
.
The sample HTTP headers below demonstrate these requirements for enabling gzip compression:
Accept-Encoding: gzip
User-Agent: my program (gzip)
... <看更多>
it would be better用法 在 『be better off』是什麼意思? be... - 每日一句學英文- Daily ... 的推薦與評價
『be better off』是什麼意思? be better off 經濟狀況較以前(或較大多數人)好; 情況好轉 e.g., Obviously we're better off now that we're ... ... <看更多>