new-lines in unicode subtitles

[hrglgrmpf]

Hello,

I'm using Bsplayer on my sister's computer to find out, if
my created OGM-files are playable on windows.

My system (debian gnu/linux) runs completely with unicode,
and I used ogmmerge
(http://www.bunkus.org/videotools/ogmtools/index.html)
to merge a divx-stream, two oggvorbis-streams, one chapter-file
and one SRT-subtitle file into one ogg-file ...

With mplayer the result is great, but Bsplayer draws only a box
instead of a new-line ... doesn't matter what character-set I select ...

could that be a bug in Bsplayer? I could put some example-movies
online, if someone is interrested.

sorry for my bad English

[Quietseb]

(I'm not 100% sure of what I write below)

I believe linux/unix systems usually use only Chr(10) as a line feed whereas many windows apps (e.g. notepad) require Chr(10)Chr(13)

Therefore these windows apps often don't read unix-produced text files correctly.
I believe some conversion utilities exist that will add theChr(13) when needed

otherwise it could be an improvement in bsplayer's subs display engine...

[hrglgrmpf]

hmm ...
unix uses "\n" (newline), dos uses "\r\n" (carriage return, newline)
(as far as I know)

but that is not responsable ... I converted my SRT-subtitle file into
the MicroDVD subtitle format, which uses "|" for newlines ...
with the same (bad) result.

The error must be in ogmmerge or in bsplayer ...

-----

I have uploaded some test-files (about 10 MB)
( http://www.hurg.org/bsplayer.tar.gz )

Bsplayer displays the subtitles correct, if they are read from an extern
file ... but if ogmmerge is buggy, why mplayer displays them right,
if they are in an ogm-file ?!

[hrglgrmpf]

Hello,

I wrote an email to the ogmmerge developer and he fixed this "bug" ...
Here is a part of the ChangeLog of the new version 1.0.0:

- Newlines in subtitles are converted to DOS style newlines (\r\n) as
some Windows players (e.g. BSPlayer) do not cope with a single \n.