| Summary: | Support for SAMI/.smi subtitles | ||
|---|---|---|---|
| Product: | [Applications] subtitlecomposer | Reporter: | Jonathan Joseph Chiarella <j_j_chiarella> |
| Component: | general | Assignee: | Mladen Milinkovic, Max <maxrd2> |
| Status: | CONFIRMED --- | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version First Reported In: | 0.7.1 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
SAMI/.smi subtitle (UTF-8) #1
SAMI/.smi Subtitle (UTF-8) #0 SAMI/.smi Subtitle (UTF-8) #2 SAMI/.smi Subtitle (UTF-8) #3 SAMI/.smi Subtitle (UTF-8) #4 SAMI/.smi Subtitle (UTF-8) #5 |
||
|
Description
Jonathan Joseph Chiarella
2023-01-04 06:02:52 UTC
Thanks for the report. I didn't know SAMI had so much adoption so never gave it a priority. Once the current WebVTT and CSS support/work is done, should be trivial to fully support SAMI subtitle format. > I didn't know SAMI had so much adoption ... I do remember it not long after it first came out. It was rolled out in 1998/1999, and I occasionally saw it alongside .srt in the very early 2000s (no one was sharing much content over dial-up in the early 1990s). It basically seemed to disappear a few years later. I think for Korea, the Windows-only freeware programs (GOM Player and Daum's Pot Player, formerly "KMPlayer" or "Kang Multimedia Player") supporting SAMI/.smi out of the box was a key part of it. In the early 2000s, many players still had hiccups with the SAMI/.smi format. Remember that on Windows, VLC was not yet a thing and even when it was, it spent several years being a distant third to Media Player Classic and KMPlayer, which came out even earlier. (Additionally, VLC did not properly show SAMI/.smi subtitles until after the format had all but disappeared from several countries, including its point of origin, America.) If you wanted to play DVDs or video files without stuttering, then having a player like KMPlayer was a godsend. KMPlayer spread by word of mouth. GOM Player (which was not quite as good overall, but had some exclusive features and a company backing it) hosted subtitle repositories on its website. The result was that every Korean had one or the other installed in the early 2000s and SAMI/.smi has been entrenched ever since. > Once the current WebVTT and CSS support/work is done, should be trivial to fully support SAMI subtitle format. Thank you kindly. I will upload some sample subtitle files as attachments. You can put them with any old video file to test them. Created attachment 155030 [details]
SAMI/.smi subtitle (UTF-8) #1
Created attachment 155031 [details]
SAMI/.smi Subtitle (UTF-8) #0
Created attachment 155032 [details]
SAMI/.smi Subtitle (UTF-8) #2
Created attachment 155033 [details]
SAMI/.smi Subtitle (UTF-8) #3
Created attachment 155034 [details]
SAMI/.smi Subtitle (UTF-8) #4
Created attachment 155035 [details]
SAMI/.smi Subtitle (UTF-8) #5
To say that SAMI/.smi is alive and well is an understatement. You see it in multiple languages for Korean and foreign content and subtitles in multiple languages ... at GOM: <https://www.gomlab.com/subtitle/> and at Cineaste: <https://cineaste.co.kr/bbs/main.php?gid=psd>; both of these websites aim at the Korean market and are on Korean websites. The GOM site, to its credit, is a bit bilingual/English-friendly, but beware of broken English, corrupted characters, etc. on the site. (China, Korea, and Japan are the world'sholdouts against Unicode everywhere, with some justification, of course. You will run across about 5% of their websites being not in Unicode or in poorly engineered Unicode. To make things easier, I converted the sample SAMI/.smi subtitle I attached into UTF-8. Most of the time they will be in plain ASCII or in UHC encoding.) I have even seen the occasional SAMI/.smi pop up on SubScene, too: <https://subscene.com/>. |