Rewrote navigation code generator to support menus spread across multiple domains.

[videolink.git] / README

diff --git a/README b/README
index df6b8f72e48e7225f5df57af1e1b41cadc2cba72..fa2fdddf9828f85bb23237c50be013ded30c1175 100644 (file)
--- a/README
+++ b/README
@@ -42,10 +42,10 @@ below.
 Linking to video
 
 You can link directly to local MPEG video files whose names end in
-".vob".  If you wish to combine multiple files into a single video
-sequence ("title" in DVD terminology) or to add chapter marks to a
-video sequence, create and link to a VOB-list file (explained below)
-whose name ends in ".voblist".
+".mpeg", ".mpeg2" or ".vob".  If you wish to combine multiple files
+into a single video sequence ("title" in DVD terminology) or to add
+chapter marks to a video sequence, create and link to a VOB-list file
+(explained below) whose name ends in ".voblist".
 
 VOB-lists
 
@@ -135,9 +135,9 @@ multiple menus.  The frame size is dictated by the video standard; see
 above.  The exact visible area varies between TVs so the background
 should cover all or very nearly all the frame whereas the important
 content such as text must not be placed near the edge.  For this
-reason VideoLink applies a stylesheet to all pages that adds 60 pixels of
-padding on all sides of the body; this doesn't apply to the
-background.
+reason VideoLink applies a stylesheet to all pages that adds padding
+equal to 10% of the frame dimension on each side of the body; this
+doesn't apply to the background.
 
 Prior to version 1.8, Mozilla may signal that a page is completely
 loaded before any background images are loaded and displayed.  This
@@ -176,6 +176,38 @@ aspect ratio and sample rate.  However, each chapter will run into the
 next.  If this is a real problem, let me know, and I may be able to
 provide a better solution in a later version of VideoLink.
 
+Currently VideoLink code can generate up to 999 menus but it may be
+possible for me to raise this internal limit if you want more.  There
+appears to be an absolute limit of 12800 menus on a DVD.
+
+Bugs
+----
+
+Under Mozilla 1.7, VideoLink sets the assumed screen resolution to
+40 dpi, which I reckon to be the average resolution of a standard
+definition TV display.  This should mean that text with a font size
+expressed in millimetres or points will appear around the specified
+size.  Unfortunately this setting has a different effect under
+Mozilla/XULRunner 1.8:
+
+Mozilla   Assumed    Requested     Actual size
+version  resolution    size     (pixels) (inches)
+           (dpi)
+
+  1.7    default:96    20 px       20      0.5
+  1.7    default:96    36 pt       48      1.2
+  1.7        40        20 px       20      0.5
+  1.7        40        36 pt       20      0.5
+  1.8    default:96    20 px       20      0.5
+  1.8    default:96    36 pt       48      1.2
+  1.8        40        20 px       48      1.2
+  1.8        40        36 pt       48      1.2
+
+From version 0.10, until I have a proper solution, VideoLink will not
+set the assumed screen resolution under Mozilla 1.8.  I must advise
+against using font sizes in millimetres or points since they will vary
+between browser versions.
+
 Author and copyright
 --------------------