Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf 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/farshid1/public_html/wp-includes/functions.php on line 6170

Deprecated: acf_get_value(): Optional parameter $post_id declared before required parameter $field is implicitly treated as a required parameter in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/acf-value-functions.php on line 54

Deprecated: acf_update_value(): Optional parameter $value declared before required parameter $field is implicitly treated as a required parameter in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/acf-value-functions.php on line 166

Deprecated: acf_update_value(): Optional parameter $post_id declared before required parameter $field is implicitly treated as a required parameter in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/acf-value-functions.php on line 166

Deprecated: Creation of dynamic property ACF::$fields is deprecated in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/fields.php on line 136

Deprecated: Creation of dynamic property acf_loop::$loops is deprecated in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/loop.php on line 26

Deprecated: Creation of dynamic property ACF::$loop is deprecated in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/loop.php on line 270

Deprecated: Creation of dynamic property ACF::$revisions is deprecated in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/revisions.php on line 413

Deprecated: Creation of dynamic property acf_validation::$errors is deprecated in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/validation.php on line 26

Deprecated: Creation of dynamic property ACF::$validation is deprecated in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/validation.php on line 212

Deprecated: ACF_Ajax::set(): Optional parameter $key declared before required parameter $value is implicitly treated as a required parameter in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/ajax/class-acf-ajax.php on line 76

Deprecated: Creation of dynamic property acf_form_customizer::$preview_values is deprecated in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-customizer.php on line 26

Deprecated: Creation of dynamic property acf_form_customizer::$preview_fields is deprecated in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-customizer.php on line 27

Deprecated: Creation of dynamic property acf_form_customizer::$preview_errors is deprecated in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-customizer.php on line 28

Deprecated: Creation of dynamic property ACF::$form_front is deprecated in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-front.php on line 603

Deprecated: Creation of dynamic property acf_form_widget::$preview_values is deprecated in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-widget.php on line 34

Deprecated: Creation of dynamic property acf_form_widget::$preview_reference is deprecated in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-widget.php on line 35

Deprecated: Creation of dynamic property acf_form_widget::$preview_errors is deprecated in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-widget.php on line 36

Deprecated: WP_Rocket_Mobile_Detect::__construct(): Implicitly marking parameter $headers as nullable is deprecated, the explicit nullable type must be used instead in /home/farshid1/public_html/wp-content/plugins/wp-rocket/inc/classes/dependencies/mobiledetect/mobiledetectlib/Mobile_Detect.php on line 888

Deprecated: Creation of dynamic property acf_field_oembed::$width is deprecated in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/fields/class-acf-field-oembed.php on line 31

Deprecated: Creation of dynamic property acf_field_oembed::$height is deprecated in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/fields/class-acf-field-oembed.php on line 32

Deprecated: Creation of dynamic property acf_field_google_map::$default_values is deprecated in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/fields/class-acf-field-google-map.php on line 33

Deprecated: Creation of dynamic property acf_field__group::$have_rows is deprecated in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/fields/class-acf-field-group.php on line 31

Deprecated: acf_field_repeater::update_row(): Optional parameter $i declared before required parameter $post_id is implicitly treated as a required parameter in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/pro/fields/class-acf-field-repeater.php on line 721

Deprecated: acf_field_repeater::delete_row(): Optional parameter $i declared before required parameter $post_id is implicitly treated as a required parameter in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/pro/fields/class-acf-field-repeater.php on line 787

Deprecated: acf_field_flexible_content::get_layout(): Optional parameter $name declared before required parameter $field is implicitly treated as a required parameter in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/pro/fields/class-acf-field-flexible-content.php on line 1040

Deprecated: acf_field_flexible_content::delete_row(): Optional parameter $i declared before required parameter $post_id is implicitly treated as a required parameter in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/pro/fields/class-acf-field-flexible-content.php on line 1076

Deprecated: acf_field_flexible_content::update_row(): Optional parameter $i declared before required parameter $post_id is implicitly treated as a required parameter in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/pro/fields/class-acf-field-flexible-content.php on line 1128

Deprecated: acf_field_gallery::render_attachment(): Optional parameter $id declared before required parameter $field is implicitly treated as a required parameter in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/pro/fields/class-acf-field-gallery.php on line 296

Deprecated: Creation of dynamic property acf_field_clone::$cloning is deprecated in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/pro/fields/class-acf-field-clone.php on line 34

Deprecated: Creation of dynamic property acf_field_clone::$have_rows is deprecated in /home/farshid1/public_html/wp-content/plugins/advanced-custom-fields-pro/pro/fields/class-acf-field-clone.php on line 35

Deprecated: Creation of dynamic property acf_field_ryancv_ui_google_font::$font is deprecated in /home/farshid1/public_html/wp-content/plugins/ryancv-plugin/acf-ext/acf-ui-google-font/acf-ui-google-font-v5.php on line 8693

