CatBus

oojason said:

‘Disney+ Finally Adds Navajo Translation for Star Wars: A New Hope’:-

https://www.cbr.com/disney-finally-adds-navajo-translation-for-star-wars-a-new-hope

The Navajo language dubbed version of Star Wars: A New Hope is now available to stream on the Disney+ platform for the first time since its 2013 debut.
 

And it is available in 1080p HD too. 👍
 

Thanks for the link!

The limited edition DVD didn’t translate the “STAR WARS” title, only “Episode IV: A New Hope” – but your link shows the Navajo translation for STAR WARS: SǪ’TAH ANAA’. Now the Navajo subtitles will be just a little more complete (next Project Threepio release).

Open request: Anyone who wants to transcribe the Navajo dub into text would allow me to make complete Navajo subtitles for Star Wars, rather than just translations of the onscreen text. It would be much appreciated!

PM sent. Couldn’t have done all of these variations for various languages without your help, schorman13!

We’ve come a long way since the original rontoscoping.

Project files have been updated to version 12.0 (codename: “Time of Your Life”), and the first post has been updated. Please PM me for temporary download links until the files are available at some more permanent locations.

Rough summary of changes from 11.0 to 12.0:

• New languages: Catalan, Basque (both thanks to laozi), and Slovak
• New Japanese translation (thanks to schorman13)
• New Korean translation for Star Wars (thanks to Kaz47)
• Included titles-only subtitles to go with the Galician dub (again, thanks to laozi)
• Improvements to the Castilian Spanish subtitles (yet again, thanks to laozi!)
• Improved Finnish translations (thanks to LexX)
• Improved Swedish translations (thanks to Rondan)
• Finally adding this much-requested feature, every official pre-1997 version of the trilogy is now fully supported in all supported languages. This includes four subtitle variations for Star Wars, and two for Empire. Multiply that by a lot of languages, and that’s just a ton of subtitles. I was able to do this without driving myself crazy by making the whole process automated, using “fragment files”, which are a sort of multi-target subtitle diff file I created for this purpose. The fragment files include translations for all of the subtitle-worthy differences for all of the pre-1997 versions of the films. Using a script, you can quickly assemble subtitles (in SUP or SRT format) for any pre-1997 version of the films using the original stereo/surround subtitles as a baseline, then adding the appropriate portions of the fragment file, and making various timing adjustments. Any new languages added to the project will need to include fragment files in addition to the regular stereo/surround SRT files. Script-generated SRT files are included in all supported languages for every pre-1997 mix, but to conserve space, only the original stereo/surround versions are provided in SUP format. You can, however, easily assemble SUP files for any version you prefer. To avoid the confusion of so many different versions, each subtitle variation has its own subfolder (thanks to laozi, RashadShehadeh, Feallan, ccfilms, LexX, ZIPC, Leoj, Rondan, Harmy, daboka, Mavimao, Kaz47, and schorman13).
• Created a new subtitle rendering script, no longer relying on ImageMagick+Pango, and instead simply rendering subtitles in a Chromium-based web browser. The advantage of the new script is that it no longer relies on running outdated versions of ImageMagick and Pango, and its cross-platform behavior is also much improved (there are no longer any scripts that can’t be rendered on Windows, for example). ImageMagick is still heavily used, just without the Pango integration. Many minor bugs in the old script were fixed during the rewrite, and it’s quite likely some new ones were also created! One known issue is that Chromium-based browsers tend to create stray processes that over time bog down a machine, so if you do run this script, I recommend rebooting your computer afterward, just to be safe.
• Bulgarian and Macedonian got better localized Cyrillic text than the current released versions of the Noto Sans fonts can provide out-of-the-box.
• Most languages got some very minor changes, typically just timing improvements
• Pre-rendered graphical NTSC DVD subtitles are no longer included with the project files. DVD subtitles are still supported and can be created using the provided instructions.
• The cyrl-compat script was removed. It turns out it was not really necessary after all.
• Pre-built Windows utilities are now 64-bit executables
• Python scripts now require Python 3.4 or later
• As part of some general language code housekeeping, the language codes for Mandarin and Cantonese have been changed for consistency with the rest of the project. The “zho-” prefix has been dropped, and now these languages use the plain ISO-639-3 language code (cmn and yue, respectively).
• Most files that are not actually usable subtitles have been moved into the resources folder, and the resources folder is now better-organized
• Most folder names have been lowercased, to make things a little easier on people working with case-sensitive filesystems
• Some dubs currently have missing sections (due to damaged tapes or other factors). “Titles” subtitles for those languages now also subtitle those missing lines, whenever a text translation is available (currently only for Cantonese and Galician). If the missing sections in those dubs are ever restored, Project Threepio will update the “titles” subtitles to remove the redundant translations.
• Project Threepio’s extensive readme.html file has been given a visual overhaul to be less overwhelming to newcomers. It now uses expanding sections to display only the information you choose to see, rather than jumping to sections in one huge wall of text. It also now includes some command-builder scripts, so that you don’t have to hand-edit the commands to customize them for your needs. Displaying the file also now does not rely on any files from Project Threepio’s resources folder (i.e. images). This should help when Project Threepio is distributed in an incomplete form, which is a fairly common scenario – although you may still need some of those resource files to actually perform the tasks described in the documentation.
• The bidi-compat script has been improved to no longer require any text-specific workarounds for any existing Project Threepio subtitles. This increases the chances that it will produce good results out of the box with any future BiDi text.
• Potentially slow bulk image manipulation scripts now include progress indicators and spinner animations
• The project now includes a changelog (changes.html), including changes for every past release (thanks to pmc3)

