Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the amp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the gotmls domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170
Pemegang Pasport China, Hong Kong & Macau Dilarang Naiki Royal Caribbean – Independent

Pemegang Pasport China, Hong Kong & Macau Dilarang Naiki Royal Caribbean

Reading Time: 2 minutes

Kapal pesiaran Royal Caribbean pada hari Jumaat mengharamkan sesiapa yang memegang pasport dari China, Hong Kong, atau Macau dari menaiki kapalnya di tengah-tengah wabak koronavirus.

Virus itu baru saja menjangkiti 61 orang di kapal Princess Cruises yang berlabuh di Yokohama berhampiran Tokyo, Jepun, kata pegawai di sana pada hari Jumaat. Empat orang dari kapal Royal Caribbean yang berlabuh di New Jersey dibawa ke hospital untuk pemeriksaan selepas menunjukkan tanda-tanda virus pada hari Jumaat.

Pengharaman baru terhadap pemegang pasport berlangsung walaupun pemegang tidak pernah berada di negara mereka sendiri untuk seketika, kata Royal Caribbean dalam satu kenyataan.

Di samping itu, sesiapa sahaja – tanpa mengira kewarganegaraan – yang telah mengembara ke China, Hong Kong, atau Macau kurang dari 15 hari sebelum cuba menaiki kapal Royal Caribbean akan dihalang daripada masuk. Dan mana-mana tetamu atau anak kapal yang telah bersentuhan, atau dalam jarak enam kaki, seseorang yang telah mengembara, ke, atau melalui tanah besar China, Hong Kong, atau Macau kurang dari 15 hari yang lalu juga akan dihalang daripada menaiki pesawat.

Penumpang yang tidak pasti sama ada mereka telah bersentuhan dengan orang tersebut akan dikehendaki menjalani pemeriksaan kesihatan khusus, dan juga penumpang yang melaporkan rasa tidak sihat atau menunjukkan gejala seperti selesema.

Negara-negara di seluruh dunia serta syarikat penerbangan dan negara-negara lain telah mengambil tindakan di tengah-tengah wabak koronavirus, menyekat perjalanan, membatalkan penerbangan, dan melaksanakan ujian di lapangan terbang, stesen kereta api, dan sempadan.

Pengumuman Royal Caribbean datang apabila Jepun enggan membenarkan kapal Carnival dari berlabuh di pelabuhannya walaupun tidak ada kes yang disahkan di atas kapal itu.

Kapal pelayaran Westerdam itu “sedang dalam status menunggu untuk dilepaskan ke pantai Jepun, tenggara Okinawa, sementara kami sedang berusaha untuk memuktamadkan sebuah pelabuhan baru,” kata Holland America, anak syarikat Carnival Corp., dalam kenyataan pada hari Khamis.

Kapal pesiaran menghadapi cabaran unik kerana bagaimana sesak semua orang berkumpul di satu tempat, kata Dr Michael Ryan, pengarah eksekutif Program Kecemasan Kesihatan Pertubuhan Kesihatan Sedunia, semasa sidang akhbar pagi di ibu pejabat organisasi di Geneva, Switzerland.

“Sebuah kapal pesiaran adalah persekitaran yang sangat khusus di mana anda boleh mempunyai tahap transmisi yang lebih tinggi walaupun dengan virus yang tidak begitu efisien,” katanya. “Itu bukan bermaksud virus ini tidak akan mendapat lebih banyak peluang menyebar dengan lebih banyak.”

Wabak kapal pesiaran besar bukan baharu, katanya, memetik wabak norovirus yang telah berlaku pada kapal-kapal dalam beberapa tahun kebelakangan ini.

“Ini tidak luar biasa,” katanya. Tidak sukar untuk orang yang terjebak dalam keadaan itu, kerana mereka terkurung. Ia agak menakutkan. Ia sangat, sangat menakutkan untuk berada dalam keadaan itu.”