A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 6

Backtrace:

File: /home/ipsit/public_html/application/controllers/Boxoffice.php
Line: 16
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 7

Backtrace:

File: /home/ipsit/public_html/application/controllers/Boxoffice.php
Line: 16
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 8

Backtrace:

File: /home/ipsit/public_html/application/controllers/Boxoffice.php
Line: 16
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 9

Backtrace:

File: /home/ipsit/public_html/application/controllers/Boxoffice.php
Line: 16
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 10

Backtrace:

File: /home/ipsit/public_html/application/controllers/Boxoffice.php
Line: 16
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 11

Backtrace:

File: /home/ipsit/public_html/application/controllers/Boxoffice.php
Line: 16
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 284

Backtrace:

File: /home/ipsit/public_html/application/controllers/Boxoffice.php
Line: 16
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 291

Backtrace:

File: /home/ipsit/public_html/application/controllers/Boxoffice.php
Line: 16
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 306

Backtrace:

File: /home/ipsit/public_html/application/controllers/Boxoffice.php
Line: 16
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 316

Backtrace:

File: /home/ipsit/public_html/application/controllers/Boxoffice.php
Line: 16
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 317

Backtrace:

File: /home/ipsit/public_html/application/controllers/Boxoffice.php
Line: 16
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 318

Backtrace:

File: /home/ipsit/public_html/application/controllers/Boxoffice.php
Line: 16
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 319

Backtrace:

File: /home/ipsit/public_html/application/controllers/Boxoffice.php
Line: 16
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 377

Backtrace:

File: /home/ipsit/public_html/application/controllers/Boxoffice.php
Line: 16
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 110

Backtrace:

File: /home/ipsit/public_html/application/controllers/Boxoffice.php
Line: 16
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_start(): Session cannot be started after headers have already been sent

Filename: Session/Session.php

Line Number: 143

Backtrace:

File: /home/ipsit/public_html/application/controllers/Boxoffice.php
Line: 16
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

NRIPage | Box Office | Mohanlal’s Thudarum Sparks Debate Over Native Titles in Telugu Dubbed Films | Get Indian Desi Movie News. Latest Buzz about Indian Telugu, Hindi, Tamil, Hollywood & other upcoming movies - NRI Page
Edit

Mohanlal’s Thudarum Sparks Debate Over Native Titles in Telugu Dubbed Films

Mohanlal’s Thudarum Sparks Debate Over Native Titles in Telugu Dubbed Films
  • 25 Apr 2025 12:00 AM
  • 79 views
The Telugu film industry has long been known for its open-armed embrace of dubbed films from other Indian languages. Whether it's Tamil, Kannada, Malayalam, or even Hindi, the Telugu audience has consistently shown a deep appreciation for diverse cinematic experiences. This inclusive attitude has turned the Telugu market into one of the most welcoming destinations for non-Telugu films dubbed into the local language. However, a noticeable shift in the dubbing culture has triggered discussions among fans, film critics, and industry insiders. The trend of retaining original, non-Telugu titles for dubbed films is growing, and many feel that this compromises the integrity of the Telugu language and its cultural identity. The most recent example that has reignited the debate is Mohanlal’s upcoming film Thudarum.
In Malayalam, Thudarum translates to "To Be Continued," a phrase that carries significant contextual meaning in the original language. However, when dubbed and released in Telugu using the same title, it fails to resonate with or convey any clear meaning to the Telugu-speaking audience. The title, disconnected from Telugu sensibilities, has left many puzzled and disappointed. The issue is not limited to the title alone. The trailer of Thudarum has also drawn criticism for poor dubbing quality, further amplifying concerns that filmmakers are not giving enough attention to the Telugu version.
This trend isn't new. Previously, the Tamil historical epic Ponniyin Selvan was released in Telugu under the same title. The filmmakers defended the choice, stating there was no suitable alternative that captured the essence of the story. Both parts of the movie followed this naming convention, and the film’s massive scale and historical roots made it somewhat acceptable to audiences. Then came Kantara, a Kannada blockbuster whose title is deeply rooted in the region’s folklore and traditions. The makers explained that there was no direct translation that could do justice to the name, and thus, it was retained in all languages, including Telugu. While some accepted this logic, others began to wonder if this approach would now become a blanket excuse for every dubbed release.
Rajinikanth’s film Vettaiyaan followed suit, with its Tamil title being retained in Telugu. The justification given was that the desired title was not available or not approved. Recently, Empuraan, another Malayalam film starring Mohanlal, was released in Telugu using its original name. The cumulative effect of these choices has started to irk a section of Telugu viewers, who feel sidelined in favor of linguistic convenience or brand consistency. Adding to the list is Alappuzah Gymkhana, a Malayalam film starring Naslen of Premalu fame, which is also releasing in Telugu with the same name. Despite being a local reference in Malayalam, no efforts were made to adapt or modify the title for Telugu audiences. Similarly, Suriya’s upcoming film Retro is heading for a Telugu release under the same name, sparking further concerns.
A growing number of voices in the Telugu film circles feel that this trend is not just lazy but also disrespectful. There’s a belief that while other South Indian film industries make an effort to localize titles and content when targeting specific linguistic audiences, Telugu seems to be treated differently—often as an afterthought. This has led to perceptions that the Telugu audience is being taken for granted, expected to accept titles and contexts they may not fully understand. Critics argue that language is more than a medium of communication—it is an identity. Titles hold emotional and cultural weight, and stripping that away by ignoring meaningful translations undermines the effort of dubbing itself. If the idea behind dubbing is to make content more accessible, shouldn’t that extend to titles too?
Moreover, the issue raises broader questions about mutual respect within South Indian cinema. While the industries often unite in resisting what they perceive as Hindi dominance or linguistic centralization, they should also strive to respect each other’s regional languages and cultures in the process. If Tamil, Kannada, and Malayalam films can be dubbed with translated titles in other languages, why not make the same effort for Telugu? Some insiders point out that marketing teams might prefer retaining original titles for consistency across regions and online platforms. In the age of social media and pan-India branding, a single recognizable title helps with promotion and online searches. But this convenience should not come at the cost of alienating a local audience.
The Telugu audience has repeatedly proven its maturity and love for good cinema, regardless of origin. However, that openness should not be mistaken for indifference. The community deserves the same linguistic respect it has extended to others over the years. A thoughtful translation or culturally relevant adaptation of titles can go a long way in maintaining that bond. As the conversation continues, it will be interesting to see whether upcoming dubbed releases will take note of this feedback. Will filmmakers and distributors begin to pay closer attention to Telugu titles and translations? Or will the trend of retaining original names, regardless of regional context, persist? The audience, after all, holds the final say.
AD
AD