Twitter outrage over Saif, Kareena naming their son Taimur

Bollywood couple Saif and Kareena's little bundle of joy arrived yesterday


Entertainment Desk December 21, 2016
PHOTO: INDIAN EXPRESS

Beloved Bollywood couple Saif and Kareena's little bundle of joy may have just arrived yesterday but the baby boy has already become controversy's favourite child.

Contrary to what many of their fans believed, the actors did not name the baby Saifeena, but Taimur Ali Khan Pataudi, which means Iron in Arabic. The #TaimurAliKhanPataudi has already been trending on top in India yesterday, says Times of India.

However, the choice of name has sparked a variety of responses from fans, some good and others, not so much, reports NDTV.

Kareena Kapoor, Saif Ali Khan blessed with baby boy

A statement released on behalf of the new parents read: "We are very pleased to share with you all the wonderful news about the birth of our son: Taimur Ali Khan Pataudi, on the 20th of December 2016. We would like to thank the media for the understanding and support they have given us over the last nine months, and of course, especially our fans and well wishers for their continued affection. Merry Christmas and a happy new year to you all."

Saif and Kareena's latest shoot captures the royal couple in all their glory

But despite the sweet message, Twitter is fixated on Saif and Kareena's choice of name. Here are some of the tweets:





https://twitter.com/heisenjit/status/811107346374082562





https://twitter.com/Vishj05/status/811086809455153152









Have something to add in the story? Share it in the comments below. 

 

COMMENTS (8)

FAZ | 7 years ago | Reply @Abhi: Guess who was Taimur's successor? SHAHRUKH lol
LOL | 7 years ago | Reply there you go. parents cannot even name their children according to their wish and they ask why our forefathers demanded separate land. Two Nation Theory is alive and well.
VIEW MORE COMMENTS
Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