Deprecated: Creation of dynamic property acf_field_ryancv_ionicons::$font is deprecated in /home/farshid1/public_html/wp-content/plugins/ryancv-plugin/acf-ext/acf-ionicons/acf-ionicons-v5.php on line 1502
Did you know these new Oxfam Language Rules? – وبسایت رسمی فرشید فرزانگان
United Arab Emirates

Did you know these new Oxfam Language Rules?


Deprecated: preg_split(): Passing null to parameter #3 ($limit) of type int is deprecated in /home/farshid1/public_html/wp-content/themes/jannah/framework/functions/post-functions.php on line 805

Did you know these new Oxfam Language Rules?

By Shashi Tharoor

Published: Thu 13 Apr 2023, 9:47 PM

A few weeks ago we discussed Stanford University’s “Elimination of Harmful Language Initiative”, under which the famous American university issued a list of words that people should avoid using because they are “ableist”, “ageist” or show “gender bias”. No doubt prompted by this, a reader has sent me a new Inclusive Language Guide issued by the British charitable agency Oxfam.

A glance at the Guide suggests that the urge to get people to bite their tongues rather than use language which some may find “politically incorrect” has now crossed all reasonable limits. Oxfam has urged its employees to avoid the terms “mother” and “father” and instead use “parent”. It warns its staff to “avoid assuming the adoption of gendered roles by transgender parents”. According to the Guide: “If trans parents have a preferred specified gender role, such as ‘mother’ or ‘father’, this should be respected. If unsure, it is more inclusive to use ‘parent’.”

Including “mother” and “father” among its list of potentially offensive terms, however, defies simple common sense. These are among the most basic terms employed by the human race; there is no language on the planet that does not have words for “mother” and “father”, depicting the primordial relationships a child encounters upon entering the world. Hilariously, Oxfam prefers the very words “male” and “female” to be replaced with AFAB and AMAB (“assigned female at birth” and “assigned male at birth”). Isn’t this taking political correctness too far?

Oxfam argues that “the important principle here is to be inclusive in the broader sense by describing people as ‘parents’.” Of course it also concedes that “if individual parents have a preference for a role name, [staff may] respect their choice.” But it goes on to urge people to replace the term “expectant mothers” with “people who become pregnant”. How many such “people” in the world would actually protest being called “expectant mothers”?

I am not objecting to every point in the 92-page Oxfam document, which is available online. It makes sense for a philanthropic body working around the world to guide staff to be sensitive to issues of race, gender justice, sexual diversity and women’s rights, disability, physical and mental health, migration and the linguistic legacy of colonisation, which left behind a number of terms whose unconscious use might indeed hurt people. Oxfam also warns employees to be conscious of words and phrases that might be considered “discriminatory” or “that have been used historically to oppress certain people or groups”. Thus it makes sense to say “sex worker” instead of “prostitute”, or “humankind” in place of “mankind”.

But even innocent, commonplace everyday words are proscribed for reasons that seem absurd. For instance, Oxfam encourages its staff not to say “attitudes” or “behaviours” but to replace them with “social norms, social beliefs or collective beliefs”. Excuse me? Equally ridiculous is the exhortation not to use the word “headquarters” because it “implies a power dynamic that prioritises one office over another. In the context in which we work the implication is very colonial, reinforcing hierarchical power issues”.

Oxfam’s hyper-sensitivity to anything that might cause offence extends preferring the use of the terms “menstrual products” in place of “sanitary products” or “feminine hygiene products” because such seemingly neutral terms imply “that periods are in themselves unclean”. You can’t say “ethnic minority” because it “places the emphasis on that ethnicity being a minority or having less power in a particular context”; instead you must say “minority ethnic person”. The guidebook also states that one should not speak of a “migration crisis”, only of “migration as a complex phenomenon”. (Both these are examples of “splitting hairs”, except that perhaps that term itself would be outlawed as being offensive to bald people!)

Don’t get me wrong: I agree with Oxfam that inclusive language is important. I accept Oxfam’s justification that the guide intends to help employees “communicate in a way that is respectful to the diverse range of people with whom we work. We …. won’t succeed in tackling poverty by excluding marginalised groups.” But the inclusion of silly prohibitions that can easily be caricatured risks undermining the more worthwhile ideas. It’s important to know when you’ve gone too far. Stop!

wknd@khaleejtimes.com



source: khaleejtimes


Deprecated: preg_split(): Passing null to parameter #3 ($limit) of type int is deprecated in /home/farshid1/public_html/wp-content/themes/jannah/framework/functions/post-functions.php on line 805
نمایش بیشتر

نوشته های مشابه

دیدگاهتان را بنویسید

نشانی ایمیل شما منتشر نخواهد شد. بخش‌های موردنیاز علامت‌گذاری شده‌اند *

دکمه بازگشت به بالا