Is it just my browser or do the three competing formats listed by Wikipedia for coding timed text not all work? I stuck with the first and simplest format but I think the W3C TTML format would be useful in customizing the text position on screen. If anyone has any solutions or input, I am all ears. 4theloveofallthings ( talk) 20:18, 26 July 2023 (UTC)
 | This request for help from administrators has been answered. If you need more help or have additional questions, please reapply the {{admin help}} template, or contact the responding user(s) directly on their own user talk page. |
- Okay so I put {{db-author}} on the Timed Text page of this file because not only was the format not timing it correctly or effectively, but I was also the only contributor to the Timed Text page and figured I’d just have it removed.
- So someone comes along and does that, but for some reason on the file page the “timed text” link is still blue.. ? As if there is a page there. So I think this is why the file when played triggers a blank black screen to come ip rather than just playing the audio file and letting the reader continue to read the article. It’s very disruptive and was hoping someone could help remove the closed captions from this file entirely? I have no idea what to do in order to achieve that.
4theloveofallthings (
talk) 21:39, 31 July 2023 (UTC)
- It's pointless to have both help templates.
- I had never even heard of this namespace before, so here's my best guess. The Wikimedia software had to be jiggered to allow language-specific subtitles to be delivered up when a filename in the timed text namespace matches the name of a file in the file namespace. Creating a timed text file creates a hidden nexus by which the various language files are linked. So creating "Timed text:MetronomeTrailer.ogg" created both this hidden nexus and a "Timed text:MetronomeTrailer.ogg.en.srt" file with your English subtitles. Only the latter was deleted, but when you query anything about "Timed text:MetronomeTrailer.ogg" it acts as if a virtual redirect was found that combines the language code .en and the subtitle suffix .srt and tacks that onto the original filename and gives you the file data appropriate for that extended filename.
- Why it wasn't working for you and how an admin could remove the unwanted hidden nexus I don't know. I suspect you maybe could mostly solve your problem by MOVEing the file to a new name, severing the connection to the hidden nexus, but if the Wikimedia software also creates a new hidden nexus for the new name (much as how it creates a new talk page for a MOVE), that would not suffice either.
— jmcgnh
(talk)
(contribs) 06:18, 1 August 2023 (UTC)
- Well, I can’t say I didn’t expect the double tag comment, but at least you didn’t just say that alone and actually gave me useful advice. So I will take it. Someone saw my tag and rolled through to correct lint errors on the page and it frustrated me so I included both tags just in case someone knew the answer but was not an admin. Considering adding the other tag brought about a prompt reply from you — I will have to assume it served its purpose.
- It’s a glitchy and no-mans-land namespace that I thought I would try exercising the benefits of for one of the articles I had created. I love the idea of making audio on Wikipedia more accessible to hearing-impaired individuals, but it is so glitchy and so without guidance of any kind that upon trying to just remove the page, and successfully doing so.. it still causes a disruptive black screen to overtake a users entire field of view when trying to listen to audio.
- I will try moving the file as you very wisely suggested. I hadn’t thought of that. I appreciate that input.
- Thanks. 4theloveofallthings ( talk) 08:06, 1 August 2023 (UTC)
Is it just my browser or do the three competing formats listed by Wikipedia for coding timed text not all work? I stuck with the first and simplest format but I think the W3C TTML format would be useful in customizing the text position on screen. If anyone has any solutions or input, I am all ears. 4theloveofallthings ( talk) 20:18, 26 July 2023 (UTC)
| This request for help from administrators has been answered. If you need more help or have additional questions, please reapply the {{admin help}} template, or contact the responding user(s) directly on their own user talk page. |
- Okay so I put {{db-author}} on the Timed Text page of this file because not only was the format not timing it correctly or effectively, but I was also the only contributor to the Timed Text page and figured I’d just have it removed.
- So someone comes along and does that, but for some reason on the file page the “timed text” link is still blue.. ? As if there is a page there. So I think this is why the file when played triggers a blank black screen to come ip rather than just playing the audio file and letting the reader continue to read the article. It’s very disruptive and was hoping someone could help remove the closed captions from this file entirely? I have no idea what to do in order to achieve that.
4theloveofallthings (
talk) 21:39, 31 July 2023 (UTC)
- It's pointless to have both help templates.
- I had never even heard of this namespace before, so here's my best guess. The Wikimedia software had to be jiggered to allow language-specific subtitles to be delivered up when a filename in the timed text namespace matches the name of a file in the file namespace. Creating a timed text file creates a hidden nexus by which the various language files are linked. So creating "Timed text:MetronomeTrailer.ogg" created both this hidden nexus and a "Timed text:MetronomeTrailer.ogg.en.srt" file with your English subtitles. Only the latter was deleted, but when you query anything about "Timed text:MetronomeTrailer.ogg" it acts as if a virtual redirect was found that combines the language code .en and the subtitle suffix .srt and tacks that onto the original filename and gives you the file data appropriate for that extended filename.
- Why it wasn't working for you and how an admin could remove the unwanted hidden nexus I don't know. I suspect you maybe could mostly solve your problem by MOVEing the file to a new name, severing the connection to the hidden nexus, but if the Wikimedia software also creates a new hidden nexus for the new name (much as how it creates a new talk page for a MOVE), that would not suffice either.
— jmcgnh
(talk)
(contribs) 06:18, 1 August 2023 (UTC)
- Well, I can’t say I didn’t expect the double tag comment, but at least you didn’t just say that alone and actually gave me useful advice. So I will take it. Someone saw my tag and rolled through to correct lint errors on the page and it frustrated me so I included both tags just in case someone knew the answer but was not an admin. Considering adding the other tag brought about a prompt reply from you — I will have to assume it served its purpose.
- It’s a glitchy and no-mans-land namespace that I thought I would try exercising the benefits of for one of the articles I had created. I love the idea of making audio on Wikipedia more accessible to hearing-impaired individuals, but it is so glitchy and so without guidance of any kind that upon trying to just remove the page, and successfully doing so.. it still causes a disruptive black screen to overtake a users entire field of view when trying to listen to audio.
- I will try moving the file as you very wisely suggested. I hadn’t thought of that. I appreciate that input.
- Thanks. 4theloveofallthings ( talk) 08:06, 1 August 2023 (UTC)