PM sent.

Thank you Rondan!

Check your PM’s.

IIRC some degraining and regraining is necessary, not for meeting in the middle per se, but so that the grain characteristics of the various sources blend. i.e. you can’t just add fake grain to a degrained shot and necessarily expect it to blend with the natural grain of surrounding shots, not to mention how many shots contain multiple sources in a single frame.

Good to hear from you! Yes, I’m not knocking on every door/window just yet, but I’m still willing and able to put work into it as soon as we get the voice talent lined up.

I’m honestly seriously kinda hoping somebody named Hark Mamill or something like that stumbles across this thread and decides to give it a go. But I’m not gonna be picky.

PM sent.

PM sent.

PM sent. Speaking of stupid amounts of work, you ain’t seen nothing yet. 12.0 is going to be really over the top, but I’m still working on it.

There are SUP files for everything. PM sent.

PM sent.

PM sent.

PM sent.

PM sent.

If zofrex is still reading, the text renderer replacement script has hit a pretty important milestone. It’s now roughly as fast as, or maybe even slightly faster than, the current script (it’s a low bar, but I still want to clear it). This was done through multithreading (rendering multiple subtitle images at the same time), which really speeds things up, but multithreading can also lead to subtle errors, so I’m still bugchecking that right now. I think there’s a good possibility this new script may be usable before the next release, so it’s now possible 12.0 may include it. I’m also finding and fixing bugs in the current renderer as I go, but I’m not backporting the fixes. The only quirk right now is that Chromium-based browsers have a tendency to occasionally leave zombie processes running, so when you use Chromium to render an image a quarter of a million times*, you could see some performance fallout.

* And yeah, it doesn’t really work in reverse, where you can use one Chromium instance to render thousands of images. There’s a hard image size limit, and I could maybe squeeze more than one image into a render operation, but the added complexity isn’t worth the payoff.

PM sent.

PM sent.

PM’s sent, and thanks for the kind words!

ThrowMeTheWhip said:

Tantive3+1 said:

https://screenshotcomparison.com/comparison/9169

Not sure the point of downscaling 4K77 to 720p… not exactly a fair comparison.

This is a 4K83 comparison, but upscaling Despecialized to 4K works too – but it’s still not a fair comparison.

Left is Despecialized, right is 4K83.

Projection prints simply have less fine detail than negatives and interpositives, no matter what resolution you scan them at.

PM sent. Generally speaking, the subtitles are designed to accompany the English soundtrack. The Russian is pretty much directly from the Blu-ray subtitles, just retimed for the original versions. The translation may match one of the Russian dubs out there, but the timing probably isn’t right anymore since it was retimed to the English dialogue.

No, it’s a fair question. As far as I’ve been able to tell, per-glyph kerning rules (the sort that put a period closer to a lowercase r than to a lowercase m) are ignored by too much software to be certain of the result. Theoretically, yes, that’s exactly what they’re for. But in practice, you have to have a lot more control over the software than I do. My goal is to make a toolkit that people can run on god knows what software stack (and clearly we’re not there yet), and where I can swap out major software components with relative impunity (which is what I’m in the middle of).

Unicode’s Private Use Areas can be put to a similar purpose. They’re not unassigned – they’re reserved for custom glyphs like this, or in this case the same glyph with different spacing. And until this bug, I’d never encountered any software that behaved weirdly about them. In this case, ImageMagick’s “-gravity” option triggers text rotation for CJK vertical text layout, but for some reason it’s applying to the PUA as well.

If I was putting this out there as a general-purpose font, I’d probably do the kerning rules in addition to the PUA glyphs, but this is pretty purpose-built. I’m not expecting people to make their résumés in this font – and even if they did, the kerning changes are so minor they wouldn’t be noticeable outside the film context anyway.

This is far from the only weird problem I’ve encountered with the ImageMagick/Pango combo – I’ve been second-guessing the decision to go with that software for years (I’m not saying either Pango or ImageMagick are bad per se, just that the ImageMagick/Pango integration is problematic). So far, Chrome resolves all of those bugs (and yes, I’ve already tested the PUA support and many other things), but the Python itself is still way too buggy. Theoretically, once it’s working 100%, it could work in Chrome/Chromium/Safari/Opera/Edge, but right now, Chrome is all I’m focused on. I could even swap it for Firefox with a little more work. And, thanks to portable Chrome, it’s much, much easier to freeze at a particular version of Chrome indefinitely, should the features I’m relying on stop working for any reason. Basically this whole effort is designed to provide future insurance against exactly what’s happening now.

I was just kinda hoping nobody would trip over it until I was further along with a fix 😉

Thanks! I’m working on a terrible coding project right now, and either I won’t be able to focus on the new dubs right away, or I’ll be delighted to work on them right now instead of programming. I’m right on the edge 😉