Planning a trip outside of your own country can be an involved process. On top of the usual tasks of purchasing airline tickets, booking a hotel, deciding what to see, and making reservations, you may also need to obtain a visa and learn some basic foreign language phrases. One thing you may not have considered, though, is brushing up on cultural faux pas of the countries where you plan to visit. For instance, is it rude to shake hands when greeting someone in certain countries? Is a “thumb’s up” considered an insult in the Middle East? Can you go into an Italian cathedral in a sleeveless shirt?
Posted by in Language and Culture on June 20, 2019 0 Comments
Faux Pas 1: Wearing sneakers or dress shoes. The latter doesn’t necessarily apply if you’re working in Miami, Oahu, or any spring break location, but if you’re in wintery areas, snow won’t show your leather dress shoes any mercy. Dress shoes might not be a smart way to go, but sneakers are just unacceptable in the workplace. For example, 1 in 5 Millennials consider themselves a financial expert, compared to fewer than 1 in 10 Baby Boomers. Additionally, 1 in 3 Millennials who committed budgeting “faux pas” reported feeling afraid to check their bank account, compared to 1 in 5 Gen-Xers and just 1 in 10 Baby Boomers. Faux Pas 1.7.1: Size: 23.66 MB: Files list: Faux Pas 1.7.1.zip (23.66 MB) Download torrent file Description. Name: Faux Pas for Mac Version: 1.7.1 Release Date: 15 Dec 2016 Mac Platform: Intel OS version:OS X 10.9 or later Processor type(s) & speed: 64-bit processor Requirements: Xcode 5 or later. Tank tops, halter tops and anything strapless. In most cases, T-shirts are seen as a fashion faux pas at the office because they're too casual. Taking that principle a step further, tank tops, spaghetti straps and halter tops are prohibited by the dress code at many offices.
Faux pas #1: Japan and China – Pointing chopsticks upright in a rice bowl.
Japan has a number of cultural “no-no’s”, and if you’re not careful you could unwittingly insult someone. For example, Buddhists consider placing chopsticks upright in a bowl of rice an offering to the dead. In China, this placement is seen as bad luck.
Faux pas #2: China – Wearing shoes in sacred places.
Many cultures have customs about taking your shoes off when you enter a temple or other sacred place. China is one of them. You should also take off your shoes upon entering someone’s home.
Faux pas #3: Confusing China for Japan (and vice-versa)
China and Japan have a very long, complicated history that would make this mistake highly insulting. But unfortunately this is a mistake even royalty can make.
Faux pas #5: United Arab Emirates – Wearing revealing clothing
Out of respect and in keeping with the dress codes of local establishments, women are generally advised to wear clothing that covers from the shoulders to the knees. Tight-fitting sports apparel, such as cycling shorts, is generally not advised for either men or women unless worn in a sports venue.
Faux pas #6: Italy – Not following the dress code for cathedrals.
Like number 5, if you’re planning a trip to Italy, you will want to visit the country’s famous cathedrals such as St. Peter’s in Vatican City. These sacred places have dress codes in order to enter them. Bare shoulders, short skirts, and dresses that are above the knees are not acceptable. Wear pants or a long dress/skirt and bring a sweater or scarf to cover your shoulders. Faux Pas 1 6 12
Faux pas #7: U.K. and Brazil – Offensive hand gestures.
Peace sign? Refrain from making this gesture in the U.K. It’s basically an invitation to a fight, as if you flipped someone off. In Brazil, raising a fist means that a man’s wife is cheating on him. The “OK” sign is also considered obscene.
Faux pas #8: Singapore – Bringing bubblegum into the country.
Bubblegum caused such a problem in terms of vandalism that the country decided to ban it altogether. Even having it on you is a strict “no-no” that can land you in jail for up to two years. So, no blowing bubbles in Singapore.
Faux pas #9: Thailand – Touching someone’s head.
The key to avoiding offense in Thailand is remembering one simple rule…the head is sacred and feet are unclean. Therefore, you never want to point at someone’s feet or make any type of physical contact with another person’s head.
Faux pas #10: Korea – Smiling at strangers.
In America, it is customary to smile when you meet someone new or even pass strangers on the street. In Korea, this is outside of the norm and even viewed as strange.
Faux pas #11: Pakistan – Not giving your elders proper respect.
Many cultures revere elderly people. Paying proper respect to them is extremely important. If you are introduced to an elderly person in Pakistan, stand up and greet him or her formally. Staying seated is an insult.
Faux pas #12: Iran and Iraq – Using a thumb’s up gesture.
If you want to say “good job” in American we often give a thumb’s up. In Iran and Iraq this common gesture is not acceptable. At all. It is one of the worst non-verbal insults you can make.
Faux pas #13: Calling a Scottish, Irish or Welsh person “English”.
Great Britain includes England, Scotland, Wales, and Northern Ireland. Various wars and conflicts have been going on between these countries for centuries. Though they mostly get along now, they prefer to be called “Welsh” or “Scottish” or “Irish”. Calling any of them “English” could lead to a fight.
Faux pas #14: Nepal – Shaking hands as a greeting.
The American way of meeting some new is by shaking hands. In Nepal, this is not acceptable. The best way to greet someone is by pressing your palms together, as if you were in prayer. It’s a gesture known as namaste.
ALTA Language Services provides professional translation services for businesses, government, medical, legal, and technical fields. Contact us today for your translation and interpretation needs.
Kristin Wallace is a USA Today Bestselling fiction author and advertising copywriter who is addicted to learning and writing about language, culture and art around the world. She lives and works in sunny Miami, Florida.
HTTP APIs are very loose by definition: there’s no standards body, no API validator and not always someone there to tell you when you may be doing something incorrect. At ReadMe we have lots of experience in building, consuming and viewing APIs created by others. We even have our own open source API Explorer which is used by all of our projects to try out APIs in the browser.
I asked engineers in the ReadMe team, “What are some common issues or pitfalls you see when using APIs?” This is a definitely a non-exhaustive list, but avoiding some of these pitfalls will make your APIs more “standard,” intuitive, and easy to use. We came up with the following faux pas:
1. Sending a Mixture of Query Params and Body Params
When you create an API endpoint you should consider accepting either query parameters or body parameters, but not both. Since GET requests can’t have bodies, the best way to pass in parameters and filters is via query string. For POST requests (and other non-idempotent methods) you should prefer bodies.
This is an example of using both query and body params, for a POST request:
It should be modified to send both properties via the body:
Using query strings is fine for filtering, like so:
2. Sending Private API Keys in a Query String
You should never accept private API keys or passwords in query strings. Servers often print out the whole URL for debugging later in their log files. You don’t want your users’ passwords being stored in plain text on the disk.
You can switch to using a header for this value to keep your users’ confidential keys and passwords safe:
3. Using the Wrong Method: POST When You Mean PUT/PATCH
HTTP consists of 9 verbs, the most common of which are: GET, POST, PUT, PATCH and DELETE. In REST APIs, each of these roughly translates to the four functions of storage: CRUD.
Using the wrong verb is considered bad practice when creating an API, though it’s technically possible. As an API consumer, you would not expect a “Read” operation (GET) to perform a “Create” (POST). For example: Using GET to “Create” a new item.
This should use POST, with a body.
4. Adding Verbs in URLs
We’ve seen this one lots of times, where a path contains a verb that should be represented via a method.
Example of a path containing the verb
create .
This is similar to using the wrong HTTP method. To correct this, remove the verb from the path and use the correct method. (See table above.)
5. Accepting Multiple Types of Object on the Same URL
Sometimes we see developers that create the “one endpoint to rule them all™”—one endpoint that can take a whole host of object shapes. If a path has a very generic noun, like
/entities and it accepts lots of different object “types,” like this:
Faux Pas 1 6 1/2
It’s better to have a different endpoint for each entity:
This is easier for documentation purposes, easier for your debugging and simpler for your users.
6. Creating Your Own Version of Something, When a Header Exists
Often we also see people re-implementing something that already exists as part of the HTTP spec. The main example of this we see regards the Accept/Content-Type headers.
The Accept header is used by the client to let the API know what content type they would like to get back, the Content-Type header is used by the server to let the client know what type they are actually returning. This process is called content negotiation.
We’ve seen unnecessary workarounds for things Accept headers can already handle, such as:
There are lots of Accept-* headers that can be utilized for various ways of defining what you as a client expect or prefer:
As with every set of rules or best practices, there are times when they are meant to be broken. Typically if you intend for your API to be accessed directly via a browser, you may have to expose things via query string that you (in an ideal world) should do via a header. This is one of the benefits of REST/HTTP—they allow the flexibility to do whatever you want to do.
Are there any others that you’d add to this list? Boom 2 1 4 1 download free. Am I completely wrong on this? Tweet @readme with your comments!
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |