I understand we should update the following page according to the currect implementation, http://www.mozilla.org/projects/intl/xprint/release.html
Assign to Roland.
Assignee: katakai → Roland.Mainz
QA Contact: Roland.Mainz → katakai
Wow... I never thought that there is such a page... :-) Any suggestions what we should include into that page ? Tobias/Jay ? Accepting bug...
Severity: enhancement → critical
Status: NEW → ASSIGNED
Priority: -- → P1
Hardware: PC → All
Summary: need to update release notes for Xprt → Need to update release notes for Xprint/Xprt
Target Milestone: --- → mozilla0.9.2
ToDo: - the URL should be http://www.mozilla.org/projects/intl/xprint/ - Add links to patches for Solaris 7/8 - Add links to X.org sources and instructions how to build libXp/Xprt binaries - Add links to Linux x86 Xprt binary + config tar.gz + RPM - Add comment that Xfree86 CVS and binaries build from it are broken - Xprint/Xprt FAQ - Mozilla Xprint module FAQ/troubleshooting - Add BugZilla query link to all open Xprint module bugs - Planns/Roadmap/Future of Xprint in Mozilla How can I modify the page without CVS access ?
Does anyone know how I can browse the CVS _dir_ for the xprint module docs ? http://lxr.mozilla.org/mozilla-org//html/projects/intl/xprint/ does not work... ;-( I'd like to know which files are "there" and what info they contain...
Summary: Need to update release notes for Xprint/Xprt → Need to update release notes for Xprint module/Xprt
CC:'ing endico to get some help with this issue...
pushing out. 0.9.2 is done. (querying for this string will get you the list of the 0.9.2 bugs I moved to 0.9.3)
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Uh... BAD. Retargeting to milestone 0.9.4... - but increating priority for this one.
Severity: critical → blocker
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Severity: blocker → critical
Target Milestone: mozilla0.9.4 → ---
Created attachment 47941 [details] cvs version 1.3 of mozilla-org/html/projects/intl/xprint/release.html
I am currently building a FAQ available under http://puck.informatik.med.uni-giessen.de/people/gisburn/work/xprint/Xprint_FAQ.txt Comments welcome...
How can get get checkin permission to the WWW docs at http://www.mozilla.org/ ?
Mozilla 1.0 already released. do we already has an updated Xprt release notes?
Arthit Suriyawongkul wrote: > Mozilla 1.0 already released. > do we already has an updated Xprt release notes? I am sorry, I do not have any Mozilla-specific yet. I have a FAQ (http://puck.informatik.med.uni-giessen.de/people/gisburn/work/xprint/Xprint_FAQ.txt) and some quickguides (http://puck.informatik.med.uni-giessen.de/people/gisburn/work/xprint/quickguide_hebrew_iso_8859_8.txt + http://puck.informatik.med.uni-giessen.de/people/gisburn/work/xprint/quickguide_koi8_r.txt). I started to hack a couple of new docs for Mozilla's Xprint module (mainly covering design) but I was servely hit by hordes of emails with questions, congratulations, suggestions, complains, bug reports (the Xprt binary tarball (e.g. fixed version of /usr/X11/bin/Xprt) for Linux x86 (http://puck.informatik.med.uni-giessen.de/download/xprint_linux_x86_006.tar.gz) was downloaded 3722 times since the release of mozilla 1.0 until today); in parallel I am working on http://xprint.mozdev.org/ (that's one step to contribute my Xprt (Xprint server side) fixes back to X.org), I am trying to give instructions to two other vendors who want to ship their own Xprt servers for their platforms, some new fixes for Xprt, a TrueType font engine and TrueType font download (e.g. Type42/Type11) and I am doing some development on Mozilla's Xprint module (see meta bug 149768 ("Make Xprint not suck in MachV/NS7"); the dependicies for this bug should be put into release notes for mozilla's Xprint module... they are all fixed in todays "trunk" and I hopefully get approval for 1.0.1 that we ship Netscape 7 with a perfectly working Xprint module). I wish someone would employ me for this stuff that I could spend more time into it...
thanks Roland, your FAQs really help :)
Arthit Suriyawongkul wrote: > thanks Roland, your FAQs really help :) Mhhh, thanks! :) Comments, contributions etc. for the FAQ/docs are welcome... BTW: You may try tomorrows "trunk" builds (or build from todays CVS) ... the fontmetrics code has been improved a lot in the last three days (see the dependicies in bug 149768). I've done some tests with a 100 DPI iso10646-1 BDF font and the results look (very) good (arabic, hebrew, thai, japanese, chinese etc.) ... :) =depends what you expect from a bitmap font... having TrueType iso10646-1 fonts and/or PS Type1 fonts (for specific encodings like hebrew) gives far better results (however my Linux Xprt does not support TrueType yet)
endico: Requesting permission for creating a new dir under mozilla-org/html/projects/xprint (Xprint module has grown beyond the "intl" area) and build a whole new set of docs there, please ?
go ahead with mozilla-org/html/projects/xprint. Add an item for it in mozilla-org/html/index.html with a short description of the project.
I am mainly "done" with creating the first version of the new Xprint module pages under http://www.mozilla.org/projects/xprint/ - comments/feedback/rants/etc. very welcome... :)
Any work is going on here or can the bug get closed?
Hi Henrik, Yes, could you please close this bug report. Thank you!!
Closing bug as WONTFIX.
Status: ASSIGNED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.