User:SOTO/Forum Archive/Inclusion debates/@comment-28743561-20191009174707/@comment-31010985-20191014223457: Difference between revisions
From Tardis Wiki, the free Doctor Who reference
(Bot: Automated import of articles) |
m (Bot: Automated text replacement (-'''User:(SOTO/Forum Archive)/(.*?)/\@comment-([\d\.]+)-(\d+)/\@comment-([\d\.]+)-(\d+)'''\n([\s\S]*)\[\[Category:SOTO archive posts\]\] +\7\2/\4-\3/\6-\5)) |
||
| Line 1: | Line 1: | ||
The new ''Mission to the Unknown'' had no differences ''per se'' but I did notice de Souza's fluff of "Special Security Service" instead of "Space Security Service" remained. Obviously, since the webcast was a conscious effort to be as faithful to the original as possible this can no longer be considered a production error but rather a production choice not to correct it. I'm not sure if we should consider the alternate name valid in this situation as we don't usually cover production errors but it was not a production error for the new version. | The new ''Mission to the Unknown'' had no differences ''per se'' but I did notice de Souza's fluff of "Special Security Service" instead of "Space Security Service" remained. Obviously, since the webcast was a conscious effort to be as faithful to the original as possible this can no longer be considered a production error but rather a production choice not to correct it. I'm not sure if we should consider the alternate name valid in this situation as we don't usually cover production errors but it was not a production error for the new version. | ||
<noinclude>[[Category:SOTO archive posts]]</noinclude> | <noinclude>[[Category:SOTO archive posts|Inclusion debates/20191009174707-28743561/20191014223457-31010985]]</noinclude> | ||
Latest revision as of 14:25, 27 April 2023
The new Mission to the Unknown had no differences per se but I did notice de Souza's fluff of "Special Security Service" instead of "Space Security Service" remained. Obviously, since the webcast was a conscious effort to be as faithful to the original as possible this can no longer be considered a production error but rather a production choice not to correct it. I'm not sure if we should consider the alternate name valid in this situation as we don't usually cover production errors but it was not a production error for the new version.
