Laal Singh Chaddha, starring Aamir Khan, has finally been released in the cinemas. It is an official remake of Forrest Gump (1994) though the writers have made a few changes here and there and Indianized the narrative. A significant scene in Laal Singh Chaddha however gives a strong déjà vu of the recent controversy of Ranveer Singh.
In Forrest Gump, the protagonist is in the army and one of his teammates passes him an adult magazine in a scene. Forrest sees the picture of his crush, Jenny, on it. The voiceover of Forrest mentions that Jenny had posed for the magazine seductively in her college sweater. As a result, she was expelled from college.
In Laal Singh Chaddha, the protagonist is handed over a newspaper. His colleague points him at the controversial naked picture of Milind Soman and Madhu Sapre. Laal Singh Chaddha, however, realizes that the same issue had also published a backless picture of his childhood love, Rupa. The article along with the picture informed Laal that a legal notice was slapped on Rupa by certain organizations for promoting vulgarity.
This track in the film reminds one of Ranveer Singh’s recent nude photoshoot controversy. The talented actor’s multiple photos were published by a magazine, wherein he was seen posing without any clothing. While many appreciated this move, a lawyer complained to the cops, after which an FIR was lodged against the actor. After this development, several personalities came forward in support of Ranveer and felt that the police complaint against him is unjustified.
Interestingly, Milind Soman and Madhu Sapre’s hot picture had also led to a lot of brouhaha. In 1995, both the models had done a bold, nude photoshoot for Turf Shoes and were aesthetically covered by a python. The social service branch of the Mumbai police had registered a case against them, citing indecency. The case lasted for 14 years, after which the courts acquitted them.
from Latest Bollywood News | Hindi Movie News | Hindi Cinema News | Indian Movies | Films - Bollywood Hungama https://ift.tt/2sxlJXm
via IFTTT
No comments:
Post a Comment