From sandram at boi.hp.com Tue Jan 12 18:12:15 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> subgroups Message-ID: <01BE3E46.529B60E0@hpb13858.boi.hp.com> Hi All, At the last meeting we spoke about defining subgroups to concentrate on the investigation / definition of the UPDF. Some obvious groups are User Interface and localization; Fonts; Rendering; dynamic configuration and transport of UPDF across networks. Any other suggestion? Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Tue Jan 12 18:16:13 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> agenda for Monday Message-ID: <01BE3E46.E0C089E0@hpb13858.boi.hp.com> Here's a prelim agenda for Monday's meeting in Hawaii. Please send me suggestions for more items to discuss. Also if people know anything about XML and want to share - that would be great. 8:30 - 9:00am Intros and misc. 9:00 - 10:00am Requirements 10:00 - 11:30am Apple presentation 11:30 - 1:00pm Lunch 1:00 - 1:30pm subgroups 1:30 - 2:00pm use cases 2:00 - 3:30pm XML stuff ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Wed Jan 13 13:59:13 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> minutes and misc posted to ftp site Message-ID: <01BE3EEC.2428A500@hpb13858.boi.hp.com> Hi, I've posted minutes from the last meeting to the ftp site. I also posted Adobe's Job Ticket spec to Archive/Specs and pdf versions of the presentations to Archive/1998. I'm still working on converting Bill Wyman's Job ticket presentation to pdf format. I am also working on the UPDG web page and I should post a current word format of the requirements doc tomorrow. Did I forget anything? If you are expecting more - let me know what you would like posted. thanks, Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From nschade at xionics.com Thu Jan 14 11:59:14 1999 From: nschade at xionics.com (NSchade) Date: Wed May 6 14:04:47 2009 Subject: UPD> subgroup proposals Message-ID: <001201be3fdf$3749e880$1c1343ce@nschade.xionics.com> Hi all, I worked on collecting some stuff the last weeks. So I'd like to make a proposal for subgroups, which is filled with some life already. There are some basic topics, which are listed below: 1. I distinguish between some levels of work. This affects the rights of subgroups, too. I do not think that the complete plenum wants to decide on each and every byte of the format. The levels are Conceptional work, Architectural work, Structural work, Functional work. 1.1. Conceptional work Discussed and decided in the plenum. Some topics are Unicode for UI and printing, definition of all numeric values in virtual units and a sophisticated parameter converter used within command sequences. 1.2. Architectural work Discussed and decided in the plenum. Some topics are to think as modular as possible, global filter functionality including constraints and error messages, global identifyers for ALL modules. The use of global identifyers is very obvious in paper size handling. There should be a number of predefined identifyers for all device descriptions (Letter=1, A4=2, etc.), a reversed area or proprietary definitions used company wide by printer manufacturers and a reserved area for user defined defintions. This architecture is useful for all modules. We will also discuss the overall architecture to be able to define mandatory modules and a proper way to include proprietary modules in this open structure. 1.3. Structural work Decided in the plenum. Discussed in the subgroups. Mandatory modules and predefined values are developed here. 1.4. Functional work Discussed and decided in the subgroups. In order to function correctly some assumptions must be made. The details should be work out in the subgroups with the detailed understanding. 2. Some assumptions have to be made. 2.1. Driver assumptions Although the driver is out of scope we have to consider how it will work. Otherwise our description is useless. Some topics are support of vector graphics, support of overlays/watermarks and the way the spooler works. The driver may maintain three sets of features (Device properties, Application defaults, Job settings). 2.2. Tooling assumptions For all the boring and time consuming repeating stuff we should think about tools and their development. I really would like to see a driver, which allows easy translation. We may seriously recommend functionality to switch the driver to a translation mode (perhaps with an additional library) to allow editing in the dialog. We may think about short cut handling. 2.3. Operating system assumtions The OS may offer some global strings like for paper sizes in various languages or pictures like for duplex modes. We have to clearly find out what we can expect concerning dialog handling. We have to know how to detect character sets info. The OS may offer lists for composed characters. The OS may offer a list of paper sizes concerning dimensions. 3. We have to decide in detail what is Out of scope at least for version 1 of the format. Some topics may be Workload balance, Application workarounds, Paper preview, Printer preview, Subdialogs. We may extend the list during development. Based on that we may define some subgroups. I'd like to see Global decisions, User interface and Localization, Paper handling, Fonts, Color, Configuration and Communication. 1. Global decisions This is a quite big group. We may split it. Some topics may be the General model description (somehow a tree), Global flags (like the exact printer language level), Optional units (input, output, duplex, RAM, ROM font cartriges, Flash ROM, Hard disks and all kinds of combinations), Positioning, Raster graphics (rendering), Memory, Overlays/Watermarks, Driver sets (Global sets, Job settings, MasterPages), Print file structure (Job Start/End, Page Start/End, Download, Overlays/Watermarks). 2. User interface and Localization Some topics are AVD (automatic version detection), Human languages, Icons/Pictures, Defaults (ranking including fallback mechanisms), UI structure, UI element description (minimum for global, extended for proprietary), String length limitations (you cannot show a paper size with 50 characters, OS specific), Short cuts, Balloon help. 3. Paper handling Some topics may be Size, Minimum margins, Orientation (these three build the minimum set of the seven values), N-up/Booklet, Logical/Physical zooming, Input, MediaType, Output, Copies including Collation. 4. Color Including halftoning. Not yet elaborated. 5. Configuration and Communication Some topics are Networking, Bidirectional communication, Model timings, PnP ID, Check sum for high speed bidi. Not yet elaborated. As you can easily see I want to come to something we can hold in our hands as soon as possible and let the spec grow during development. Regards Norbert From surfchina at gserver.com Mon Jan 18 03:22:36 1999 From: surfchina at gserver.com (Surf China) Date: Wed May 6 14:04:47 2009 Subject: UPD> SurfChina.com - Search Engine for China Message-ID: <199901180822.BAA10673@gserver.com> Dear friend, Do you ever wonder where to find information about China? Well, wonder no more. Come check out SurfChina.com (http://www.surfchina.com), the BEST SEARCH ENGINE for China. SurfChina.com's database consists of thousands of China, Chinese related web sites, all sites are carefully categorized into over 300 categories, which makes search very easy. New sites and categories are added everyday. You can find Chinese companies, Chinese culture sites, travel agencies, employment opportunities, Chinese newspapers, and much, much more. Take a look for yourself, and tell a friend about SurfChina.com, so everyone can take advantage of this wonderful resource. SurfChina.com also provides China statistical information service. We work directly with the State Statistical Bureau of China to provide the latest, the most accurate, and most authritative China statistical data for our clients. To find out more about this service, please visit http://www.surfchina.com/stats/ Sincerely yours, SurfChina.com team From sandram at boi.hp.com Fri Jan 29 15:23:06 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: No subject Message-ID: <01BE4B8A.82347AC0@hpb13858.boi.hp.com> Hi All, At the last UPDF meetings we decided to have a bi-weekly phone conference to discuss the subgroups. The phone number for our phone conference is 612-315-6802 The access code is 058459494 I will activate the number on Feb 2 from 10-12 Pacific time. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From nschade at xionics.com Mon Feb 1 09:34:11 1999 From: nschade at xionics.com (NSchade) Date: Wed May 6 14:04:47 2009 Subject: UPD> draft samples for UPDF sections Message-ID: <001001be4def$ef7fb880$1c1343ce@nschade.xionics.com> All, I feel we should work on something real when discussing the UPDF spec, the sections we implement, other printer descriptions used as a base and the defintion of subgroups. I hope the attached four ASCII files (Windows International char set) are helpful showing the differences we have to deal with and ways to go. These are two descriptions (Paper source and Power save), each provided one general and once filled with parameters. I did not care about syntax. I did not care about a real structure. I did not care about completeness or perfect correctness. My major concern was to start a discussion about an open structure (you can add proprietary sections and/or delete optional sections without injuring the format). Some details are that the short cuts are not included in the string (like an ampercent) to ease translations or to rank elements of a module per language to provide an easy fallback mechanism for defaults. Xionics will be participating with some people in tomorrow's teleconference. We may refer to these documents. If I am not clear enough in some areas, please ask me directly for further explanations. Regards Norbert -------------- next part -------------- Legend ModuleClassifications M_ // mandatory, predefined by UPDF // must be supported O_ // optional, predefined by UPDF // can be supported P_ // optional, proprietary, defined by manufacturer // can be supported ParameterClassifications G_ // global, predefined by UPDF // the first 500 reserved P_ // proprietary, defined by manufacturer // the second 500 reserved U_ // user defined // the third 500 reserved This module is called ID_PaperSource with all the available input trays as elements. Some descriptions are general for the module. Later you see those descriptions specific to each element of the module. The general descriptions of this module are: M_Basics O_Comment M_PrinterConnector O_OwnsElements O_ElementsPaperSource M_Dialog M_Style M_Attributes M_Margins M_Left M_Right M_Top M_Bottom M_StoreData M_MemberOfSet M_MemberOfGroup M_RelatedToElement M_Position // relative to M_RelatedToElement M_Horizontal M_Vertical M_ElementTitle M_Style M_Margins M_Left M_Right M_Top M_Bottom M_Attributes M_Position M_Horizontal M_Vertical M_Language // per Language O_BalloonHelp // per Language O_Help O_CheckRelatedElementSizes O_Preview O_ElementImage FunctionCall M_Functions Init CallBack1 O_Communication O_Errors O_Event O_Message // per Language O_Config O_JobStatus These are the element specific descriptions: O_ElementsPaperSource M_ElementBasics O_ElementComment // per Element M_TechnicalElementID // per Element M_ValueLimitations M_MinimumWidth // per Element unit: mm/10 M_MaximumWidth // per Element unit: mm/10 M_MinimumLength // per Element unit: mm/10 M_MaximumLength // per Element unit: mm/10 O_LeftOffset // per Element unit: mm/10 O_RightOffset // per Element unit: mm/10 M_Ranking // per Language M_ElementLanguage // per Element per Language O_Preview O_PaperPathPreview FunctionCall sample parameters: FeedingAngle FrontPage O_PrinterConfigPreview FunctionCall sample parameters: ImageSelected ImageDeselected M_Print O_SequenceJobHeader O_Ranking O_Redundancy O_SequenceJobTrailer O_Ranking O_Redundancy O_SequenceJobStart // after JobHeader O_Ranking O_Redundancy O_SequenceJobEnd // before JobEnd O_Ranking O_Redundancy O_SequencePageStart O_Ranking O_Redundancy O_SequencePageEnd O_Ranking O_Redundancy O_Filters O_ActiveFilters sample parameters: FeedingAngle, ID_PaperSize, ID_HWMargins // combined filter O_Condition O_Message // per Language ID_PrintMedia O_Condition O_Message // per Language ID_Duplex O_Condition O_Message // per Language O_PassiveFilters sample parameters: ID_InputOptions O_Message O_Communication O_Errors O_Event O_Message // per Language O_Config -------------- next part -------------- ID_PaperSource Sample for 2 human languages (US English, German), 2 elements (Tray 1, Manual) M_Basics O_Comment Paper sources of model Sirius M_PrinterConnector Connected to the lower connector, the same connector is provided at its bottom for other paper sources O_OwnsElements O_ElementsPaperSource M_Dialog M_Style Combo box with max 5 entries at a time M_Attributes Change to static text control, if 1 entry M_Margins // around the combo box M_Left 5 pixel M_Right 5 pixel M_Top 5 pixel M_Bottom 5 pixel M_StoreData dmDefaultSource M_MemberOfSet QuickSets M_MemberOfGroup TabGroup_Paper M_RelatedToElement ID_PaperSize M_Position M_Horizontal Same M_Vertical Down O_CheckRelatedElementSizes ID_PaperSize M_ElementTitle M_Style StaticText M_Margins // around the text prompt M_Left 5 pixel M_Right 5 pixel M_Top 5 pixel M_Bottom 5 pixel M_Attributes Short cut M_Position M_Horizontal Left M_Vertical Same M_Language US English: Paper Source (7), German: Papierschacht (7) // the bracket shows the short cut position within the string O_BalloonHelp US English: Select a paper source. German: Waehlen Sie einen Schacht aus. O_Help HLP_PaperSource // entry point for the help fle O_CheckRelatedElementSizes ID_PaperSize /* This dialog section says that paper source is to be shown within the Paper tab below the paper size control, not smaller than the paper size control. Paper source is to be provided as a combo box with the prompt left to it, no small picture next to the control. A margin of 5 pixel shall be used around the combo box as well as around the text. */ M_Functions Init use standard initialization O_ElementsPaperSource M_ElementBasics O_ElementComment Tray 1 of Sirius M_TechnicalElementID Input1 // predefined M_ValueLimitations M_MinimumWidth 1000 unit: mm/10 M_MaximumWidth 2159 unit: mm/10 M_MinimumLength 1000 unit: mm/10 M_MaximumLength 3556 unit: mm/10 M_Ranking US English: 1 German: 2 M_ElementLanguage US English: Tray 1 German: Schacht 1 O_Preview O_PaperPathPreview FunctionCall sample parameters: FeedingAngle the feeding angle for the selected paper size FrontPage Face down O_PrinterConfigPreview FunctionCall sample parameters: ImageSelected BMP_Highlight_Tray1 ImageDeselected BMP_Tray1 M_Print O_SequencePageStart esc & l 1 H O_Ranking as second command sequence at page start O_Redundancy only to be sent, if different O_SequencePageEnd FormFeed O_Ranking as first command sequence at page end O_Redundancy Sent always O_Filters O_ActiveFilters FeedingAngle, ID_PaperSize, ID_HWMargins List O_Condition Short-edge, Letter, each min margin = 75 Short-edge, A4, each min margin = 71 O_PassiveFilters // passive filters are acceleration fields ID_InputOptions List // automatically filled by definition of active filters //of ID_InputOptions M_ElementBasics O_ElementComment Manual Tray of Sirius M_TechnicalElementID Manual // predefined M_ValueLimitations M_MinimumWidth 1000 unit: mm/10 M_MaximumWidth 2970 unit: mm/10 M_MinimumLength 1000 unit: mm/10 M_MaximumLength 4200 unit: mm/10 M_Ranking US English: 2 German: 1 M_ElementLanguage US English: Manual German: Manuell O_Preview O_PaperPathPreview FunctionCall sample parameters: FeedingAngle the feeding angle for the selected paper size FrontPage Face down O_PrinterConfigPreview FunctionCall sample parameters: ImageSelected BMP_Highlight_Manual ImageDeselected BMP_Manual M_Print O_SequencePageStart esc & l 2 H O_Ranking as second command sequence at page start O_Redundancy only to be sent, if different O_SequencePageEnd FormFeed O_Ranking as first command sequence at page end O_Redundancy Sent always O_Filters O_ActiveFilters FeedingAngle, ID_PaperSize, ID_HWMargins List O_Condition Long-edge, Letter, each min margin = 75 Long-edge, A4, each min margin = 71 Short-edge, A3, each margin = 71 O_PassiveFilters // passive filters are acceleration fields ID_InputOptions List // automatically filled by definition of active filters //of ID_InputOptions -------------- next part -------------- Legend ModuleClassifications M_ // mandatory, predefined by UPDF // must be supported O_ // optional, predefined by UPDF // can be supported P_ // optional, proprietary, defined by manufacturer // can be supported ParameterClassifications G_ // global, predefined by UPDF // the first 500 reserved P_ // proprietary, defined by manufacturer // the second 500 reserved U_ // user defined // the third 500 reserved This module is called ID_PowerSave just with 2 settings as elements. Some descriptions are general for the module. Later you see those descriptions specific to each element of the module. The general descriptions of this module are: M_Basics O_Comment O_OwnsElements O_ElementsPowerSave M_Dialog M_Style M_Attributes M_Margins M_Left M_Right M_Top M_Bottom M_StoreData M_MemberOfSet M_MemberOfGroup M_RelatedToElement M_Position // relative to M_RelatedToElement M_Horizontal M_Vertical M_ElementTitle M_Style M_Margins M_Left M_Right M_Top M_Bottom M_Attributes M_Position M_Horizontal M_Vertical M_Language // per Language O_BalloonHelp // per Language O_Help O_CheckRelatedElementSizes O_Preview O_ElementImage FunctionCall M_Functions Init CallBack1 O_Communication O_Errors O_Event O_Message // per Language O_Config O_JobStatus These are the element specific descriptions: O_ElementsPowerSave M_ElementBasics O_ElementComment // per Element M_TechnicalElementID // per Element M_Ranking // per Language M_ElementLanguage // per Element per Language M_Print O_SequenceJobHeader O_Ranking O_Redundancy O_SequenceJobTrailer O_Ranking O_Redundancy O_Filters O_ActiveFilters O_PassiveFilters sample parameters: ID_Model O_Message O_Communication O_Errors O_Event O_Message // per Language O_Config -------------- next part -------------- ID_PowerSave Sample for 2 human languages (US English, German), 2 elements (On, Off) M_Basics O_Comment Power save modes of model Sirius O_OwnsElements O_ElementsPowerSave M_Dialog M_Style Combo box with max 2 entries at a time M_Attributes Change to static text control, if 1 entry M_Margins // around the combo box M_Left 5 pixel M_Right 5 pixel M_Top 5 pixel M_Bottom 5 pixel M_StoreData XDMPowerSave M_MemberOfSet QuickSets M_MemberOfGroup TabGroup_PermanentSettings M_RelatedToElement zero // This is the first element in the group M_Position M_Horizontal Left M_Vertical Top O_CheckRelatedElementSizes zero // ignore all other controls in this dialog for the size // of this control M_ElementTitle M_Style StaticText M_Margins // around the text prompt M_Left 5 pixel M_Right 5 pixel M_Top 5 pixel M_Bottom 5 pixel M_Attributes Short cut M_Position M_Horizontal Left M_Vertical Same M_Language US English: Power Save (1), German: Sparmodus (2) // the bracket shows the short cut position within the string O_BalloonHelp US English: Select the power save mode. German: Waehlen Sie den Sparmodus. O_Help HLP_PowerSave // entry point for the help fle O_CheckRelatedElementSizes zero O_Preview O_ElementImage BMP_PLUG FunctionCall /* This dialog section says that power save is to be shown within the Permanent settings tab at the upper left corner. Power save is to be provided as a combo box with the prompt left to it, a small picture of a plug next to the control. A margin of 5 pixel shall be used around the combo box as well as around the text. */ M_Functions Init use standard initialization O_ElementsPowerSave M_ElementBasics O_ElementComment Power save on M_TechnicalElementID ON // predefined M_Ranking US English: 1 German: 2 M_ElementLanguage US English: On German: An M_Print O_SequenceJobHeader @PJL SET POWERSAVE=ON O_Ranking as third command sequence in job header O_Redundancy sent always O_Filters O_PassiveFilters // passive filters are acceleration fields ID_Model List // automatically filled by definition of active filters //of ID_Model M_ElementBasics O_ElementComment Power save off M_TechnicalElementID OFF // predefined M_Ranking US English: 1 German: 2 M_ElementLanguage US English: Off German: Aus M_Print O_SequenceJobHeader @PJL SET POWERSAVE=OFF O_Ranking as third command sequence in job header O_Redundancy sent always O_Filters O_PassiveFilters // passive filters are acceleration fields ID_InputOptions List // automatically filled by definition of active filters //of ID_InputOptions From nschade at xionics.com Mon Feb 8 05:12:18 1999 From: nschade at xionics.com (NSchade) Date: Wed May 6 14:04:47 2009 Subject: UPD> conclusion of last teleconference Message-ID: <001701be534b$826ebaa0$1c1343ce@nschade.xionics.com> All, I'd like to put some info together to remember the discussion and probably make some decisions. Statements to be decided: 1. Virtual units Every UPDF has a basic field ID_M_VirtualUnit. Sample parameter: 7200. Conceptional idea: The universal driver will work with this virtual unit for most of the variable parameters for print output without further caring for resolutions in the UPDF. Sample 1: Horizontal positioning Target: To be able to define formulas, which generally tell about the specific unit to calculate in. The formulas will be handled by a driver routine called ParameterConverter (quite simple routine). Sample formula for horizontal positioning (final syntax to be agreed on): esc * p formula(ID_M_HorizontalPosition * ID_M_DeviceResolution / ID_M_VirtualUnit) X Rounding and truncating to be discussed. Print output: correct positioning command sequence for the current device resolution in consistent units overall the complete driver. Can be reused for future models, which may even work in higher device resolutions. Sample 2: Specification of width values for bitmap fonts Sampe char: "A" Assumption: the width of "A" is 20 pixel in 300 dpi Specified value in UPDF: 480 (comment: 7200 / 300 = 24). Advantage: 480 virtual units are valid for each device resolution (300 dpi, 600 dpi, even future resoutions). Conclusion: This would unify a lot of parameter specifications. A universal driver can nearly always think in virtual units. The implementation of future models with higher resolutions saves a tremendous time. If the parameter spec is correct once, it must be correct for other future device resolutions working with the same virtual unit. This will dramatically decrease test and maintenance effort. 2. ID-classification Sample ID's: ID_M_VirtualUnits, ID_M_HorizontalPosition, ID_M_PaperSource, ID_M_PaperSize, ID_O_PrintMedia, ID_P_HolePunching Legend: M_ Mandatory. This ID is necessary to establish a correctly working universal driver. The list will be defined by UPDF. O_ Optional. This ID is not necessary to establish a correctly working universal driver. One universal driver on one operating system may support it, another driver on another operating system may not yet support it. The ID may not be supported by any universal driver yet. But it will make driver extensions more reliable. It will encourage universal driver developers to support more optional ID's. The list will be defined by UPDF. It may grow from time to time. Optional ID's may be supported by one, some or all universal drivers. P_ Proprietary. This ID may only be supported by proprietary drivers, probably developed by a printer manufacturer while implementing the rules of UPDF. This will be defined by e.g. a peripheral manufacturer. A universal driver may support this control without knowing what it means, if it is a simple toggle or something similar. Conclusion: This is not really changing the way a universal driver will work, but it makes it easier to write a UPDF looking at some lists. Xionics' requirement: UPDF must be an open standard to allow proprietary solutions while following the standard rules of UPDF. We do not assume that the universal driver provided by every operating system fulfilles all necessities of Xionics from beginning on. We think this will heavily improve the acceptance of UPDF. 3. Parameter classification Sample ID: ID_M_PaperSize Sample parameters: Parm_G_Letter, Parm_G_A4, Parm_O_A5, Parm_P_CompanyXYZFormat1, Parm_U_UserDefined1 Legend: G_ Global. This parameter will be detected by every universal printer driver. A side effect may be that the UI strings for those parameters may be provided by the operating system to ensure consistent UI strings throughout all drivers. A side effect may be that values for paper width and length may be provided by the operating system to ensure consistent values thtoughout all drivers. The list will be defined by UPDF. We will define a range big enough for future extensions. O_ Optional. This list will be defined by UPDF. It is not ensured that a paper size with an optional parameter will be supported by an operating system global UI string or global values. We will define a range big enough for future extensions. If an optional parameter proves its worldwide use over the times, it will be the target to move more of these to the global list, until the global list is somehow complete. P_ Proprieatary. This parameter may be defined by e.g. a printer manufacturer. It is not ensured that a document saved with a proprietary parameter for paper size will be detected later by another UPDF, although the other one may support the same physical paper size, but with a different parameter. Proprietary parameters may move to the optional list after having proven its reliability and necessity. UPDF will define a range for this list, but not the list itself. U_ User defined. This list is not predefined at all. UPDF will define a range for this list. These are reserved parameters for paper sizes defined by the end user, if a certain paper source allows that. Conclusion: I can imagine numeric values or alphanumeric values. 4. Tree structure of UPDF One UPDF will define one model. The UPDF is somehow a tree. I can well imagine several hierarchic levels (e.g Fonts may be listed on level 1, while the font attributes, which assemble a font, will be listed on level 2). The universal driver will detect ID's by its name and may jump over ID's, which definition it cannot completely support. This is the concept of an open format. It allows to add branches to the tree without injuring correct functionality of other branches. 5. Unique and central definition per module All specification is only done once. A module like a paper source ID is specified in one block with all components. 5.1. A module may have a basic component. 5.2. A module may have a dialog component. 5.3. A module may have a print component. 5.4. Function call backs like initialization or specific functionality may be a separate component or to be handled within the other components. 5.5. Other components to be discussed. Samples: ID_M_PaperSource and ID_M_PaperSize are typical modules for 5.1. (owns a list of paper sources), 5.2. (is represented in the dialog) and 5.3. (some bytes have to be sent to the device). A general printer language init (esc E) is a typical module for 5.3., but not necessarily for 5.1. and normally not for 5.2. A group box is a typical module for 5.2., but not necessarily for 5.1. and definitely not for 5.3. 6. Default driver settings A standard problem of multilingual drivers provided for different derivates of operating systems (International, East European, Arabic, Japanese, etc.) is the default setting. Standard problems to be solved for a universal driver are that not all parameters are supported by some operating systems (e.g. Graphic modes like Raster and GL/2 in PCL5e). As we do not want to specify operating system specific defaults, we need a kind of a fallback, which allows the definition of priorities. Countries may require different defaults (e.g. Letter size for US, A4 for Europe). A fallback mechanism may even help in this case. A ranking has to be defined per country/language, which allow the global default specification for each module per each country/language, even if some elements may not be available under certain operating systems or certain configurations. We may think about grouping countries/languages to bigger groups like Europe to avoid to many listings. Feedback appreciated. Sandra, as these items are basic conceptional decisions, they must be clear right from beginning. Perhaps we can agree on that in Miami. Regards Norbert From sandram at boi.hp.com Wed Feb 24 15:00:47 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> minutes Message-ID: <01BE5FF5.B31E82A0@hpb13858.boi.hp.com> Hi All, I've copied the minutes from the last meeting to the web page and archive. I've also copied electronic versions of the presentations. They are at www.pwg.org/updf/index.html Let me know if you want anything else copied. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Wed Feb 24 15:11:06 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> subgroups for UPDF Message-ID: <01BE5FF7.23AF3B80@hpb13858.boi.hp.com> Hi All, I'm assuming we still want to create subgroups for UPDF Spec definition. I would like to elicit feedback on how to proceed. The following subgroups are defined: 1. Global 2. Font handling 3. Paper handling 4. Color handling 5. Localization 6. Communication 7. User Interface 8. Callback mechanism 9. Device capabilities 10. PDL It seems to me first we should all work on the Global and decide what goes into the Global and also set the rules (ie syntax req., guidelines, and so on) for the subgroups. We should spend some time in Miami to hammer this out. When exactly do the subgroups meet? I prefer Wed and Thur. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From mattsf3 at ix.netcom.com Fri Feb 26 13:02:42 1999 From: mattsf3 at ix.netcom.com (mattsf3@ix.netcom.com) Date: Wed May 6 14:04:47 2009 Subject: UPD> Warning! meeting charges Message-ID: <199922610461641@ix.netcom.com> Hi All, I was just informed by the marriott that they will not accept individual credit cards. I am paying for the meeting on my AmEx. People will have to pay Brian Batchelder on Monday, Tuesday, and Wednesday by check or cash. On Thursday and Friday, I will be there so you can pay me. If you write a check, please make it out to "Sandra Matts" The meeting charges are $38 / day. Sorry for the inconvenience. If you don't have checks or cannot get enough cash, give me or Brian Batchelder your name and company and you can pay me later in the month. Sandra Matts From sandram at boi.hp.com Tue Mar 2 10:32:14 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> phone conference Message-ID: <01BE6487.2D805420@hpb13858.boi.hp.com> Hi, I've received questions on whether there is a call today or not. I believe there is no call scheduled during the PWG week. I will send out emails before the next one. Here's March's schedule: March 9 and 23rd Pacific time 10-12 (Tuesdays) Phone number is: 612-315-6802 Access code is: 687920064 Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Wed Mar 10 12:15:53 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> phone conf Tuesday 3-16 Message-ID: <01BE6ADE.FB9E6BA0@hpb13858.boi.hp.com> Hi All, At the last meeting the UPDF group decided to have the phone call Tues 3-16 instead of 3-9. I apologize for the last minute notice - my son has been sick and this is my first day at work. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From sandram at hpbs1061.boi.hp.com Wed Mar 10 13:51:07 1999 From: sandram at hpbs1061.boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> phone conference Message-ID: <9903101851.AA00644@hpbs1061.boi.hp.com> Hi, It was decided at the last UPDF meeting to have the phone call on Tues. 3-16 10-12 pacific. Sandra Matts From sandram at hpbs1061.boi.hp.com Wed Mar 10 18:05:55 1999 From: sandram at hpbs1061.boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> my email address Message-ID: <9903102305.AA01367@hpbs1061.boi.hp.com> Hi, For some reason my current email address is not functioning so I have not received any email for the last three days. If you have sent me any email please resend to sandram@hpbs1061.boi.hp.com. I will let you know when my real email (sandram@boi.hp.com) is working. thanks, Sandra Matts From sandram at hpbs1061.boi.hp.com Wed Mar 10 18:29:47 1999 From: sandram at hpbs1061.boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> UPDF spec Message-ID: <9903102329.AA01436@hpbs1061.boi.hp.com> Hi, I've copied the UPDF Spec version 0.4 to ftp://ftp.pwg.org/pub/pwg/upd/Archive/Specs. There are several files: UPDF Functional Specification.doc Updf.dtd cmfp.xml Sandra Matts From Michael_Yeung at cissc.canon.com Wed Mar 10 18:38:51 1999 From: Michael_Yeung at cissc.canon.com (Yeung, Michael) Date: Wed May 6 14:04:47 2009 Subject: UPD> XML Editors Message-ID: > URL Links for XML editor > > > "XML 1.2 - Demo Version" > Vervet Logic > http://www.vervet.com/ > go! XML Pro Demo Download > > "XML NotePad > Microsoft > http://www.microsoft.com/workshop/c-frame.htm#/xml/default.asp > go! Genaeral Information - XML NotePad > > > > Mike > From sandram at boi.hp.com Thu Mar 11 11:27:10 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: FW: UPD> my email address Message-ID: <01BE6BA1.57B46760@hpb13858.boi.hp.com> Hi, My original email address is now working. You can send email to sandram@boi.hp.com and I will get it. Sandra Matts -----Original Message----- From: Sandra Matts [SMTP:sandram@hpbs1061.boi.hp.com] Sent: Wednesday, March 10, 1999 4:06 PM To: upd@pwg.org Subject: UPD> my email address Hi, For some reason my current email address is not functioning so I have not received any email for the last three days. If you have sent me any email please resend to sandram@hpbs1061.boi.hp.com. I will let you know when my real email (sandram@boi.hp.com) is working. thanks, Sandra Matts From sandram at boi.hp.com Thu Mar 11 16:13:29 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> fixed link to UPDF spec Message-ID: <01BE6BC9.574FD200@hpb13858.boi.hp.com> Hi, The link is slightly incorrect for the UPDFspec. Try this: ftp://ftp.pwg.org/pub/pwg/upd/Archive/Specs/ Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Thu Mar 11 17:47:46 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> minutes from Miami meeting Message-ID: <01BE6BD6.82D93940@hpb13858.boi.hp.com> Hi, I posted minutes from the Miami meeting on the web page at http://www.pwg.org/updf/ ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Mon Mar 15 11:24:44 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> Tues phone conference Message-ID: <01BE6EC5.A9FA04E0@hpb13858.boi.hp.com> Hi All, UPDF will have a phone conference on Tuesday 10-12 Pacific time. Phone number is: (612) 315-6802 Access code is: 058459494 Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Tue Mar 16 10:43:32 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> agenda for phone conf today Message-ID: <01BE6F89.133E3840@hpb13858.boi.hp.com> Hi, Here's the items I would like to discuss. People are always welcome to add items they want to discuss during the phone conference. Mac OS and Linux support. Discuss the subgroup work slated for New Orleans. UPDF specification. Is there anything in the header to be added or is it complete as is? Furthur comments on UPDF spec. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Tue Mar 23 12:46:19 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> break out rooms for Philly Message-ID: <01BE751A.637712A0@hpb13858.boi.hp.com> Hi All, I'm setting up the additional meeting room for the UPDF UI and Imaging meetings. Unlike the New Orleans hotel, we will have to pay $275 / day for the room. I would like people to ping me if they will be attending so that I can calculate about how much to charge everyone. Also do people want breakfast included with the room at an additional charge or do you prefer breakfast on your own. Its about 15.00 / person for breakfast. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Thu Mar 25 13:01:39 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> break out room for Philly Message-ID: <01BE76AE.DC105EC0@hpb13858.boi.hp.com> Hi, A couple of days ago I sent out a message concerning break out rooms for the UI and Imaging meetings for UPD. So far no one has responded that they will attend. I'm in the process of signing the contract for the rooms and I need to know if people are going to the UI and Imaging meeting. The extra room costs $275 /day or total is $550. The cost will be divided amoungst the attendees. If ten people attend that's 27.50 per day. This is less than the main meeting. Can people please let me know if they will attend. Marriott would like the contract back today. Remember - Wed after Plenery is UI and Thursday is Imaging Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Mon Mar 29 16:39:07 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> phone conf or not Message-ID: <01BE79F1.E7175DA0@hpb13858.boi.hp.com> Hi, Tomorrow the UPDF group has a phone conference scheduled. There hasn't been much activity since the last phone conference. Unless people feel a real strong need to have the conf. I propose that we do not have a phone conference and just meet in New Orleans on Wed for the User Interface portion of the UPDF meeting. Reply with your thoughts. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From charles.a.adams at exgate.tek.com Mon Mar 29 17:15:21 1999 From: charles.a.adams at exgate.tek.com (charles.a.adams@exgate.tek.com) Date: Wed May 6 14:04:47 2009 Subject: UPD> phone conf or not Message-ID: <6B57A2A3212BD2119C2600805F6F141301A33D64@us-wv-m11.wv.tek.com> I am also guilty. I have had little time to work on UPDF. But at the same time I am not going to make the meeting in New Orleans. Is there a chance of getting something together for a conference call next week? Chuck Adams Tektronix, Inc. > -----Original Message----- > From: Sandra Matts [SMTP:sandram@boi.hp.COM] > Sent: Monday, March 29, 1999 1:39 PM > To: Universal Printer Driver (E-mail) > Subject: UPD> phone conf or not > > Hi, > Tomorrow the UPDF group has a phone conference scheduled. There > hasn't been much activity since the last phone conference. Unless people > feel a real strong need to have the conf. I propose that we do not have > a phone conference and just meet in New Orleans on Wed for the User > Interface portion of the UPDF meeting. > > Reply with your thoughts. > > > Sandra Matts > > ------------------------ > Sandra Matts > Hewlett-Packard > Engineer Scientist > sandram@boi.hp.com > (208) 396-4755 phone > (208) 396-5161 fax From sandram at boi.hp.com Tue Mar 30 13:55:27 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: FW: UPD> phone conf or not Message-ID: <01BE7AA4.34BD50C0@hpb13858.boi.hp.com> No conference call today. Everyone agreed in reply. Those who replied anyway. Sandra Matts -----Original Message----- From: Farrell, Lee [SMTP:Lee_Farrell@cissc.canon.com] Sent: Tuesday, March 30, 1999 10:50 AM To: 'Sandra Matts' Subject: RE: UPD> phone conf or not I assume that the final decision is no conference call today? (There didn't seem to be a notice after your proposal below.) lee -----Original Message----- From: Sandra Matts [mailto:sandram@boi.hp.com] Sent: Monday, March 29, 1999 1:39 PM To: Universal Printer Driver (E-mail) Subject: UPD> phone conf or not Hi, Tomorrow the UPDF group has a phone conference scheduled. There hasn't been much activity since the last phone conference. Unless people feel a real strong need to have the conf. I propose that we do not have a phone conference and just meet in New Orleans on Wed for the User Interface portion of the UPDF meeting. Reply with your thoughts. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Thu Apr 15 19:35:34 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> minutes from UI and imaging mtg Message-ID: <01BE8766.5F1B6F40@hpb13858.boi.hp.com> Hi, I copied the minutes from our UI meeting and Imaging meeting to the ftp site in minutes\1999\updf_mtg.doc. I will also bring a hard copy to Friday's meeting. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Mon Apr 26 19:11:07 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> phone conf tomorrow Message-ID: <01BE9007.C6DB8A80@hpb13858.boi.hp.com> Hi All, We usually have a phone conference the second Tuesday after the PWG meeting. Unfortunately I haven't even put the notes from the meeting on the web page yet or updated the UPDF spec. I plan on doing those tasks this week. Do people still want to have the phone conference or can we delay for two weeks? In two weeks I will have a modified version of the UPDF and notes from the PWG meeting - so I vote for a phone conf. in two weeks. Send your opinion please. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Tue Apr 27 12:48:51 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> phone conference cancelled Message-ID: <01BE909B.8A2EB500@hpb13858.boi.hp.com> Hi All, Today's phone conference is cancelled. We will have a phone conf on Tuesday May 11. I will send out an agenda the week before the conf. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Mon May 10 18:56:16 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> no phone conf. tomorrow Message-ID: <01BE9B06.0543EFC0@hpb13858.boi.hp.com> Hi All, It appears I have to give a presentation tomorrow from 10am - 2 pm and cannot hold the UPDF phone conference. I apologize for the late notice. I will send out notes from the last meeting and start the agenda for the meeting in Philly. If anybody has specific agenda items - please email them. thanks, Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Mon May 17 17:19:55 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> minutes from last meeting on ftp site Message-ID: <01BEA078.B86FB1C0@hpb13858.boi.hp.com> Hi, I've copied the minutes from the last meeting into ftp://ftp.pwg.org/pub/pwg/upd/minutes/1999/upd990416.html I will create pdf and doc versions soon and I should have the web page updated tomorrow. Thank you, Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Wed May 26 14:57:53 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> new locale doc on ftp site Message-ID: <01BEA777.6A84FDC0@hpb13858.boi.hp.com> Hi, I"ve copied a white paper for Locale to ftp.pwg.org/pub/pwg/upd/Archive/Specs/Locale.pdf I will bring hard copies to the meeting Friday but if you want to read it now - download the pdf version. I also fixed some typos in the UPDF spec and posted the new version at ftp.pwg.org/pub/upd/Archive/Specs/UPDF_Spec/v0.51 Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Wed May 26 18:03:27 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> ISO std for Paper sizes Message-ID: <01BEA791.4DA35980@hpb13858.boi.hp.com> Hi, I haven't been able to find a listing of the ISO standard for paper sizes. I can order the standard from ISO but does anyone know of a document that already lists them so I can get started sooner. Also there are several paper size standards. Which one does IPP use? thanks, Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From Robert.Herriot at pahv.xerox.com Fri Jun 4 18:54:16 1999 From: Robert.Herriot at pahv.xerox.com (Herriot, Robert) Date: Wed May 6 14:04:47 2009 Subject: UPD> ISO std for Paper sizes Message-ID: <51B8ABCE456FD111899900805F6FD6EE035C2ADF@mercury.ADOC.xerox.com> IPP Appendix C copied the media and media sizes from ISO 10175 (DPA). IPP contains all values from DPA. The only sizes that are obviously missing are for A, B, C, D and E. A is 8.5x11. Each additional size doubles the short dimension. Tom will add these sizes to the next release of the IPP document which will be ready in a few days. Is there other information you need beyond what IPP Appendix C has? Bob Herriot -----Original Message----- From: Sandra Matts [mailto:sandram@boi.hp.com] Sent: Wednesday, May 26, 1999 3:03 PM To: Universal Printer Driver (E-mail) Subject: UPD> ISO std for Paper sizes Hi, I haven't been able to find a listing of the ISO standard for paper sizes. I can order the standard from ISO but does anyone know of a document that already lists them so I can get started sooner. Also there are several paper size standards. Which one does IPP use? thanks, Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From cmanros at cp10.es.xerox.com Fri Jun 4 20:27:59 1999 From: cmanros at cp10.es.xerox.com (Manros, Carl-Uno B) Date: Wed May 6 14:04:47 2009 Subject: UPD> ISO std for Paper sizes Message-ID: <918C79AB552BD211A2BD00805F15CE85014EAD23@x-crt-es-ms1.cp10.es.xerox.com> Bob, What do you mean with A being 8.5x11? Maybe I am not understanding what you A, B, C etc. refer to. ISO A4 is 210x297 mm, A3 is 297x420 mm, etc. Carl-Uno > -----Original Message----- > From: Herriot, Robert [mailto:Robert.Herriot@pahv.xerox.com] > Sent: Friday, June 04, 1999 3:54 PM > To: Sandra Matts; Universal Printer Driver (E-mail) > Subject: RE: UPD> ISO std for Paper sizes > > > IPP Appendix C copied the media and media sizes from ISO > 10175 (DPA). IPP > contains all values from DPA. The only sizes that are > obviously missing are > for A, B, C, D and E. A is 8.5x11. Each additional size > doubles the short > dimension. Tom will add these sizes to the next release of > the IPP document > which will be ready in a few days. > > Is there other information you need beyond what IPP Appendix C has? > > Bob Herriot > > -----Original Message----- > From: Sandra Matts [mailto:sandram@boi.hp.com] > Sent: Wednesday, May 26, 1999 3:03 PM > To: Universal Printer Driver (E-mail) > Subject: UPD> ISO std for Paper sizes > > > Hi, > I haven't been able to find a listing of the ISO standard > for paper sizes. I can order the standard from ISO but does > anyone know of a document that already lists them so > I can get started sooner. > > Also there are several paper size standards. Which > one does IPP use? > > thanks, > Sandra > > ------------------------ > Sandra Matts > Hewlett-Packard > Engineer Scientist > sandram@boi.hp.com > (208) 396-4755 phone > (208) 396-5161 fax > From Robert.Herriot at pahv.xerox.com Fri Jun 4 20:32:07 1999 From: Robert.Herriot at pahv.xerox.com (Herriot, Robert) Date: Wed May 6 14:04:47 2009 Subject: UPD> ISO std for Paper sizes Message-ID: <51B8ABCE456FD111899900805F6FD6EE035C2AEC@mercury.ADOC.xerox.com> I was referring to English engineering sizes of A (same as letter), B (same as ledger), C, D and E. Bob Herriot -----Original Message----- From: Manros, Carl-Uno B [mailto:cmanros@cp10.es.xerox.com] Sent: Friday, June 04, 1999 5:28 PM To: Herriot, Robert; Sandra Matts; Universal Printer Driver (E-mail) Subject: RE: UPD> ISO std for Paper sizes Bob, What do you mean with A being 8.5x11? Maybe I am not understanding what you A, B, C etc. refer to. ISO A4 is 210x297 mm, A3 is 297x420 mm, etc. Carl-Uno > -----Original Message----- > From: Herriot, Robert [mailto:Robert.Herriot@pahv.xerox.com] > Sent: Friday, June 04, 1999 3:54 PM > To: Sandra Matts; Universal Printer Driver (E-mail) > Subject: RE: UPD> ISO std for Paper sizes > > > IPP Appendix C copied the media and media sizes from ISO > 10175 (DPA). IPP > contains all values from DPA. The only sizes that are > obviously missing are > for A, B, C, D and E. A is 8.5x11. Each additional size > doubles the short > dimension. Tom will add these sizes to the next release of > the IPP document > which will be ready in a few days. > > Is there other information you need beyond what IPP Appendix C has? > > Bob Herriot > > -----Original Message----- > From: Sandra Matts [mailto:sandram@boi.hp.com] > Sent: Wednesday, May 26, 1999 3:03 PM > To: Universal Printer Driver (E-mail) > Subject: UPD> ISO std for Paper sizes > > > Hi, > I haven't been able to find a listing of the ISO standard > for paper sizes. I can order the standard from ISO but does > anyone know of a document that already lists them so > I can get started sooner. > > Also there are several paper size standards. Which > one does IPP use? > > thanks, > Sandra > > ------------------------ > Sandra Matts > Hewlett-Packard > Engineer Scientist > sandram@boi.hp.com > (208) 396-4755 phone > (208) 396-5161 fax > From sandram at boi.hp.com Tue Jun 8 10:18:05 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> ISO std for Paper sizes Message-ID: <01BEB187.6FB84080@hpb13858.boi.hp.com> thanks - that will give us a start. I will put a list in the UPDF spec. and send it out. Sandra -----Original Message----- From: Herriot, Robert [SMTP:Robert.Herriot@pahv.xerox.com] Sent: Friday, June 04, 1999 4:54 PM To: Sandra Matts; Universal Printer Driver (E-mail) Subject: RE: UPD> ISO std for Paper sizes IPP Appendix C copied the media and media sizes from ISO 10175 (DPA). IPP contains all values from DPA. The only sizes that are obviously missing are for A, B, C, D and E. A is 8.5x11. Each additional size doubles the short dimension. Tom will add these sizes to the next release of the IPP document which will be ready in a few days. Is there other information you need beyond what IPP Appendix C has? Bob Herriot -----Original Message----- From: Sandra Matts [mailto:sandram@boi.hp.com] Sent: Wednesday, May 26, 1999 3:03 PM To: Universal Printer Driver (E-mail) Subject: UPD> ISO std for Paper sizes Hi, I haven't been able to find a listing of the ISO standard for paper sizes. I can order the standard from ISO but does anyone know of a document that already lists them so I can get started sooner. Also there are several paper size standards. Which one does IPP use? thanks, Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Tue Jun 8 11:10:34 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> phone conf Message-ID: <01BEB18E.C4A9FE60@hpb13858.boi.hp.com> I will activate the phone conference at 10am Pacific time today if people want to talk. I didn't have time to set up an agenda but people might want to find out about the last meeting. And discuss items for this month. Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Tue Jun 8 11:34:47 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> phone number Message-ID: <01BEB192.26C15AA0@hpb13858.boi.hp.com> Phone number is: 1-612-315-6802 access code: 058459494 -----Original Message----- From: Sandra Matts [SMTP:sandram@boi.hp.com] Sent: Tuesday, June 08, 1999 9:11 AM To: Universal Printer Driver (E-mail) Subject: UPD> phone conf I will activate the phone conference at 10am Pacific time today if people want to talk. I didn't have time to set up an agenda but people might want to find out about the last meeting. And discuss items for this month. Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Tue Jun 8 12:10:43 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> phone conf Message-ID: <01BEB197.2C1E16A0@hpb13858.boi.hp.com> Since I sent such short notice on the phone conf., We can set up a another one for next Tuesday if that works for most people. I will send out an agenda by thur this week. Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Fri Jun 11 12:01:19 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> Tuesday phone conf Message-ID: <01BEB3F1.5B12C6C0@hpb13858.boi.hp.com> Hi All, I'm trying to set up a phone conf for either next Tuesday or the following Tuesday. The two dates are: June 15 10-12 am Pacific or June 22 10-12 am. agenda so far: Process for moving open issues to closed. Locale: Proposal is to use the ISO standards for language / country. Update on 2 or three letter acronym. Look at creating actual XML for Locale and Default Paper Handling for UPDF spec. PDL registration and specification Font metrics List of things to go into implementor's guide so far. If people have a strong opinion of which Tuesday to hold the phone conf. - reply to this email. Otherwise I will pick one. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From Michael_Yeung at cissc.canon.com Fri Jun 11 13:45:24 1999 From: Michael_Yeung at cissc.canon.com (Yeung, Michael) Date: Wed May 6 14:04:47 2009 Subject: UPD> Tuesday phone conf Message-ID: <6C940F5153E5D211937A0090274E8D8B165AC9@cissc.cisoc.canon.com> I would prefer June 22, because of Java0ne (Starts next week!) Mike -----Original Message----- From: Sandra Matts [mailto:sandram@boi.hp.com] Sent: Friday, June 11, 1999 9:01 AM To: Universal Printer Driver (E-mail) Subject: UPD> Tuesday phone conf Hi All, I'm trying to set up a phone conf for either next Tuesday or the following Tuesday. The two dates are: June 15 10-12 am Pacific or June 22 10-12 am. agenda so far: Process for moving open issues to closed. Locale: Proposal is to use the ISO standards for language / country. Update on 2 or three letter acronym. Look at creating actual XML for Locale and Default Paper Handling for UPDF spec. PDL registration and specification Font metrics List of things to go into implementor's guide so far. If people have a strong opinion of which Tuesday to hold the phone conf. - reply to this email. Otherwise I will pick one. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Fri Jun 11 16:02:42 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> Tuesday phone conf Message-ID: <01BEB413.137EADC0@hpb13858.boi.hp.com> We will have the phone conference on June 22 10-12am Pacific. thanks, Sandra -----Original Message----- From: Sandra Matts [SMTP:sandram@boi.hp.com] Sent: Friday, June 11, 1999 10:01 AM To: Universal Printer Driver (E-mail) Subject: UPD> Tuesday phone conf Hi All, I'm trying to set up a phone conf for either next Tuesday or the following Tuesday. The two dates are: June 15 10-12 am Pacific or June 22 10-12 am. agenda so far: Process for moving open issues to closed. Locale: Proposal is to use the ISO standards for language / country. Update on 2 or three letter acronym. Look at creating actual XML for Locale and Default Paper Handling for UPDF spec. PDL registration and specification Font metrics List of things to go into implementor's guide so far. If people have a strong opinion of which Tuesday to hold the phone conf. - reply to this email. Otherwise I will pick one. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From BEN_BREZINSKI at HP-Vancouver-om1.om.hp.com Mon Jun 14 14:50:24 1999 From: BEN_BREZINSKI at HP-Vancouver-om1.om.hp.com (BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com) Date: Wed May 6 14:04:47 2009 Subject: UPD> Tuesday phone conf In-Reply-To: <01BEB3F1.5B12C6C0@hpb13858.boi.hp.com> Message-ID: Item Subject: UPD> Tuesday phone conf June 22 would work for me. I am booked June 15. I vote for the ISO standards for language/country, 3 letter codes. I have no opinion on font metrics. Here is what I wrote down so far for the implementor's guide. No UI controls are required in the UPDF. The driver implementers may choose to implement whatever controls he chooses. Dynamic nature of the UPDF file. The driver implemter should be aware that the UPDF file reflect the current configuration, and may change as accessories are added or deleted. The frequency of update is not specified, but should be reasonable. Mapping of UPDF language_country codes to operating systems. Ben Brezinski ______________________________ Reply Separator _________________________________ Subject: UPD> Tuesday phone conf Author: sandram-at-boi (sandram@boi.hp.com) at HP-Vancouver,shargw1 Date: 6/11/99 9:01 AM Hi All, I'm trying to set up a phone conf for either next Tuesday or the following Tuesday. The two dates are: June 15 10-12 am Pacific or June 22 10-12 am. agenda so far: Process for moving open issues to closed. Locale: Proposal is to use the ISO standards for language / country. Upd ate on 2 or three letter acronym. Look at creating actual XML for Locale and De fault Paper Handling for UPDF spec. PDL registration and specification Font metrics List of things to go into implementor's guide so far. If people have a strong opinion of which Tuesday to hold the phone conf. - reply to this email. Otherwise I will pick one. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Mon Jun 14 15:45:43 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: FW: UPD> Tuesday phone conf Message-ID: <01BEB66C.3325EFC0@hpb13858.boi.hp.com> ok so I left out a few details. 612-315-6802 access code: 058459494 Sandra Matts -----Original Message----- From: BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com [SMTP:BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com] Sent: Monday, June 14, 1999 1:29 PM To: sandram@boi.hp.com Subject: RE: UPD> Tuesday phone conf And the number is.......? Ben B ______________________________ Reply Separator _________________________________ Subject: RE: UPD> Tuesday phone conf Author: sandram-at-boi (sandram@boi.hp.com) at HP-Vancouver,shargw1 Date: 6/11/99 1:02 PM We will have the phone conference on June 22 10-12am Pacific. thanks, Sandra -----Original Message----- From: Sandra Matts [SMTP:sandram@boi.hp.com] Sent: Friday, June 11, 1999 10:01 AM To: Universal Printer Driver (E-mail) Subject: UPD> Tuesday phone conf Hi All, I'm trying to set up a phone conf for either next Tuesday or the following Tuesday. The two dates are: June 15 10-12 am Pacific or June 22 10-12 am. agenda so far: Process for moving open issues to closed. Locale: Proposal is to use the ISO standards for language / country. Upd ate on 2 or three letter acronym. Look at creating actual XML for Locale and De fault Paper Handling for UPDF spec. PDL registration and specification Font metrics List of things to go into implementor's guide so far. If people have a strong opinion of which Tuesday to hold the phone conf. - reply to this email. Otherwise I will pick one. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Wed Jun 16 12:53:37 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> minutes on ftp site Message-ID: <01BEB7E6.7D4CD160@hpb13858.boi.hp.com> Hi All, I copied the minutes from the last meeting onto the ftp site. It's at: ftp://ftp.pwg.org/pub/pwg/upd/minutes/1999/upd990528.htm I'm working on updating the Locale white paper a bit and the issues doc. I will copy those to the Archive section of the ftp site when I'm done. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at hpbs1061.boi.hp.com Fri Jun 18 17:16:26 1999 From: sandram at hpbs1061.boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> new dtd and xml Message-ID: <9906182116.AA12036@hpbs1061.boi.hp.com> Hi All, I copied a new dtd and Color laserJet 4500 xml file that has a stab at the start of Locale using the ISO standards. Please take a look at it and email comments. It's in ftp.pwg.org/pub/pwg/upd/Archive/1999/990618 There are pdf versions of the files with changes in yellow highlight. There is also the updf.dtd file and an xml file showing implementation. Sandra Matts Engineer Scientist Hewlett-Packard sandram@boi.hp.com From sandram at hpbs1061.boi.hp.com Mon Jun 21 17:47:34 1999 From: sandram at hpbs1061.boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> XML based UI work Message-ID: <9906212147.AA25252@hpbs1061.boi.hp.com> Hi All, I found a couple of very interesting sites defining User Interface components in XML. They look quite promising for our work and I believe we can leverage their work. The first one is at: www.oasis-open.org/cover/uiml.html The group is defining a language for the actual interface elements in a graphical interface like Windows and Motif. The second one is at: www.oasis-open.org/cover/xul.html This work appears to be defining an XToolkit and I don't know how tied to Unix it is. Sandra Matts Engineer Scientist Hewlett-Packard 208-396-4755 From charles.a.adams at exgate.tek.com Tue Jul 27 10:40:34 1999 From: charles.a.adams at exgate.tek.com (charles.a.adams@exgate.tek.com) Date: Wed May 6 14:04:47 2009 Subject: UPD> DTD's vs. Schema's Message-ID: <6B57A2A3212BD2119C2600805F6F1413027873A2@us-wv-m11.wv.tek.com> More food for thought. * EXTREME XML: Describe Your Data - DTD or schema? http://msdn.microsoft.com/voices/xml.asp Charles "Chuck" Adams adamsc@pogo.wv.tek.com Tektronix, Inc. From sandram at boi.hp.com Thu Aug 12 13:15:31 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> notes from Denmark and new docs Message-ID: <01BEE4B3.FE23F1C0@hpb13858.boi.hp.com> Hi All, I have just returned from a 4.5 week vacation and I now realize my out of office reply did not work correctly. I apologize if people sent me email and I did not reply. Anyway I am trying to copy documents from the Denmark meeting to the ftp site and haven't been successful. We are trying to get it resolved currently. In the meantime - do people want me to attach pdf versions to an email message? I know the email reflector does not like large emails and they tend to bounce if they are too big. I can also try to copy from my home machine which has no security at all and see if I can get through. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Thu Aug 12 13:32:37 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> re-scope of UPDF Message-ID: <01BEE4B6.618F13A0@hpb13858.boi.hp.com> Hi, Even though the UPDF spec is coming along - the work is not as focused as it could be. I believe there are a couple of reasons for this. One being there sheer size of the task. We did an excellent job dividing the job into sections - UI, Localization, etc - but I haven't done a very good job keeping the work focused on a specific area. Another issue has been the usefulness of the project itself. Is UPDF really needed when IPP can retrieve some of the info from the printer? Can IPP and UPDF complement each other or is there maybe too much overlap? There also has been some thought about steering UPDF towards a Linux (and other Unix flavors) printing solution and not really a "Universal" solution. What do people think about that? Chuck sent out the DTD vs Schema link. This is something to look at. Also please check out the UIML and XUL documents for User Interface specification in UPDF. thanks, Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Fri Aug 13 14:57:50 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> updated docs Message-ID: <01BEE58B.73CBBF20@hpb13858.boi.hp.com> Hi, Attached are the latest dtd and xml documents that contain the locale syntax. The locale list is not all inclusive but only a short example list currently. I was able to copy slides from the Denmark meeting to ftp.pwg.org/pub/pwg/upd/minutes/1999/updf_mtg990709.pdf and .ppt Also I copied a new document that shows a mapping of UPDF to PPD keywords. ftp.pwg.org/pub/pwg/upd/Archive/Specs/mapping_updf_ppd.pdf and .doc And lastly I copied an updated version of locale.doc and pdf. Unfortunately, Windows is not as case sensitive as Unix and there are two copies of the docs: Locale and locale. I wasn't able to telnet in to rename so please get the doc with the latest date. I'm working on minutes from the Denmark meeting and an updated UPDF spec. I will post when done and I will also bring copies to the Alaska meeting. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax begin 600 CLJ4500.xml M/#]X;6P@=F5R2!B87-I8R!54$1&(&9I M;&4@=VET:"!J=7-T('1H92!M:6YI;75M(')E<75I7,@551&+3@N#0H-"B @("!,;V-A;&5S('-U M<'!O2!T:&ES(%501$8@9FEL92X-"CPA+2T@+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+B M+3X-"B @(" \3&]C86QE3&ES=#X-"B @(" @(" @/$QO8V%L92!, M;V-A;&5)9#TB96Y?054B/CPO3&]C86QE/@T*(" @(" @(" \3&]C86QE($QO M8V%L94ED/2)E;E]'0B(^/"],;V-A;&4^#0H@(" @(" @(#Q,;V-A;&4@3&]C M86QE260](F5N7U53(CX\+TQO8V%L93X-"B @(" @(" @/$QO8V%L92!,;V-A M;&5)9#TB9&%?1$LB/CPO3&]C86QE/@T*(" @(" @(" \0W5S=&]M3&]C86QE M#0H@(" @(" @(" @("!#=7-T;VU,;V-A;&5)9#TB96Y?54LB/CPO0W5S=&]M M3&]C86QE/@T*(" @(" @(" \0W5S=&]M3&]C86QE#0H@(" @(" @(" @("!# M=7-T;VU,;V-A;&5)9#TB86%?0D(B/CPO0W5S=&]M3&]C86QE/@T*(" @(#PO M3&]C86QE3&ES=#X-"@T*(" @(#Q&:6QE3F%M93Y#3$HT-3 P+GAM;#PO1FEL M94YA;64^#0H-"B @(" \0W5S=&]M1&5V:6-E0V%P5&%G7!E-#(B+SX-"B @(" \+T-U M2!M=6QT:7!L92!L86YG=6%G97,@ M+2!A="!L96%S="!T:')E90T*/"$M+2 N+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN("TM/@T* M(" @(" @(" @(" @(" @(#Q,86YG=6%G92Y01$P@#0H@(" @(" @(" @(" @ M(" @(" @("!01$Q-86IOF5+8CTB,S(W-C@B#0H@(" @(" @(" @(" @(" @(" @(" @("!204U);G1E M7-I8V%L/@T*(" @(" @(" @(" @/%!L M871F;W)M/@T*(" @(" @(" @(" @(" @(#Q-;V1U;&5.86UE7,^/"]/=F5R;&%Y T*(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" \54E#;VYT4UA;F%G93X\+U!R M:6YT97)-96UOF4Z($QE='1E MF4](D1-4$%015)?030B+SX-"B @(" @(" @(" @(" @ M(" @(" @(" @(" @(" \+T100W5S=&]M3&]C86QE/@T*(" @(" @(" @(" @ M(" @(" @(" @(" @/"]$969A=6QT4&%P97(^#0H-"@T*(" @(" @(" @(" @ M(" @(" @(" @(" @/%!A<&5R(&1M<&%P97)S:7IE/2)$35!!4$527TQ%5%1% M4B(^3&5T=&5R#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @/%!A<&5R M+D%R96$^#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @/"$M+2TM+2TM M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM M+2T-"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @25-3544Z("I) M;6%G96%B;&5!&5L#0H@(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @("!L969T/2(Q,BXP,"(@=&]P/2(Q,BXQ M,B(@&5L#0H@(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @;&5F=#TB,3(N,# B('1O<#TB,3(N,3(B(')I M9VAT/2(U.#,N,#@B(&)O='1O;3TB.#(Y+C8X(B\^#0H@(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(#Q087!E#TB M,3$Q,2(@>3TB,3$Q,2(O/@T*(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(#PO4&%P97(N07)E83X-"B @(" @(" @(" @(" @(" @(" @(" @(#PO4&%P M97(^#0H@(" @(" @(" @(" @(" @(" @(" @(" \4&%P97(@9&UP87!EF4](D1-4$%015)?3$5'04PB/DQE9V%L#0H@(" @(" @(" @(" @(" @(" @ M(" @(" @(" @/%!A<&5R+D%R96$^#0H@(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(#Q087!E&5L('@](C8Q,B(@>3TB M,3 P."(O/@T*(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" \4&%P M97(N07)E82YR8TUA&5L#0H@(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @;&5F=#TB,3(N,# B('1O<#TB,3(N,3(B(')I M9VAT/2(U.3DN.#@B(&)O='1O;3TB.3DU+CDP(B\^#0H@(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(#Q087!E#TB M,3$Q,2(@>3TB,3$Q,2(O/@T*(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(#PO4&%P97(N07)E83X-"B @(" @(" @(" @(" @(" @(" @(" @(#PO4&%P M97(^#0H-"B @(" @(" @(" @(" @(" @(" @(" @(#Q087!E&5L#0H@(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @;&5F=#TB,3(N,# B('1O<#TB M,3(N,3(B(')I9VAT/2(U,#DN.#@B(&)O='1O;3TB-S0S+CDP(B\^#0H@(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q087!E#TB,3$Q,2(@>3TB,3$Q,2(O/@T*(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(#PO4&%P97(N07)E83X-"B @(" @(" @(" @(" @(" @(" @ M(" @(#PO4&%P97(^#0H-"B @(" @(" @(" @(" @(" @(" @(" @(#Q087!E M#TB-#(P M(B!Y/2(U.34B+SX-"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M/%!A<&5R+D%R96$NF5-;3$P M('@](C$Q,3$B('D](C$Q,3$B+SX-"B @(" @(" @(" @(" @(" @(" @(" @ M(" @(" \+U!A<&5R+D%R96$^#0H@(" @(" @(" @(" @(" @(" @(" @(" \ M+U!A<&5R/@T*#0H@(" @(" @(" @(" @(" @(" @(" @(" \4&%P97(@9&UP M87!EF4](D1-4$%015)?0C4B/D(U("A*25,I#0H@(" @(" @(" @(" @ M(" @(" @(" @(" @(" @/%!A<&5R+D%R96$^#0H@(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(#Q087!E&5L('@](C4Q M-B(@>3TB-S(Y(B\^#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(#Q087!E#TB-#DY(B!Y/2(W,#DB+SX-"B @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @/%!A<&5R+D%R96$NF5-;3$P('@](C$Q,3$B('D](C$Q,3$B+SX-"B @(" @(" @(" @(" @ M(" @(" @(" @(" @(" \+U!A<&5R+D%R96$^#0H@(" @(" @(" @(" @(" @ M(" @(" @(" \+U!A<&5R/@T*#0H@(" @(" @(" @(" @(" @(" @(" @(" \ M4&%P97(@9&UP87!EF4](D1-4$%015)?14Y67S$P(CY%;G9E;&]P92 C M,3 -"B @(" @(" @(" @(" @(" @(" @(" @(" @(" \4&%P97(N07)E83X- M"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @/%!A<&5R+D%R96$N M<'1!#TB,CDW(B!Y/2(V.#0B+SX-"B @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @/%!A<&5R+D%R96$NF5-;3$P('@](C$Q,3$B('D](C$Q,3$B+SX-"B @(" @ M(" @(" @(" @(" @(" @(" @(" @(" \+U!A<&5R+D%R96$^#0H@(" @(" @ M(" @(" @(" @(" @(" @(" \+U!A<&5R/@T*#0H@(" @(" @(" @(" @(" @ M(" @(" @(" \4&%P97(@9&UP87!EF4](D1-4$%015)?14Y67T,U(CY% M;G9E;&]P92!#-0T*(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q087!E M&5L#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @;&5F=#TB,3(N,# B('1O<#TB,3(N,3(B(')I9VAT/2(T-#3TB-C(T(B\^ M#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q087!E&5L M('@](C(W.2(@>3TB-30P(B\^#0H@(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(#Q087!E"!T1'5P;&5X/2)/3B(^/"]$=7!L97@^#0H@(" @(" @(" @(" @(" @ M(" @(#Q";V]K;&5T('1";V]K;&5T/2)/1D8B+SX-"B @(" @(" @(" @(" @ M(" @(" @/$-E;G1E7-T96US+"!);F,@(" @(" @(" @(" @(" @(" @(" @(" M+3X-"CPA+2T@ M4')I;G1EF5?96YU;2 -"@DG*"!&04Q317P-"@E$35!!4$527TQ% M5%1%4GP-"@E$35!!4$527TQ%5%1%4E--04Q,? T*"41-4$%015)?5$%"3$]) M1'P-"@E$35!!4$527TQ%1$=%4GP-"@E$35!!4$527TQ%1T%,? T*"41-4$%0 M15)?4U1!5$5-14Y4? T*"41-4$%015)?15A%0U54259%? T*"41-4$%015)? M03-\#0H)1$U005!%4E]!-'P-"@E$35!!4$527T$T4TU!3$Q\#0H)1$U005!% M4E]!-7P-"@E$35!!4$527T(T? T*"41-4$%015)?0C5\#0H)1$U005!%4E]& M3TQ)3WP-"@E$35!!4$527U%505)43WP-"@E$35!!4$527S$P6#$T? T*"41- M4$%015)?,3%8,3=\#0H)1$U005!%4E].3U1%? T*"41-4$%015)?14Y67SE\ M#0H)1$U005!%4E]%3E9?,3!\#0H)1$U005!%4E]%3E9?,3%\#0H)1$U005!% M4E]%3E9?,3)\#0H)1$U005!%4E]%3E9?,31\#0H)1$U005!%4E]#4TA%151\ M#0H)1$U005!%4E]$4TA%151\#0H)1$U005!%4E]%4TA%151\#0H)1$U005!% M4E]%3E9?1$Q\#0H)1$U005!%4E]%3E9?0S5\#0H)1$U005!%4E]%3E9?0S-\ M#0H)1$U005!%4E]%3E9?0S1\#0H)1$U005!%4E]%3E9?0S9\#0H)1$U005!% M4E]%3E9?0S8U? T*"41-4$%015)?14Y67T(T? T*"41-4$%015)?14Y67T(U M? T*"41-4$%015)?14Y67T(V? T*"41-4$%015)?14Y67TE404Q9? T*"41- M4$%015)?14Y67TU/3D%20TA\#0H)1$U005!%4E]%3E9?4$524T].04Q\#0H) M1$U005!%4E]&04Y&3TQ$7U53? T*"41-4$%015)?1D%.1D],1%]35$1?1T52 M34%.? T*"41-4$%015)?1D%.1D],1%],1TQ?1T5234%.? T*"41-4$%015)? M25-/7T(T? T*"41-4$%015)?2D%004Y%4T5?4$]35$-!4D1\#0H)1$U005!% M4E\Y6#$Q? T*"41-4$%015)?,3!8,3%\#0H)1$U005!%4E\Q-5@Q,7P-"@E$ M35!!4$527T5.5E])3E9)5$5\#0H)1$U005!%4E]215-%4E9%1%\T.'P-"@E$ M35!!4$527U)%4T525D5$7S0Y? T*"41-4$%015)?3$545$527T585%)!? T* M"41-4$%015)?3$5'04Q?15A44D%\#0H)1$U005!%4E]404),3TE$7T585%)! M? T*"41-4$%015)?031?15A44D%\#0H)1$U005!%4E],151415)?5%)!3E-6 M15)317P-"@E$35!!4$527T$T7U1204Y35D524T5\#0H)1$U005!%4E],1514 M15)?15A44D%?5%)!3E-615)317P-"@E$35!!4$527T%?4$Q54WP-"@E$35!! M4$527T)?4$Q54WP-"@E$35!!4$527TQ%5%1%4E]03%53? T*"41-4$%015)? M031?4$Q54WP-"@E$35!!4$527T$U7U1204Y35D524T5\#0H)1$U005!%4E]" M-5]44D%.4U9%4E-%? T*"41-4$%015)?03-?15A44D%\#0H)1$U005!%4E]! M-5]%6%1207P-"@E$35!!4$527T(U7T585%)!? T*"41-4$%015)?03)\#0H) M1$U005!%4E]!,U]44D%.4U9%4E-%? T*"41-4$%015)?03-?15A44D%?5%)! M3E-615)317P-"@E$35!!4$527U5315)\#0H)1$U005!%4E]*05!!3D5315]% M3E9?631\#0H)1$U005!%4E]*05!!3D5315]%3E9?63)\#0H)1$U005!%4E]* M05!!3D5315]%3E9?2S(I)SX-"CPA14Y42519("4@9&UP87!EF5?871T MF5?96YU;3L@(D9!3%-% M(B<^#0H-"CPA14Y42519("4@9&UP7!E("A.3TY% M?$9L87-H?$A$1"D@(DY/3D4B( T*"0D)4W1OF4@3DU43TM%3B B M,"(^#0H)/"$M+2 N+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BTM/@T*"3PA+2T@3U,O2$]3 M5" @0V]L;W(@36%N86=E;65N="]296YD97)I;F<@(" @(" @(" @(" @(" @ M(" @(" @(" @(" M+3X-"@D\(2TM("XN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+2T^#0H) M/"%%3$5-14Y4(%!L871F;W)M("A-;V1U;&5.86UEF%T:6]N(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" M+3X- M"@D\(2TM("XN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+2T^#0H)/"%%3$5-14Y4($QO8V%L M:7IA=&EO;B!%35!462 ^#0H)/"$M+2 N+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BTM/@T* M"3PA+2T@1VQO8F%L(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" M+3X-"@D\(2TM("XN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+2T^#0H@(" @/"%%3$5-14Y4($=L;V)A;" H57-E4UA;F%G92Q004=%4%)/5$5#5%,L4D533TQ55$E/3E,L#0H@(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @("!43TY%4E-!5D53+"!334]/5$A) M3D=-3T1%4RQ$251(15)334]/5$A)3D=3+ T*(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @1$E42$524RP@54E#;VYS=')A:6YT'Q,:7-T*3X-"B @ M(" @(" @/"%%3$5-14Y4($)U='1O;B!%35!463X-"B @(" @(" @/"%%3$5- M14Y4(%)A9&EO0G5T=&]N1W)O=7 @*%)A9&EO0G5T=&]N*RD^#0H@(" @(" @ M(#PA05143$E35"!2861I;T)U='1O;D=R;W5P#0H@(" @(" @(" @("!.=6U" M=71T;VYS($Y-5$]+14X@(C$B/@T*(" @(" @(" @(" @/"%%3$5-14Y4(%)A M9&EO0G5T=&]N($5-4%19/@T*(" @(" @(" @(" @/"%!5%1,25-4(%)A9&EO M0G5T=&]N#0H@(" @(" @(" @(" @(" @54E,86)E;"!#1$%402 C24U03$E% M1 T*(" @(" @(" @(" @(" @($-O;6UA;F0@0T1!5$$@(TE-4$Q)140^#0H@ M(" @(" @(#PA14Q%345.5"!#:&5C:T)O>"!%35!463X-"B @(" @(" @/"%% M3$5-14Y4($QI4UA;F%G92 H(U!#1$%4 M02D^#0H@(" @(" @(#PA05143$E35"!04UA;F%G94ED("A.3TY%?$UA>&E- M96U\365T?$UE;6]R>4)O;W-T97(I(").3TY%(CX-"B @(" @(" @/"%%3$5- M14Y4(%!!1T504D]414-44R H4&%G95!R;W1E8W0J*3X-"B @(" @(" @/"%! M5%1,25-4(%!!1T504D]414-44R -"B @(" @(" @(" @(&9086=E4')O=&5C M=" E8F]O;%]A='1R:6)U=&5?9F%L6]U=" -"@D)"0D)1W)A>6]U=$ED("A04DE.5$521$5&055,5'Q4 M97AT1W)A<&AI8WQ497AT?$]F9GQ$969A=6QT?$=R87!H:6-\26UA9V5\5&5X M=$EM86=E?$=R87!H:6-);6%G97Q!;&PI(")04DE.5$521$5&055,5"(@/@T* M"0D)/"$M+2!$:71H97)S(&5N9" M+3X-"@T*"0D\(45,14U%3E0@54E#;VYS M=')A:6YT&EN9TUO9&4L2&E296=I6]U="HI/@T* M"0D)/"%!5%1,25-4($Q!64]55%,@#0H)"0D)=$QA>6]U=" E&5L+ T*"0D)"0D)"5!A<&5R+D%R96$N<'13 M:7IE36TQ,"Q087!EF5);F-H,3 P( T*"0D)"0D))7!O:6YT7V%T M=')I8G5T97,[/@T*"0D)"0D\(45,14U%3E0@4&%P97(N07)E82YP=$%R96%- M;3$P($5-4%19(#X-"@D)"0D)/"%!5%1,25-4(%!A<&5R+D%R96$N<'1!6]U=$9L86<@ M14U05%D^#0H)"0D)/"%!5%1,25-4(%!A<&5R+DQA>6]U=$9L86<@#0H)"0D) M"69!F5-;3$P+%5$4$EN9F\N<'1-87A3 M:7IE36TQ,"D^#0H)"0D)/"%%3$5-14Y4(%5$4$EN9F\N<'1$9693:7IE36TQ M,"!%35!462 ^#0H)"0D)/"%!5%1,25-4(%5$4$EN9F\N<'1$9693:7IE36TQ M," -"@D)"0D))7!O:6YT7V%T=')I8G5T97,[/@T*"0D)"3PA14Q%345.5"!5 M1%!);F9O+G)C36%R9VEN36TQ,"!%35!462 ^#0H)"0D)/"%!5%1,25-4(%5$ M4$EN9F\NF5-;3$P($5-4%19(#X- M"@D)"0D\(4%45$Q)4U0@541026YF;RYP=$UI;E-I>F5-;3$P( T*"0D)"0DE M<&]I;G1?871T7Q#;V%T961\3&%B96QS*2 B4%))3E1%4D1%1D%53%0B(#X-"@D@(" @/"$M M+2 N+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+2T^#0H)(" @(#PA+2T@4&%P97)(86YD;&EN9R @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @("TM M/@T*"2 @(" \(2TM("XN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXM+3X-"@D)/"%%3$5-14Y4(%!A M<&5R2&%N9&QI;F<@*%!!4$524T]54D-%4RQ005!%4D1%4U1)3D%424].4RD^ M#0H)"3PA+2T@+2T^#0H)"3PA14Q%345.5"!005!%4E-/55)#15,@*$1E9F%U M;'1087!E#\L0F]O:VQE=#\L0V5N M=&5R1F]L9$%N9%-T87!L93\L4F5V97)S94]R9&5R/RQ*;V)/9F9S970_+$-O M;&QA=&4L1W)O=7 _+$UA:6Q";W@_+%-T87!L93\L1D],1%,_+$AO;&50=6YC M:#\I/@T*"0D\(4%45$Q)4U0@1DE.25-(24Y'4R -"@D)"71&:6YI"!%35!463X-"@D)"3PA05143$E35"!$=7!L97@@#0H)"0D)=$1U<&QE M>" E7!E/RD^#0H) M"0D\(4%45$Q)4U0@0V]L;&%T92 -"@D)"0ET0V]L;&%T92 E" -"@D)"0ET36%I;$)O>" E$YU;2 H(U!#1$%402D^#0H)"0D)/"%%3$5-14Y4(%-T M87!L92Y,3T-!5$E/3E,@*%-T87!L92Y,;V-A=&EO;BHI/@T*"0D)"3PA0514 M3$E35"!3=&%P;&4N3$]#051)3TY3( T*"0D)"0E3=&%P;&4N3G5M3&]C871I M;VX@3DU43TM%3B B,"(^#0H)"0D)"3PA14Q%345.5"!3=&%P;&4N3&]C871I M;VX@*"-00T1!5$$I/@T*"0D)"0D\(4%45$Q)4U0@4W1A<&QE+DQO8V%T:6]N M( T*"0D)"0D)4W1A<&QE+DQO8V%T:6]N260@)7-T87!L96QO8V%T:6]N7V%T M=')I8G5T95]D969A=6QT.SX-"@D)"3PA14Q%345.5"!&3TQ$4R H1F]L9"HI M/@T*"0D)/"%!5%1,25-4($9/3$13( T*"0D)"71&;VQD("5S=&%T93-?871T M7!E*3X-"@D)"0D)/"%%3$5-14Y4 M($9O;&0N5'EP92!%35!463X@#0H)"0D)"3PA05143$E35"!&;VQD+E1Y<&4@ M#0H)"0D)"0E&;VQD5'EP94ED("A.3TY%?%I&;VQD?%-A9&1L97Q$;W5B;&5' M871E?$QE9G1'871E?%)I9VAT1V%T97Q,971T97)&;VQD?%A&;VQD*2 B3D]. M12(-"@D)"0D)"4UA>$YU;0E.351/2T5.("-)35!,245$/@T*"0D)/"%%3$5- M14Y4($AO;&50=6YC:" H2&]L95!U;F-H+DUA>$YU;3\I/@T*"0D)/"%!5%1, M25-4($AO;&50=6YC: T*"0D)"71(;VQE4'5N8V@@)7-T871E,U]A='1R:6)U M=&5?9&5F875L=#L^#0H)"0D)/"%%3$5-14Y4($AO;&50=6YC:"Y-87A.=6T@ M*"-00T1!5$$I/@T*#0H@(" @(" @(#PA+2T@+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BTM/@T* M(" @(" @(" \(2TM($-O;&]R&5L1&5P=&A)9"!.351/2T5. M("-)35!,245$( T*"0D)"4-O;&]R4W!A8V5)9" E8V]L;W)S<&%C95]E;G5M M.R B3D].12(^#0H)(" @(#PA+2T@+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BTM/@T*"0D\(2TM M($5X<&%N'!&;VYT0V%R9"Y&3TY44R -"@D)"0D) M"45X<$9O;G1.=6T@3DU43TM%3B C24U03$E%1#X-"@D)"0D)"3PA+2T@14Q% M345.5"!&;VYT("@C4$-$051!*2TM/@T*"0D)#0H)"0D\(45,14U%3E0@15A0 M1%503$584R H17AP1'5P;&5X*BD^#0H)"0D\(4%45$Q)4U0@15A01%503$58 M4R -"@D)"0EF17AP1'5P;&5X("5B;V]L7V%T=')I8G5T95]F86QS93L@#0H) M"0D)3G5M17AP1'5P;&5X($Y-5$]+14X@(C B/@T*"0D)"3PA14Q%345.5"!% M>'!$=7!L97@@*%!#1$%402Q005!%4E,I/@T*"0D)"0D\(2TM(#\_/S\_($9) M3DE32$E.1U,@+2T^#0H)"0D)"3PA+2T@14Q%345.5"!005!%4E,@*%!A<&5R M*2LM+3X-"@D)"0T*"0D)/"%%3$5-14Y4($584%!!4$524T]54D-%4R H17AP M4&%P97)3;W5R8V4J*3X-"@D)"3PA05143$E35"!%6%!005!%4E-/55)#15,@ M#0H)"0D)9D5X<%!A<&5R4V]U re-scope of UPDF In-Reply-To: <01BEE4B6.618F13A0@hpb13858.boi.hp.com> Message-ID: Item Subject: UPD> re-scope of UPDF I don't see any much overlap between IPP and UPDF. UPDF is the description of the printer, and is (should be?) transport independent. As far as I know, we haven't made IPP a required component of UPDF. I agree that we need to re-clarify. IPP is capable of retreiving facts about the printer, but UPDF expresses not only the facts, but how they relate to one another. If we steer toward Linux and Unix, then we need to drop the "U" from the comittee name, as it will no longer be universal, and will be of a much more limited interest to me. Regards, Ben B ______________________________ Reply Separator _________________________________ Subject: UPD> re-scope of UPDF Author: sandram-at-boi (sandram@boi.hp.com) at HP-Vancouver,shargw1 Date: 8/12/99 10:32 AM Hi, Even though the UPDF spec is coming along - the work is not as focused as it could be. I believe there are a couple of reasons for this. One being ther e sheer size of the task. We did an excellent job dividing the job into sections - UI, Localization, etc - but I haven't done a very good job keeping the work focused on a specific area. Another issue has been the usefulness of the project itself. Is UPDF really needed when IPP can retrieve some of the info from the printer? Can IPP and UPDF complement each other or is there maybe too much overlap? There also has been some thought about steering UPDF towards a Linux (and other Unix flavors) printing solution and not really a "Universal" solution. What do people think about that? Chuck sent out the DTD vs Schema link. This is something to look at. Als o please check out the UIML and XUL documents for User Interface specification in UPDF. thanks, Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From qaisi at apple.com Fri Aug 13 19:36:34 1999 From: qaisi at apple.com (Abdallah Qaisi) Date: Wed May 6 14:04:47 2009 Subject: UPD> re-scope of UPDF Message-ID: <199908132335.QAA25516@scv2.apple.com> Ben, Sandra, see my comments below. Abdallah Qaisi Apple Computer >Item Subject: UPD> re-scope of UPDF > I don't see any much overlap between IPP and UPDF. UPDF is the > description of the printer, and is (should be?) transport independent. > As far as I know, we haven't made IPP a required component of UPDF. > > I agree that we need to re-clarify. IPP is capable of retreiving > facts about the printer, but UPDF expresses not only the facts, but > how they relate to one another. > > If we steer toward Linux and Unix, then we need to drop the "U" from > the comittee name, "U" can stand for Unix too;) Dropping it causes a clash with Adobe PDF. > as it will no longer be universal, and will be of a > much more limited interest to me. > > Regards, > Ben B > > >______________________________ Reply Separator >_________________________________ >Subject: UPD> re-scope of UPDF >Author: sandram-at-boi (sandram@boi.hp.com) at HP-Vancouver,shargw1 >Date: 8/12/99 10:32 AM > > >Hi, > Even though the UPDF spec is coming along - the work is not as >focused >as it could be. I believe there are a couple of reasons for this. One >being ther >e >sheer size of the task. We did an excellent job dividing the job into >sections - > >UI, Localization, etc - but I haven't done a very good job keeping the work >focused on a specific area. > Another issue has been the usefulness of the project itself. Is >UPDF really needed when IPP can retrieve some of the info from >the printer? Can IPP and UPDF complement each other or is there maybe >too much overlap? > > There also has been some thought about steering UPDF towards >a Linux (and other Unix flavors) printing solution and not really a >"Universal" >solution. What do >people think about that? > > If UPDF is limited to Unix, how is it better than today's solution - PPD? I understand that one of the goals for UPDF is to support both Postscript and non-Postscript printers. But while PPD handles PS only, it does it nicely on all platforms not just Unix. My other thought: Is non-Postscript printing on Unix the biggest problem that UPDF is aiming to solve or the easiest problem to solve? If it's the biggest problem, then you may be heading in the right direction as long as you promise adding more platforms later. If on the other hand, you are doing it just for the sake of scoping down the project then I disagree with the direction. Finally, as you know, Apple's Mac OS X at the low level is Unix based so there may be ways we can support your new direction but I cannot say for sure until I see a better definition of the new UPDF proposal. At minimum, the XML portion of a UPDF file could easily be handled on OS X since the new OS already handles XML parsing at the system level. I'm not sure about the optional code modules (the UI and rendering plugins) - whether these binaries will be compatible or not. These are my thoughts at this time. Sorry for not being able to contribute much to this project. But I'm still watching and tracking it with interest. Thanks. Abdallah > > Chuck sent out the DTD vs Schema link. This is something to look >at. Als >o >please check out the UIML and XUL documents for User Interface >specification in >UPDF. > >thanks, >Sandra > >------------------------ >Sandra Matts >Hewlett-Packard >Engineer Scientist >sandram@boi.hp.com >(208) 396-4755 phone >(208) 396-5161 fax > From egglestn at lexmark.com Mon Aug 16 15:56:24 1999 From: egglestn at lexmark.com (egglestn@lexmark.com) Date: Wed May 6 14:04:47 2009 Subject: UPD> test Message-ID: <199908161956.PAA23782@interlock2.lexmark.com> This is just a test -Roger From sandra_matts at am.exch.hp.com Mon Aug 16 16:17:44 1999 From: sandra_matts at am.exch.hp.com (MATTS,SANDRA (HP-Boise,ex1)) Date: Wed May 6 14:04:47 2009 Subject: UPD> re-scope of UPDF Message-ID: Here is the copy of my email. For some reason it never makes it to the UPD email reflector. sandra -----Original Message----- From: MATTS,SANDRA (HP-Boise,ex1) Sent: Monday, August 16, 1999 1:08 PM To: 'upd@pwg.org' Subject: FW: UPD> re-scope of UPDF comments inline. -----Original Message----- From: Abdallah Qaisi [SMTP:qaisi@apple.com] Sent: Friday, August 13, 1999 5:37 PM To: BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com; sandram@boi.hp.com Cc: upd@pwg.org Subject: Re: UPD> re-scope of UPDF Ben, Sandra, see my comments below. Abdallah Qaisi Apple Computer >Item Subject: UPD> re-scope of UPDF > I don't see any much overlap between IPP and UPDF. UPDF is the > description of the printer, and is (should be?) transport independent. > As far as I know, we haven't made IPP a required component of UPDF. [Sandra Matts] It's true we haven't made IPP a requirement - UPDF is supposed to be protocol independent. However, that means we will have to create the xml that can be used with any network protocol and then provide the mapping from UPDF to the different protocols. This will be a large job and will require more time to do. We would have to schedule work time between meetings to get this done. In the interest of making UPDF useful to the largest number of printers - I believe this is the right thing to do. However, it would be helpful if I felt people would contribute input when we do the bi-di work. > > I agree that we need to re-clarify. IPP is capable of retreiving > facts about the printer, but UPDF expresses not only the facts, but > how they relate to one another. > > If we steer toward Linux and Unix, then we need to drop the "U" from > the comittee name, "U" can stand for Unix too;) Dropping it causes a clash with Adobe PDF. > as it will no longer be universal, and will be of a > much more limited interest to me. > > Regards, > Ben B > > [Sandra Matts] stuff deleted. > > There also has been some thought about steering UPDF towards >a Linux (and other Unix flavors) printing solution and not really a >"Universal" >solution. What do >people think about that? > > If UPDF is limited to Unix, how is it better than today's solution - PPD? I understand that one of the goals for UPDF is to support both Postscript and non-Postscript printers. But while PPD handles PS only, it does it nicely on all platforms not just Unix. [Sandra Matts] Good point. If we start scoping down the project in order to get it done, we have to make sure we don't eliminate the features that make it better and that solve the original problem. My other thought: Is non-Postscript printing on Unix the biggest problem that UPDF is aiming to solve or the easiest problem to solve? If it's the biggest problem, then you may be heading in the right direction as long as you promise adding more platforms later. If on the other hand, you are doing it just for the sake of scoping down the project then I disagree with the direction. Finally, as you know, Apple's Mac OS X at the low level is Unix based so there may be ways we can support your new direction but I cannot say for sure until I see a better definition of the new UPDF proposal. At minimum, the XML portion of a UPDF file could easily be handled on OS X since the new OS already handles XML parsing at the system level. I'm not sure about the optional code modules (the UI and rendering plugins) - whether these binaries will be compatible or not. [Sandra Matts] In order to keep it useful for the largest number of OSs - we should do as much specification in XML and only resort to binaries when absolutely needed. These are my thoughts at this time. Sorry for not being able to contribute much to this project. But I'm still watching and tracking it with interest. Thanks. Abdallah > > Chuck sent out the DTD vs Schema link. This is something to look >at. Als >o >please check out the UIML and XUL documents for User Interface >specification in >UPDF. > >thanks, >Sandra > >------------------------ >Sandra Matts >Hewlett-Packard >Engineer Scientist >sandram@boi.hp.com >(208) 396-4755 phone >(208) 396-5161 fax > From egglestn at lexmark.com Mon Aug 16 15:52:48 1999 From: egglestn at lexmark.com (egglestn@lexmark.com) Date: Wed May 6 14:04:47 2009 Subject: No subject Message-ID: <199908162020.QAA01221@pwg.org> This is just a test.... -Roger From sandra_matts at am.exch.hp.com Mon Aug 16 15:07:39 1999 From: sandra_matts at am.exch.hp.com (MATTS,SANDRA (HP-Boise,ex1)) Date: Wed May 6 14:04:47 2009 Subject: FW: UPD> re-scope of UPDF Message-ID: comments inline. -----Original Message----- From: Abdallah Qaisi [SMTP:qaisi@apple.com] Sent: Friday, August 13, 1999 5:37 PM To: BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com; sandram@boi.hp.com Cc: upd@pwg.org Subject: Re: UPD> re-scope of UPDF Ben, Sandra, see my comments below. Abdallah Qaisi Apple Computer >Item Subject: UPD> re-scope of UPDF > I don't see any much overlap between IPP and UPDF. UPDF is the > description of the printer, and is (should be?) transport independent. > As far as I know, we haven't made IPP a required component of UPDF. [Sandra Matts] It's true we haven't made IPP a requirement - UPDF is supposed to be protocol independent. However, that means we will have to create the xml that can be used with any network protocol and then provide the mapping from UPDF to the different protocols. This will be a large job and will require more time to do. We would have to schedule work time between meetings to get this done. In the interest of making UPDF useful to the largest number of printers - I believe this is the right thing to do. However, it would be helpful if I felt people would contribute input when we do the bi-di work. > > I agree that we need to re-clarify. IPP is capable of retreiving > facts about the printer, but UPDF expresses not only the facts, but > how they relate to one another. > > If we steer toward Linux and Unix, then we need to drop the "U" from > the comittee name, "U" can stand for Unix too;) Dropping it causes a clash with Adobe PDF. > as it will no longer be universal, and will be of a > much more limited interest to me. > > Regards, > Ben B > > [Sandra Matts] stuff deleted. > > There also has been some thought about steering UPDF towards >a Linux (and other Unix flavors) printing solution and not really a >"Universal" >solution. What do >people think about that? > > If UPDF is limited to Unix, how is it better than today's solution - PPD? I understand that one of the goals for UPDF is to support both Postscript and non-Postscript printers. But while PPD handles PS only, it does it nicely on all platforms not just Unix. [Sandra Matts] Good point. If we start scoping down the project in order to get it done, we have to make sure we don't eliminate the features that make it better and that solve the original problem. My other thought: Is non-Postscript printing on Unix the biggest problem that UPDF is aiming to solve or the easiest problem to solve? If it's the biggest problem, then you may be heading in the right direction as long as you promise adding more platforms later. If on the other hand, you are doing it just for the sake of scoping down the project then I disagree with the direction. Finally, as you know, Apple's Mac OS X at the low level is Unix based so there may be ways we can support your new direction but I cannot say for sure until I see a better definition of the new UPDF proposal. At minimum, the XML portion of a UPDF file could easily be handled on OS X since the new OS already handles XML parsing at the system level. I'm not sure about the optional code modules (the UI and rendering plugins) - whether these binaries will be compatible or not. [Sandra Matts] In order to keep it useful for the largest number of OSs - we should do as much specification in XML and only resort to binaries when absolutely needed. These are my thoughts at this time. Sorry for not being able to contribute much to this project. But I'm still watching and tracking it with interest. Thanks. Abdallah > > Chuck sent out the DTD vs Schema link. This is something to look >at. Als >o >please check out the UIML and XUL documents for User Interface >specification in >UPDF. > >thanks, >Sandra > >------------------------ >Sandra Matts >Hewlett-Packard >Engineer Scientist >sandram@boi.hp.com >(208) 396-4755 phone >(208) 396-5161 fax > From sandram at boi.hp.com Mon Aug 16 11:24:13 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: FW: UPD> re-scope of UPDF Message-ID: <01BEE7C9.1B8E35A0@hpb13858.boi.hp.com> -----Original Message----- From: Sandra Matts [SMTP:sandram@boi.hp.com] Sent: Sunday, August 15, 1999 12:17 PM To: 'Abdallah Qaisi'; BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com Cc: upd@pwg.org Subject: RE: UPD> re-scope of UPDF comments inline. -----Original Message----- From: Abdallah Qaisi [SMTP:qaisi@apple.com] Sent: Friday, August 13, 1999 5:37 PM To: BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com; sandram@boi.hp.com Cc: upd@pwg.org Subject: Re: UPD> re-scope of UPDF Ben, Sandra, see my comments below. Abdallah Qaisi Apple Computer >Item Subject: UPD> re-scope of UPDF > I don't see any much overlap between IPP and UPDF. UPDF is the > description of the printer, and is (should be?) transport independent. > As far as I know, we haven't made IPP a required component of UPDF. [Sandra Matts] It's true we haven't made IPP a requirement - UPDF is supposed to be protocol independent. However, that means we will have to create the xml that can be used with any network protocol and then provide the mapping from UPDF to the different protocols. This will be a large job and will require more time to do. We would have to schedule work time between meetings to get this done. In the interest of making UPDF useful to the largest number of printers - I believe this is the right thing to do. However, it would be helpful if I felt people would contribute input when we do the bi-di work. > > I agree that we need to re-clarify. IPP is capable of retreiving > facts about the printer, but UPDF expresses not only the facts, but > how they relate to one another. > > If we steer toward Linux and Unix, then we need to drop the "U" from > the comittee name, "U" can stand for Unix too;) Dropping it causes a clash with Adobe PDF. > as it will no longer be universal, and will be of a > much more limited interest to me. > > Regards, > Ben B > > [Sandra Matts] stuff deleted. > > There also has been some thought about steering UPDF towards >a Linux (and other Unix flavors) printing solution and not really a >"Universal" >solution. What do >people think about that? > > If UPDF is limited to Unix, how is it better than today's solution - PPD? I understand that one of the goals for UPDF is to support both Postscript and non-Postscript printers. But while PPD handles PS only, it does it nicely on all platforms not just Unix. [Sandra Matts] Good point. If we start scoping down the project in order to get it done, we have to make sure we don't eliminate the features that make it better and that solve the original problem. My other thought: Is non-Postscript printing on Unix the biggest problem that UPDF is aiming to solve or the easiest problem to solve? If it's the biggest problem, then you may be heading in the right direction as long as you promise adding more platforms later. If on the other hand, you are doing it just for the sake of scoping down the project then I disagree with the direction. Finally, as you know, Apple's Mac OS X at the low level is Unix based so there may be ways we can support your new direction but I cannot say for sure until I see a better definition of the new UPDF proposal. At minimum, the XML portion of a UPDF file could easily be handled on OS X since the new OS already handles XML parsing at the system level. I'm not sure about the optional code modules (the UI and rendering plugins) - whether these binaries will be compatible or not. [Sandra Matts] In order to keep it useful for the largest number of OSs - we should do as much specification in XML and only resort to binaries when absolutely needed. These are my thoughts at this time. Sorry for not being able to contribute much to this project. But I'm still watching and tracking it with interest. Thanks. Abdallah > > Chuck sent out the DTD vs Schema link. This is something to look >at. Als >o >please check out the UIML and XUL documents for User Interface >specification in >UPDF. > >thanks, >Sandra > >------------------------ >Sandra Matts >Hewlett-Packard >Engineer Scientist >sandram@boi.hp.com >(208) 396-4755 phone >(208) 396-5161 fax > From egglestn at lexmark.com Tue Aug 17 08:54:24 1999 From: egglestn at lexmark.com (egglestn@lexmark.com) Date: Wed May 6 14:04:47 2009 Subject: UPD> Test Message-ID: <199908171254.IAA05711@interlock2.lexmark.com> This is just a test.... -Roger From egglestn at lexmark.com Wed Aug 18 08:50:42 1999 From: egglestn at lexmark.com (egglestn@lexmark.com) Date: Wed May 6 14:04:47 2009 Subject: UPD> Test Message-ID: <199908181251.IAA08605@interlock2.lexmark.com> This is just a test -Roger From egglestn at lexmark.com Wed Aug 18 10:49:40 1999 From: egglestn at lexmark.com (egglestn@lexmark.com) Date: Wed May 6 14:04:47 2009 Subject: UPD> test Message-ID: <199908181450.KAA06298@interlock2.lexmark.com> Testing...please ignore -Roger From sandram at boi.hp.com Fri Aug 20 10:33:28 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> test - ignore Message-ID: <01BEEAE6.ADD8D940@hpb13858.boi.hp.com> My email is bouncing - just testing. ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Sun Aug 15 14:16:50 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> re-scope of UPDF Message-ID: <01BEE718.0E823C00@hpb13858.boi.hp.com> comments inline. -----Original Message----- From: Abdallah Qaisi [SMTP:qaisi@apple.com] Sent: Friday, August 13, 1999 5:37 PM To: BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com; sandram@boi.hp.com Cc: upd@pwg.org Subject: Re: UPD> re-scope of UPDF Ben, Sandra, see my comments below. Abdallah Qaisi Apple Computer >Item Subject: UPD> re-scope of UPDF > I don't see any much overlap between IPP and UPDF. UPDF is the > description of the printer, and is (should be?) transport independent. > As far as I know, we haven't made IPP a required component of UPDF. [Sandra Matts] It's true we haven't made IPP a requirement - UPDF is supposed to be protocol independent. However, that means we will have to create the xml that can be used with any network protocol and then provide the mapping from UPDF to the different protocols. This will be a large job and will require more time to do. We would have to schedule work time between meetings to get this done. In the interest of making UPDF useful to the largest number of printers - I believe this is the right thing to do. However, it would be helpful if I felt people would contribute input when we do the bi-di work. > > I agree that we need to re-clarify. IPP is capable of retreiving > facts about the printer, but UPDF expresses not only the facts, but > how they relate to one another. > > If we steer toward Linux and Unix, then we need to drop the "U" from > the comittee name, "U" can stand for Unix too;) Dropping it causes a clash with Adobe PDF. > as it will no longer be universal, and will be of a > much more limited interest to me. > > Regards, > Ben B > > [Sandra Matts] stuff deleted. > > There also has been some thought about steering UPDF towards >a Linux (and other Unix flavors) printing solution and not really a >"Universal" >solution. What do >people think about that? > > If UPDF is limited to Unix, how is it better than today's solution - PPD? I understand that one of the goals for UPDF is to support both Postscript and non-Postscript printers. But while PPD handles PS only, it does it nicely on all platforms not just Unix. [Sandra Matts] Good point. If we start scoping down the project in order to get it done, we have to make sure we don't eliminate the features that make it better and that solve the original problem. My other thought: Is non-Postscript printing on Unix the biggest problem that UPDF is aiming to solve or the easiest problem to solve? If it's the biggest problem, then you may be heading in the right direction as long as you promise adding more platforms later. If on the other hand, you are doing it just for the sake of scoping down the project then I disagree with the direction. Finally, as you know, Apple's Mac OS X at the low level is Unix based so there may be ways we can support your new direction but I cannot say for sure until I see a better definition of the new UPDF proposal. At minimum, the XML portion of a UPDF file could easily be handled on OS X since the new OS already handles XML parsing at the system level. I'm not sure about the optional code modules (the UI and rendering plugins) - whether these binaries will be compatible or not. [Sandra Matts] In order to keep it useful for the largest number of OSs - we should do as much specification in XML and only resort to binaries when absolutely needed. These are my thoughts at this time. Sorry for not being able to contribute much to this project. But I'm still watching and tracking it with interest. Thanks. Abdallah > > Chuck sent out the DTD vs Schema link. This is something to look >at. Als >o >please check out the UIML and XUL documents for User Interface >specification in >UPDF. > >thanks, >Sandra > >------------------------ >Sandra Matts >Hewlett-Packard >Engineer Scientist >sandram@boi.hp.com >(208) 396-4755 phone >(208) 396-5161 fax > From sandram at boi.hp.com Mon Aug 30 10:46:17 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> phone conf tomorrow Message-ID: <01BEF2C4.B1135AA0@hpb13858.boi.hp.com> Hi, At the last meeting we discussed having a phone conference to discuss UI requirements and specifics. The phone number for our phone conference is 612-315-6802 The access code is 058459494 I will activate the number on August 31 from 10-12 Pacific time. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From charles.a.adams at exgate.tek.com Mon Aug 30 13:18:32 1999 From: charles.a.adams at exgate.tek.com (charles.a.adams@exgate.tek.com) Date: Wed May 6 14:04:47 2009 Subject: UPD> UPDF User Interface Requirements Document Message-ID: <6B57A2A3212BD2119C2600805F6F14130278751A@us-wv-m11.wv.tek.com> Folks, Sorry things were a bit hectic last week. So the requirements document has not gotten the work it deserves. But I thought we might discuss it (such that it is) tomorrow and then I can put more work into it this week. <> Charles "Chuck" Adams adamsc@pogo.wv.tek.com Tektronix, Inc. Color Printing and Imaging Division -------------- next part -------------- A non-text attachment was scrubbed... Name: updf_ui_reqs.doc Type: application/msword Size: 22528 bytes Desc: not available Url : http://www.pwg.org/archives/upd/attachments/19990830/312c06d3/updf_ui_reqs.doc From jkm at underscore.com Mon Aug 30 13:37:09 1999 From: jkm at underscore.com (Jay Martin) Date: Wed May 6 14:04:47 2009 Subject: UPD> UPDF User Interface Requirements Document References: <6B57A2A3212BD2119C2600805F6F14130278751A@us-wv-m11.wv.tek.com> Message-ID: <37CAC145.269BBC0C@underscore.com> How does UPDF differ/compare with Adobe's PPD files? On the surface (to the uninformed reader) this effort appears to simply replace what exists in PPD files. Surely, I'm missing something here, so any enlightenment would be appreciated. ...jay From charles.a.adams at exgate.tek.com Mon Aug 30 14:54:32 1999 From: charles.a.adams at exgate.tek.com (charles.a.adams@exgate.tek.com) Date: Wed May 6 14:04:47 2009 Subject: UPD> UPDF User Interface Requirements Document Message-ID: <6B57A2A3212BD2119C2600805F6F14130278751E@us-wv-m11.wv.tek.com> The requirements are a super-set of PPD's functionality. Specifically, PPD's have a very limited UI capability. In addition, since UPDF is XML-based I believe we will be able to take advantage of the development of UI tools being done for XML. Chuck Adams > -----Original Message----- > From: Jay Martin [SMTP:jkm@underscore.com] > Sent: Monday, August 30, 1999 10:37 AM > To: Adams, Charles A > Cc: upd@pwg.org > Subject: Re: UPD> UPDF User Interface Requirements Document > > How does UPDF differ/compare with Adobe's PPD files? > On the surface (to the uninformed reader) this effort > appears to simply replace what exists in PPD files. > Surely, I'm missing something here, so any enlightenment > would be appreciated. > > ...jay From sandra_matts at am.exch.hp.com Tue Aug 31 13:04:40 1999 From: sandra_matts at am.exch.hp.com (MATTS,SANDRA (HP-Boise,ex1)) Date: Wed May 6 14:04:47 2009 Subject: UPD> phone conf Message-ID: Hi, Is anybody joining the conf today? Sandra Sandra Matts Engineer Scientist Hewlett-Packard sandram@boi.hp.com (208) 396-4755 phone From charles.a.adams at exgate.tek.com Tue Sep 7 16:25:39 1999 From: charles.a.adams at exgate.tek.com (charles.a.adams@exgate.tek.com) Date: Wed May 6 14:04:48 2009 Subject: UPD> UPDF User Interface Requirements Document Update Message-ID: <6B57A2A3212BD2119C2600805F6F141302787566@us-wv-m11.wv.tek.com> Folks, The attached update is based on the teleconference feedback. Hope this captured all the issues raised. Charles "Chuck" Adams adamsc@pogo.wv.tek.com Tektronix, Inc. <> -------------- next part -------------- A non-text attachment was scrubbed... Name: updf_ui_reqs.doc Type: application/msword Size: 38912 bytes Desc: not available Url : http://www.pwg.org/archives/upd/attachments/19990907/a876869f/updf_ui_reqs.doc From sandram at boi.hp.com Mon Sep 13 12:03:48 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:48 2009 Subject: UPD> phone conf tomorrow Message-ID: <01BEFDCF.4653B0A0@hpb13858.boi.hp.com> Hi, At the last meeting we discussed having a phone conference to discuss UI requirements and specifics. The phone number for our phone conference is 612-315-6802 The access code is 058459494 I will activate the number on September 14 (Tuesday) from 10-11 Pacific time. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From mwu at kodak.com Tue Sep 14 13:53:50 1999 From: mwu at kodak.com (mwu@kodak.com) Date: Wed May 6 14:04:48 2009 Subject: UPD> IPP> ANNOUNCEMENT: Common UNIX Printing System 1.0 Beta 9 Message-ID: <852567EC.0061DA06.00@knotes.kodak.com> From: Michael Wu FYI ---------------------- Forwarded by Michael Wu/414061/OI/EKC on 09/14/99 01:56 PM --------------------------- Michael Sweet on 09/03/99 05:30:31 PM To: IPP Mailing List cc: (bcc: Michael Wu/414061/OI/EKC) Subject: IPP> ANNOUNCEMENT: Common UNIX Printing System 1.0 Beta 9 -------------- next part -------------- The 8th beta release of the Common UNIX Printing System ("CUPS") is now available for download from the CUPS web site at: http://www.cups.org Binaries for several platforms are also available! The Common UNIX Printing System provides a portable printing layer for UNIX? operating systems. It has been developed by Easy Software Products to promote a standard printing solution for all UNIX vendors and users. CUPS provides the System V and Berkeley command-line interfaces. CUPS uses the Internet Printing Protocol (IETF-IPP) as the basis for managing print jobs and queues. The Line Printer Daemon (LPD, RFC1179), Server Message Block (SMB), and AppSocket protocols are also supported with reduced functionality. CUPS adds network printer browsing and PostScript Printer Description ("PPD")-based printing options to support real world applications under UNIX. CUPS also includes a customized version of GNU GhostScript (currently based off GNU GhostScript 4.03) and an image file RIP that can be used to support non-PostScript printers. Sample drivers are provided for HP DeskJet and LaserJet printers. Drivers for over 1500 printers are available in our ESP Print Pro software. CUPS is licensed under the GNU General Public License. Please contact Easy Software Products for commercial support and "binary distribution" rights. Changes since the last release include: - The IPP backend wasn't appending a 0-length chunk when needed. - You couldn't add a printer if there was a remote class of the same name, and visa-versa. - The setgid() and setuid() calls were backwards in the scheduler. - The scheduler didn't always log printer status messages; this should be fixed now. - Filter creation and death are now logged (debug level only.) This should better aid filter debugging. - The image library code was using lseek() after rewind() to ensure that the file descriptor was at the beginning of the file. This was needed for the TIFF image handler but broke the rest of the file formats. Moved the lseek() to the TIFF image handler... -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike@easysw.com Printing Software for UNIX http://www.easysw.com From sandram at boi.hp.com Tue Sep 21 20:30:06 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:48 2009 Subject: UPD> investigation results of UIML and XUL Message-ID: <01BF045F.54B4C300@hpb13858.boi.hp.com> Hi, At the last phone conference it was decided to see if either UIML or XUL is a good fit for UPDF User Interface definition. Mike Yeung from Canon wrote up results of his investigation of UIML and I did the XUL. I've copied both of these to the ftp site. ftp://ftp.pwg.org/pub/upd/Archive/1999/ XULstudy.doc and UserInterfaceMarkupLanguagestudy.doc are the files. Please download for discussion on Friday's UPDF meeting. I will try to bring hard copies to the meeting if needed. thanks, Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From owner-upd at pwg.org Mon Sep 27 11:28:23 1999 From: owner-upd at pwg.org (owner-upd@pwg.org) Date: Wed May 6 14:04:48 2009 Subject: No subject Message-ID: <199909271528.LAA01793@pwg.org> From sandra_matts at am.exch.hp.com Mon Oct 4 13:40:30 1999 From: sandra_matts at am.exch.hp.com (MATTS,SANDRA (HP-Boise,ex1)) Date: Wed May 6 14:04:48 2009 Subject: UPD> UPDF phone conf. Message-ID: Hi All, We are scheduled to have a UPDF phone conference tomorow - Tuesday from 10-11am Pacific tme. We will discuss the last UPDF meetings and any action items from that meeting. Phone number is 612-315-6802 access code is 058459494 I do have minutes done from the last meeting. I just have to copy them to the ftp site. I will do that today. Sandra Matts Sandra Matts Engineer Scientist Hewlett-Packard sandram@boi.hp.com (208) 396-4755 phone From charles.a.adams at exgate.tek.com Tue Oct 5 14:03:50 1999 From: charles.a.adams at exgate.tek.com (charles.a.adams@exgate.tek.com) Date: Wed May 6 14:04:48 2009 Subject: UPD> Tools for XML and XSL Message-ID: <6B57A2A3212BD2119C2600805F6F1413027875EE@us-wv-m11.wv.tek.com> Folks, Here is a not so recent article on tools for XML. Several of them also handle CSS and XSL. http://www.internetwk.com/lead/lead081099.htm Charles "Chuck" Adams adamsc@pogo.wv.tek.com Tektronix, Inc. From sandram at boi.hp.com Tue Oct 19 11:12:39 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:48 2009 Subject: UPD> phone conference today Message-ID: <01BF1A12.A19519E0@hpb13858.boi.hp.com> Hi All, Sorry for late reminder - but we are scheduled for a phone conference today at 10am Pacific time. We are supposed to discuss style sheets and how they fit in with the UPDF UI XML. The phone number for our phone conference is 612-315-6802 The access code is 058459494 Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From nschade at xionics.com Tue Oct 19 07:27:01 1999 From: nschade at xionics.com (Norbert Schade) Date: Wed May 6 14:04:48 2009 Subject: UPD> Arbortext contact Message-ID: <001e01bf1a24$dd6cc0a0$c31343ce@gca-2.xionics.com> All, I contacted Arbortext today. They will send me a sample package for evaluation very soon. It will mainly include info about the ADEPT series. I will keep you informed about it. The homepage is just arbortext.com. Norbert From BEN_BREZINSKI at HP-Vancouver-om1.om.hp.com Tue Oct 19 14:16:43 1999 From: BEN_BREZINSKI at HP-Vancouver-om1.om.hp.com (BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com) Date: Wed May 6 14:04:48 2009 Subject: UPD> Error in line 658 using XMLPro Message-ID: I have found out that this error message is referring to a line number in the DTD. By deleting the offending lines I was able to get clj4500.xml to load. I have not found the specific errors, but will keep you posted. Regards, Ben Brezinski Hewlett Packard From BEN_BREZINSKI at HP-Vancouver-om1.om.hp.com Tue Oct 19 14:26:20 1999 From: BEN_BREZINSKI at HP-Vancouver-om1.om.hp.com (BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com) Date: Wed May 6 14:04:48 2009 Subject: UPD> More info on "Error in Line 658" using XMLPro Message-ID: The error message "whitespace expected" is literal. In the offending line, there really needs to be a whitespace between EXPUNITS and the '('. There is a similar mistake further up aroune line 258. Regards, Ben Brezinski Hewlett Packard From sandram at boi.hp.com Thu Oct 21 11:58:37 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:48 2009 Subject: UPD> current dtd and xml file Message-ID: <01BF1BAA.D959E240@hpb13858.boi.hp.com> Hi All, I believe people are using an older dtd and color laserjet 4500 updf file. I'm attaching the version I'm using currently. I just loaded it with the shareware version of XML Pro and it seemed to work. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax begin 600 CLJ4500.xml M/#]X;6P@=F5R2!B87-I8R!54$1&(&9I M;&4@=VET:"!J=7-T('1H92!M:6YI;75M(')E<75I7,@551&+3@N#0H-"B @("!,;V-A;&5S('-U M<'!O2!T:&ES(%501$8@9FEL92X-"CPA+2T@+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+B M+3X-"B @(" \3&]C86QE3&ES=#X-"B @(" @(" @/$QO8V%L92!, M;V-A;&5)9#TB96Y?054B/CPO3&]C86QE/@T*(" @(" @(" \3&]C86QE($QO M8V%L94ED/2)E;E]'0B(^/"],;V-A;&4^#0H@(" @(" @(#Q,;V-A;&4@3&]C M86QE260](F5N7U53(CX\+TQO8V%L93X-"B @(" @(" @/$QO8V%L92!,;V-A M;&5)9#TB9&%?1$LB/CPO3&]C86QE/@T*(" @(" @(" \0W5S=&]M3&]C86QE M#0H@(" @(" @(" @("!#=7-T;VU,;V-A;&5)9#TB96Y?54LB/CPO0W5S=&]M M3&]C86QE/@T*(" @(" @(" \0W5S=&]M3&]C86QE#0H@(" @(" @(" @("!# M=7-T;VU,;V-A;&5)9#TB86%?0D(B/CPO0W5S=&]M3&]C86QE/@T*(" @(#PO M3&]C86QE3&ES=#X-"@T*(" @(#Q&:6QE3F%M93Y#3$HT-3 P+GAM;#PO1FEL M94YA;64^#0H-"B @(" \0W5S=&]M1&5V:6-E0V%P5&%G7!E-#(B+SX-"B @(" \+T-U M7-I8V%L/@T*(" @(" @(" @(" @(" @(#Q%;F=I M;F4^/"]%;F=I;F4^#0H@(" @(" @(" @(" @(" @/%)!32!F4D%-/2)44E5% M(CX-"B @(" @(" @(" @(" @(" @(" @/%)!32Y);G1EF5+ M8CTB-# Y-B(^/"]204TN26YT97)N86P^#0H@(" @(" @(" @(" @(" @/"]2 M04T^#0H@(" @(" @(" @(" @(" @/%)/32!F4D]-/2)&04Q312(^/"]23TT^ M#0H@(" @(" @(" @(" @(" @/$-O;&]R('1#;VQOF50=#TB,3 B( T*(" @(" @(" @(" @(" @(" @("!$969A=6QT1F]N M=$1"0U,](DYO;F4B/D-O=7)I97(-"B @(" @(" @(" @(" @(" \+T1E9F%U M;'1&;VYT/@T*(" @(" @(" @(" @(" @(#Q);G1EF4-"B @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q524-O;G1R;VP^#0H@ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @/$QIF4] M(E12544B#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @2&5L<%1E>'0](DAE;'!-92(-"B @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @("!3:&]R=&-U=$ME>3TB>2(O/DQA>6]U= T*(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @/%5)0V]N=')O;#X- M"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" \4F%D M:6]"=71T;VY'3TB4"(-"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @($-O;6UA;F0](F-M9"(O/@T*(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" \4F%D:6]"=71T;VX- M"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(%5)3&%B96P](DQA;F1S8V%P92(-"B @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(%-H;W)T8W5T2V5Y/2),(@T* M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @0V]M;6%N9#TB8VUD(B\^#0H@(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @/"]2861I;T)U='1O;D=R;W5P/@T*(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @/"]524-O;G1R;VP^#0H@(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" \54E#;VYT#X\+T-H96-K0F]X/@T*(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @/"]524-O;G1R;VP^#0H@(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(#PO54E&96%T=7)E/@T*(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" \54E&96%T=7)E/@T*(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" \54E!='1R:6)U=&5S#0H@(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @54E$:7-P;&%Y3F%M93TB4&%P97(@ M4V]UF4](E12544B#0H@(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @2&5L<%1E>'0](DAE;'!-92(-"B @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @("!3:&]R=&-U=$ME>3TB M3R(O/E!A<&5R4V]U3TB9"(O/D1U<&QE> T*(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" \54E#;VYT'0](DAE;'!-92(O/DUE9&EA#0H@(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(#Q524-O;G1R;VP^#0H@(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" \3&ES=#X-"B @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" \271E;4EN3&ES= T*(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @("!524QA M8F5L/2)0;&%I;B(-"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @0V]M;6%N9#TB8VUD(B\^#0H@(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" \+TQIF4](D1-4$%015)?3$545$52(B\^#0H@(" @(" @(" @(" @ M(" @(" @(" @(" @(" @/"]$4$QO8V%L93X-"B @(" @(" @(" @(" @(" @ M(" @(" @(" @(" \1%!,;V-A;&4-"B @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @3&]C86QE260](F1A7T1+(CX-"B @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @/$104PT*(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @1&5F875L=%!A<&5R4VEZ93TB1$U005!%4E]!-"(O/@T* M(" @(" @(" @(" @(" @(" @(" @(" @(" @(#PO1%!,;V-A;&4^#0H@(" @ M(" @(" @(" @(" @(" @(" @(" @(" @/$103&]C86QE#0H@(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @($QO8V%L94ED/2)E;E]'0B(^#0H@(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q$4%,-"B @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @($1E9F%U;'1087!EF4](D1- M4$%015)?030B+SX-"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M/$104PT*(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @1&5F M875L=%!A<&5R4VEZ93TB1$U005!%4E],151415(B+SX-"B @(" @(" @(" @ M(" @(" @(" @(" @(" @(" \+T103&]C86QE/@T*(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(#Q$4$-U#TB-C$R(B!Y/2(W.3(B+SX- M"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @/%!A<&5R+D%R96$N M#TB-3DU(B!Y/2(X-#(B+SX-"B @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @/%!A<&5R+D%R96$NF5-;3$P('@](C$Q,3$B('D](C$Q,3$B+SX- M"B @(" @(" @(" @(" @(" @(" @(" @(" @(" \+U!A<&5R+D%R96$^#0H@ M(" @(" @(" @(" @(" @(" @(" @(" \+U!A<&5R/@T*(" @(" @(" @(" @ M(" @(" @(" @(" @/%!A<&5R(&1M<&%P97)S:7IE/2)$35!!4$527TQ%1T%, M(CY,96=A; T*(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q087!EF5-;3$P('@](C$Q,3$B('D](C$Q,3$B+SX- M"B @(" @(" @(" @(" @(" @(" @(" @(" @(" \+U!A<&5R+D%R96$^#0H@ M(" @(" @(" @(" @(" @(" @(" @(" \+U!A<&5R/@T*#0H@(" @(" @(" @ M(" @(" @(" @(" @(" \4&%P97(@9&UP87!EF4](D1-4$%015)?15A% M0U54259%(CY%>&5C=71I=F4-"B @(" @(" @(" @(" @(" @(" @(" @(" @ M(" \4&%P97(N07)E83X-"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @/%!A<&5R+D%R96$N<'1!#TB-3(R(B!Y/2(W-38B+SX- M"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @/%!A<&5R+D%R96$N MF5-;3$P('@](C$Q,3$B('D] M(C$Q,3$B+SX-"B @(" @(" @(" @(" @(" @(" @(" @(" @(" \+U!A<&5R M+D%R96$^#0H@(" @(" @(" @(" @(" @(" @(" @(" \+U!A<&5R/@T*#0H@ M(" @(" @(" @(" @(" @(" @(" @(" \4&%P97(@9&UP87!EF4](D1- M4$%015)?034B/D$U#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @/%!A M<&5R+D%R96$^#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q0 M87!E&5L('@](C0R,"(@>3TB-3DU(B\^#0H@(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q087!E&5L#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @;&5F=#TB,3(N,# B('1O<#TB,3(N,3(B(')I9VAT/2(U,#,N.#@B M(&)O='1O;3TB-S$U+CDR(B\^#0H@(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(#Q087!E#TB,3$Q,2(@>3TB,3$Q M,2(O/@T*(" @(" @(" @(" @(" @(" @(" @(" @(" @(#PO4&%P97(N07)E M83X-"B @(" @(" @(" @(" @(" @(" @(" @(#PO4&%P97(^#0H-"B @(" @ M(" @(" @(" @(" @(" @(" @(#Q087!E&5L('@](C0Y.2(@>3TB-S Y M(B\^#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q087!E&5L('@](C(Y M-R(@>3TB-C@T(B\^#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(#Q087!E#TB-#4Y(B!Y/2(V-#DB+SX-"B @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @/%!A<&5R+D%R96$NF5-;3$P('@](C$Q,3$B('D](C$Q,3$B+SX-"B @(" @(" @(" @(" @ M(" @(" @(" @(" @(" \+U!A<&5R+D%R96$^#0H@(" @(" @(" @(" @(" @ M(" @(" @(" \+U!A<&5R/@T*#0H@(" @(" @(" @(" @(" @(" @(" @(" \ M4&%P97(@9&UP87!EF4](D1-4$%015)?14Y67T1,(CY%;G9E;&]P92!$ M3 T*(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q087!E&5L#0H@ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @;&5F=#TB M,3(N,# B('1O<#TB,3(N,3(B(')I9VAT/2(R.3DN-C0B(&)O='1O;3TB-C$Q M+C0R(B\^#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q087!E M#TB,3$Q,2(@>3TB,3$Q,2(O/@T*(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(#PO4&%P97(N07)E83X-"B @(" @(" @ M(" @(" @(" @(" @(" @(#PO4&%P97(^#0H-"B @(" @(" @(" @(" @(" @ M(" @(" @(#Q087!E&5L#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @;&5F=#TB,3(N,# B('1O<#TB,3(N,3(B(')I9VAT/2(R M-C8N-S8B(&)O='1O;3TB-3(W+CDP(B\^#0H@(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(#Q087!E#TB,3$Q,2(@ M>3TB,3$Q,2(O/@T*(" @(" @(" @(" @(" @(" @(" @(" @(" @(#PO4&%P M97(N07)E83X-"B @(" @(" @(" @(" @(" @(" @(" @(#PO4&%P97(^#0H- M"B @(" @(" @(" @(" @(" @(" @/"]005!%4E,^#0H-"B @(" @(" @(" @ M(" @(" @(" @/"$M+2 N+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN("TM/@T*(" @(" @(" @ M(" @(" @(" @(" \(2TM(%5S97(@1&5F:6YE(%!A<&5R($EN9F\@(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @+2T^#0H@(" @(" @ M(" @(" @(" @(" @(#PA+2T@+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+B M+3X-"B @(" @ M(" @(" @(" @(" @(" @/%5$4$E.1D]3(&951%!);F9O/2)&04Q312(^#0H@ M(" @(" @(" @(" @(" @(" @(#PO541024Y&3U,^#0H@(" @(" @(" @(" @ M(" @(" @(#PA+2T@+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+B M+3X-"B @(" @(" @(" @ M(" @(" @(" @/"$M+2!-961I82!S:&]U;&0@8F4@82!G2(^5')A;G-P87)E;F-Y/"]-961I83X-"B @(" @(" @(" @(" @ M(" @(" @(" @(#Q-961I82 -"B @(" @(" @(" @(" @(" @(" @(" @(" @ M("!-961I84ED/2),86)E;',B/DQA8F5L#TB3TXB M/CPO1'5P;&5X/@T*(" @(" @(" @(" @(" @(" @(" \0F]O:VQE="!T0F]O M:VQE=#TB3T9&(B\^#0H@(" @(" @(" @(" @(" @(" @(#Q#96YT97)&;VQD M06YD4W1A<&QE/CPO0V5N=&5R1F]L9$%N9%-T87!L93X-"B @(" @(" @(" @ M(" @(" @(" @/%)E=F5R#X-"B @(" @(" @(" @ M(" @(" @(" @/%-T87!L93X\+U-T87!L93X-"B @(" @(" @(" @(" @(" @ M(" @/$9/3$13/CPO1D],1%,^#0H@(" @(" @(" @(" @(" @(" @(#Q(;VQE M4'5N8V@^/"](;VQE4'5N8V@^#0H@(" @(" @(" @(" @(" @/"]&24Y)4TA) M3D=3/@T*(" @(" @(" @(" @(" @(#Q#;VQO7-T96US+"!);F,@(" @(" @(" @(" @(" @(" @(" @(" M+3X-"CPA+2T@ M4')I;G1EF5?96YU;2 -"@DG*"!&04Q317P-"@E$35!!4$527TQ% M5%1%4GP-"@E$35!!4$527TQ%5%1%4E--04Q,? T*"41-4$%015)?5$%"3$]) M1'P-"@E$35!!4$527TQ%1$=%4GP-"@E$35!!4$527TQ%1T%,? T*"41-4$%0 M15)?4U1!5$5-14Y4? T*"41-4$%015)?15A%0U54259%? T*"41-4$%015)? M03-\#0H)1$U005!%4E]!-'P-"@E$35!!4$527T$T4TU!3$Q\#0H)1$U005!% M4E]!-7P-"@E$35!!4$527T(T? T*"41-4$%015)?0C5\#0H)1$U005!%4E]& M3TQ)3WP-"@E$35!!4$527U%505)43WP-"@E$35!!4$527S$P6#$T? T*"41- M4$%015)?,3%8,3=\#0H)1$U005!%4E].3U1%? T*"41-4$%015)?14Y67SE\ M#0H)1$U005!%4E]%3E9?,3!\#0H)1$U005!%4E]%3E9?,3%\#0H)1$U005!% M4E]%3E9?,3)\#0H)1$U005!%4E]%3E9?,31\#0H)1$U005!%4E]#4TA%151\ M#0H)1$U005!%4E]$4TA%151\#0H)1$U005!%4E]%4TA%151\#0H)1$U005!% M4E]%3E9?1$Q\#0H)1$U005!%4E]%3E9?0S5\#0H)1$U005!%4E]%3E9?0S-\ M#0H)1$U005!%4E]%3E9?0S1\#0H)1$U005!%4E]%3E9?0S9\#0H)1$U005!% M4E]%3E9?0S8U? T*"41-4$%015)?14Y67T(T? T*"41-4$%015)?14Y67T(U M? T*"41-4$%015)?14Y67T(V? T*"41-4$%015)?14Y67TE404Q9? T*"41- M4$%015)?14Y67TU/3D%20TA\#0H)1$U005!%4E]%3E9?4$524T].04Q\#0H) M1$U005!%4E]&04Y&3TQ$7U53? T*"41-4$%015)?1D%.1D],1%]35$1?1T52 M34%.? T*"41-4$%015)?1D%.1D],1%],1TQ?1T5234%.? T*"41-4$%015)? M25-/7T(T? T*"41-4$%015)?2D%004Y%4T5?4$]35$-!4D1\#0H)1$U005!% M4E\Y6#$Q? T*"41-4$%015)?,3!8,3%\#0H)1$U005!%4E\Q-5@Q,7P-"@E$ M35!!4$527T5.5E])3E9)5$5\#0H)1$U005!%4E]215-%4E9%1%\T.'P-"@E$ M35!!4$527U)%4T525D5$7S0Y? T*"41-4$%015)?3$545$527T585%)!? T* M"41-4$%015)?3$5'04Q?15A44D%\#0H)1$U005!%4E]404),3TE$7T585%)! M? T*"41-4$%015)?031?15A44D%\#0H)1$U005!%4E],151415)?5%)!3E-6 M15)317P-"@E$35!!4$527T$T7U1204Y35D524T5\#0H)1$U005!%4E],1514 M15)?15A44D%?5%)!3E-615)317P-"@E$35!!4$527T%?4$Q54WP-"@E$35!! M4$527T)?4$Q54WP-"@E$35!!4$527TQ%5%1%4E]03%53? T*"41-4$%015)? M031?4$Q54WP-"@E$35!!4$527T$U7U1204Y35D524T5\#0H)1$U005!%4E]" M-5]44D%.4U9%4E-%? T*"41-4$%015)?03-?15A44D%\#0H)1$U005!%4E]! M-5]%6%1207P-"@E$35!!4$527T(U7T585%)!? T*"41-4$%015)?03)\#0H) M1$U005!%4E]!,U]44D%.4U9%4E-%? T*"41-4$%015)?03-?15A44D%?5%)! M3E-615)317P-"@E$35!!4$527U5315)\#0H)1$U005!%4E]*05!!3D5315]% M3E9?631\#0H)1$U005!%4E]*05!!3D5315]%3E9?63)\#0H)1$U005!%4E]* M05!!3D5315]%3E9?2S(I)SX-"CPA14Y42519("4@9&UP87!EF5?871T MF5?96YU;3L@(D9!3%-% M(B<^#0H-"CPA14Y42519("4@9&UP7!E("A.3TY% M?$9L87-H?$A$1"D@(DY/3D4B( T*"0D)4W1OF4@3DU43TM%3B B M,"(^#0H)/"$M+2 N+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BTM/@T*"3PA+2T@3U,O2$]3 M5" @0V]L;W(@36%N86=E;65N="]296YD97)I;F<@(" @(" @(" @(" @(" @ M(" @(" @(" @(" M+3X-"@D\(2TM("XN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+2T^#0H) M/"%%3$5-14Y4(%!L871F;W)M("A-;V1U;&5.86UEF%T:6]N(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" M+3X- M"@D\(2TM("XN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+2T^#0H)/"%%3$5-14Y4($QO8V%L M:7IA=&EO;B!%35!462 ^#0H)/"$M+2 N+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BTM/@T* M"3PA+2T@1VQO8F%L(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" M+3X-"@D\(2TM("XN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+2T^#0H@(" @/"%%3$5-14Y4($=L;V)A;" H57-E'0@ M0T1!5$$@(TE-4$Q)140-"B @(" @(" @(" @(%-H;W)T8W5T2V5Y($-$051! M("-)35!,245$/B @#0H@(" @(" @(#PA14Q%345.5"!524-O;G1R;VP@*$)U M='1O;GQ2861I;T)U='1O;D=R;W5P?$-H96-K0F]X?$QI"P@(" @(" @ M(" M+3X-"B @(" @(" @/"$M+2!38W)O;&Q"87(L(%-P:6Y#;VYT2!#1$%402 C24U03$E%1 T*(" @(" @(" @(" @ M(" @($-O;6UA;F0@0T1!5$$@(TE-4$Q)140^#0H@(" @(" @(#PA14Q%345. M5"!#:&5C:T)O>"!%35!463X-"B @(" @(" @/"%%3$5-14Y4($QI4UA;F%G92 -"B @(" @(" @ M(" @(%!R:6YT97)-96UO5]A='1R M:6)U=&5?9&5F875L=#L^#0H@(" @(" @(#PA14Q%345.5"!43TY%4E-!5D53 M("A4;VYE6]U="HI/@T*"0D)/"%!5%1, M25-4($=205E/5513( T*"0D)"69'6]U="!.351/2T5.("(P(CX-"@D)"0D\(45, M14U%3E0@1W)A>6]U=" H(U!#1$%402D^#0H)"0D)/"%!5%1,25-4($=R87EO M=70@#0H)"0D)"4=R87EO=71)9" H4%))3E1%4D1%1D%53%1\5&5X=$=R87!H M:6-\5&5X='Q/9F9\1&5F875L='Q''1);6%G97Q' M6]U=$ED("A.3TY%?$9I='Q3=')E=&-H?%IO;VU\,E50 M?#154'Q4=VEC92D@(DY/3D4B/@T*(" @(" @(" \(2TM("XN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXM+3X-"B @(" @(" @/"$M+2!087!E&5L+%!A<&5R+D%R96$N MF5);F-H,3 P+ T*"0D)"0D)"5!A<&5R+D%R96$N M<'1!&5L($5-4%19(#X-"@D)"0D) M/"%!5%1,25-4(%!A<&5R+D%R96$N<'1!&5L( T*"0D)"0D))7)E8W1?871TF5-;3$P( T*"0D)"0D) M)7!O:6YT7V%T=')I8G5T97,[/@T*"0D)"0D\(45,14U%3E0@4&%P97(N07)E M82YP=%-I>F5);F-H,3 P($5-4%19(#X-"@D)"0D)/"%!5%1,25-4(%!A<&5R M+D%R96$N<'13:7IE26YC:#$P," -"@D)"0D)"25P;VEN=%]A='1R:6)U=&5S M.SX-"@D)"0D)/"%%3$5-14Y4(%!A<&5R+D%R96$N<'1!F5-;3$P+%5$4$EN9F\N7!E($5-4%19/@T* M"0D)"3PA05143$E35"!#;VQL871E5'EP92 -"@D)"0D)0V]L;&%T951Y<&5) M9" H05543WQ*4WQ(87)D=V%R92D@(D%55$\B/@T*"0D)"3PA+2U%3$5-14Y4 M($-O;&QA=&4N36%X3G5M("@C4$-$051!*2TM/@T*"0D)/"%%3$5-14Y4($=R M;W5P($5-4%19/@T*"0D)/"%!5%1,25-4($=R;W5P( T*"0D)"71'$YU;3\I/@T*"0D)/"%!5%1,25-4($UA:6Q";W@@ M#0H)"0D)=$UA:6Q";W@@)7-T871E,U]A='1R:6)U=&5?9&5F875L=#L^#0H) M"0D)/"%%3$5-14Y4($UA:6YL0F]X+DUA>$YU;2 H(U!#1$%402D^#0H)"0D\ M(45,14U%3E0@4W1A<&QE("A3=&%P;&4N36%X3G5M/RQ3=&%P;&4N3$]#051) M3TY3/RD^#0H)"0D\(4%45$Q)4U0@4W1A<&QE( T*"0D)"713=&%P;&4@)7-T M871E,U]A='1R:6)U=&5?9&5F875L=#L^#0H)"0D)/"%%3$5-14Y4(%-T87!L M92Y-87A.=6T@*"-00T1!5$$I/@T*"0D)"3PA14Q%345.5"!3=&%P;&4N3$]# M051)3TY3("A3=&%P;&4N3&]C871I;VXJ*3X-"@D)"0D\(4%45$Q)4U0@4W1A M<&QE+DQ/0T%424].4R -"@D)"0D)4W1A<&QE+DYU;4QO8V%T:6]N($Y-5$]+ M14X@(C B/@T*"0D)"0D\(45,14U%3E0@4W1A<&QE+DQO8V%T:6]N("@C4$-$ M051!*3X-"@D)"0D)/"%!5%1,25-4(%-T87!L92Y,;V-A=&EO;B -"@D)"0D) M"5-T87!L92Y,;V-A=&EO;DED("5S=&%P;&5L;V-A=&EO;E]A='1R:6)U=&5? M9&5F875L=#L^#0H)"0D\(45,14U%3E0@1D],1%,@*$9O;&0J*3X-"@D)"3PA M05143$E35"!&3TQ$4R -"@D)"0ET1F]L9" E$YU;2 H(U!#1$%402D@+2T^#0H)"0D)/"%%3$5- M14Y4($9O;&0@*$9O;&0N5'EP92D^#0H)"0D)"3PA14Q%345.5"!&;VQD+E1Y M<&4@14U05%D^( T*"0D)"0D\(4%45$Q)4U0@1F]L9"Y4>7!E( T*"0D)"0D) M1F]L9%1Y<&5)9" H3D].17Q:1F]L9'Q3861D;&5\1&]U8FQE1V%T97Q,969T M1V%T97Q2:6=H=$=A=&5\3&5T=&5R1F]L9'Q81F]L9"D@(DY/3D4B#0H)"0D) M"0E-87A.=6T)3DU43TM%3B C24U03$E%1#X-"@D)"3PA14Q%345.5"!(;VQE M4'5N8V@@*$AO;&50=6YC:"Y-87A.=6T_*3X-"@D)"3PA05143$E35"!(;VQE M4'5N8V@-"@D)"0ET2&]L95!U;F-H("5S=&%T93-?871T'!A;G-I M;VX@56YI=',@(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @+2T^#0H)(" @(#PA+2T@+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BTM/@T*"0D\(45, M14U%3E0@15A054Y)5%,H15A04D%-4RQ%6%!&3TY40T%21%,L15A01%503$58 M4RQ%6%!005!%4E-/55)#15,L15A04$%015)$15-424Y!5$E/3E,L15A024Y3 M15)415)3+$584%-43U)!1T53*3X-"@D)"3PA14Q%345.5"!%6%!204U3("A% M>'!204TJ*3X-"@D)"3PA05143$E35"!%6%!204U3( T*"0D)"69%>'!204T@ M)6)O;VQ?871T'!204T@3DU43TM% M3B B,"(^( T*"0D)"3PA14Q%345.5"!%>'!204T@*"-00T1!5$$I/@T*"0D) M"3PA05143$E35"!%>'!204T@#0H)"0D)16YT'!&;VYT0V%R9" E M8F]O;%]A='1R:6)U=&5?9F%L'!&;VYT0V%R9"Y&3TY44RD^#0H)"0D)/"%!5%1,25-4($5X<$9O;G1# M87)D( T*"0D)"0E%>'!&;VYT0V%R9$ED($Y-5$]+14X@(TE-4$Q)140^#0H) M"0D)"3PA14Q%345.5"!%>'!&;VYT0V%R9"Y&3TY44R H1F]N="HI/@T*"0D) M"0D\(4%45$Q)4U0@17AP1F]N=$-A'!&;VYT M3G5M($Y-5$]+14X@(TE-4$Q)140^#0H)"0D)"0D\(2TM($5,14U%3E0@1F]N M=" H(U!#1$%402DM+3X-"@D)"0T*"0D)/"%%3$5-14Y4($584$154$Q%6%,@ M*$5X<$1U<&QE>"HI/@T*"0D)/"%!5%1,25-4($584$154$Q%6%,@#0H)"0D) M9D5X<$1U<&QE>" E8F]O;%]A='1R:6)U=&5?9F%L"!.351/2T5.("(P(CX-"@D)"0D\(45,14U%3E0@17AP1'5P;&5X M("A00T1!5$$L4$%015)3*3X-"@D)"0D)/"$M+2 _/S\_/R!&24Y)4TA)3D=3 M("TM/@T*"0D)"0D\(2TM($5,14U%3E0@4$%015)3("A087!E'!087!E'!087!E'!087!E'!087!E'!) M;G-E'!3=&]R M86=E($Y-5$]+14X@(C B/@T*"0D)"3PA+2U%3$5-14Y4(%-T;W)A9V4@*"-0 M0T1!5$$I+2T^#0H-"CPA+2T@+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BX@+2T^#0H\ M(2TM($9!6$-!4"!I$-A<"Y(96%D M97(L1F5A='5R97,I/B -"CPA14Q%345.5"!&87A#87 N2&5A9&5R("A&87@L M3&%N9W5A9V4L36]D=6QE3F%M97,I/@T*"3PA14Q%345.5"!&87@@*"-00T1! M5$$I/@T*/"$M+2 N+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+B M+3X-"CPA+2T@1F%X M($9E871U updated web page Message-ID: Hi All, I've updated the UPDF web page at http://www.pwg.org/updf I also added links to the current DTD and XML file at the bottom of the page. I've decided to move it higher in the page though so it's easier to see. The DTD still dosn't load completely in Visual Basic - but I will work on it later today. Sandra Matts --------------------------------------- Sandra Matts Engineer Scientist Hewlett-Packard sandram@boi.hp.com 208-396-4755 phone Boise, ID 83714 -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 1696 bytes Desc: not available Url : http://www.pwg.org/archives/upd/attachments/19991116/020c0635/winmail.bin From sandram at boi.hp.com Wed Nov 17 14:27:28 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:48 2009 Subject: UPD> UPDF.dtd now works in VB Message-ID: Hi, I've updated the ftp site with a updf.dtd and CLJ4500.xml file that produces NO errors in Visual Basic. Whew! I guess I learned my lesson using XML Pro. There were a bunch of problems in the DTD and XML file. I also deleted some lines from the DTD in the interest of getting it to parse correctly. I do have previous versions of the DTD checked into my source control at work. We can always pull it out later after the UI work is done. Current versions are at : ftp.pwg.org/pub/pwg/upd/updf.dtd ftp.pwg.org/pub/pwg/upd/CLJ4500.xml Sandra Matts Sandra Matts Engineer Scientist Hewlett-Packard sandram@boi.hp.com 208-396-4755 phone Boise, ID 83714 -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 1860 bytes Desc: not available Url : http://www.pwg.org/archives/upd/attachments/19991117/8c65e4c2/winmail.bin From sandram at boi.hp.com Wed Nov 17 14:37:31 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:48 2009 Subject: UPD> XUL uses dtd in non standard way Message-ID: Hi, I've run across a problem trying to use XUL in the MS XML parser. XUL has the XML describing the user interface in a file with the .xul extension. It's pretty standard XML and XML schema code. I think so anyway. They are localizing using !ENTITIES in a dtd file. In reality, XUL is not using the DTD to describe the grammer for the user interface code in the .xul file. The problem is Visual Basic won't parse the .xul file since it is expecting the DTD. If I don't include the DTD in the xul file then of course the parser complains because it can't find the ENTITY defines. The XPFE - cross platform front engine must be a home-grown parser and can handle the DTD inconsistencies. Unless everyone wants to use the XPFE, we can't use XUL directly. I don't want to be forced to use the XPFE, I think the advantage of having a XML based format is to use parsers already out there. If we can't directly use XUL - it looks like we have to leverage. Concerns??? Suggestions??? Sandra Matts Sandra Matts Engineer Scientist Hewlett-Packard sandram@boi.hp.com 208-396-4755 phone Boise, ID 83714 -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 2140 bytes Desc: not available Url : http://www.pwg.org/archives/upd/attachments/19991117/067c83d8/winmail.bin From sandram at boi.hp.com Fri Nov 19 17:41:57 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:48 2009 Subject: UPD> UPDF phone conference Message-ID: Please respond to this email if you want to have a UPDF phone conference this Tuesday. Reply to upd@pwg.org. Due to the low turnout last time, I want to make sure people will participate. Sandra Matts From nschade at xionics.com Mon Nov 22 10:11:34 1999 From: nschade at xionics.com (Norbert Schade) Date: Wed May 6 14:04:48 2009 Subject: Fw: UPD> UPDF phone conference Message-ID: <001801bf34fb$dda9ed80$c31343ce@gca-2.xionics.com> to make it public -----Original Message----- From: Norbert Schade To: Sandra Matts Date: Monday, November 22, 1999 10:09 AM Subject: Re: UPD> UPDF phone conference >Sandra, >I have a chance to spend most of the time of this short week on Mozilla. >So a call next week Tuesday would be more productive for me. > >Just to confirm: >We do not expect any driver to rely on Mozilla being installed for realizing >any UI. We just use that spec to describe our stuff. Correct? > >Concerning the LA conference I get my booking done this Wednesday. >If I don't hear any other schedule, I'll arrive Wednesday evening. So I'd be >available all Thursday, if required. >One day earlier would not be a problem, but I don't want to hang around. >regards >Norbert >-----Original Message----- >From: Sandra Matts >To: Universal Printer Driver >Date: Friday, November 19, 1999 5:43 PM >Subject: UPD> UPDF phone conference > > >>Please respond to this email if you want >>to have a UPDF phone conference this Tuesday. >>Reply to upd@pwg.org. >>Due to the low turnout last time, I want >>to make sure people will participate. >> >>Sandra Matts >> > From sandram at boi.hp.com Mon Nov 22 19:48:00 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:48 2009 Subject: UPD> updf phone conference Message-ID: Hi, Since only two people replied, we won't be having a phone conference on Tuesday. I am still working on creating a proof of concept for LA with style sheets, so I will just keep plugging away. I will send out what I have on Wed. the week before the PWG meeting so that people can look at it. Sandra Matts From sandram at boi.hp.com Tue Nov 23 19:21:51 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:48 2009 Subject: UPD> FW: XPToolkit spec frozen Message-ID: Norbert sent me this message and I wanted the reply to the entire UPDF group. The XPToolkit is not frozen. They are adding widgets but very slowly. Here is a link to a list of widgets supported so far. http://www.mozilla.org/newlayout/doc/widgets.html They list radio buttons, tab, combo box. Almost everything we need. Sandra Matts -----Original Message----- From: Norbert Schade [mailto:nschade@xionics.com] Sent: Tuesday, November 23, 1999 11:23 AM To: Sandra Matts Subject: XPToolkit spec frozen Sandra, what's your information status about XPToolkit? Is it frozen concerning the feature set or are they redesigning it every now and then? I'm surprised not to find some basics described like edit boxes, combo boxes, list boxes and radio buttons at least. If you have a direct contact, could you ask? I'd be very surprised, if they'd leave it out for the first version, as many homepages already work with that. Let's work on a prioritized list of missing widgets: 1. edit boxes, combo boxes, list boxes, radio buttons 2. spin controls, switch groups (can probably be realized by tabs) 3. Preview (page, printer config, etc.) To be extended. We may stay with Mozilla's help options for now. Norbert From jkm at underscore.com Tue Nov 23 19:33:06 1999 From: jkm at underscore.com (Jay Martin) Date: Wed May 6 14:04:48 2009 Subject: UPD> FW: XPToolkit spec frozen References: Message-ID: <383B3242.4CA5EF47@underscore.com> Should we be worried that the page referenced in your message is dated early October 1998 (near the top of the page)? ...jay Sandra Matts wrote: > > Norbert sent me this message and I wanted the reply to > the entire UPDF group. > > The XPToolkit is not frozen. They are adding widgets > but very slowly. Here is a link to a list of widgets > supported so far. > http://www.mozilla.org/newlayout/doc/widgets.html > > They list radio buttons, tab, combo box. Almost > everything we need. > > Sandra Matts > > -----Original Message----- > From: Norbert Schade [mailto:nschade@xionics.com] > Sent: Tuesday, November 23, 1999 11:23 AM > To: Sandra Matts > Subject: XPToolkit spec frozen > > Sandra, > what's your information status about XPToolkit? > Is it frozen concerning the feature set or are they redesigning it every now > and then? > I'm surprised not to find some basics described like edit boxes, combo > boxes, list boxes and radio buttons at least. > If you have a direct contact, could you ask? I'd be very surprised, if > they'd leave it out for the first version, as many homepages already work > with that. > Let's work on a prioritized list of missing widgets: > 1. edit boxes, combo boxes, list boxes, radio buttons > 2. spin controls, switch groups (can probably be realized by tabs) > 3. Preview (page, printer config, etc.) > To be extended. > We may stay with Mozilla's help options for now. > Norbert From sandram at boi.hp.com Tue Nov 23 20:02:25 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:48 2009 Subject: UPD> FW: XPToolkit spec frozen In-Reply-To: <383B3242.4CA5EF47@underscore.com> Message-ID: Yes - it is odd. At the bottom of the page the "real" last modified is Jan 14, 1999. It appears that documentation is behind the implementation. I will download the latest Milestone binary and see how full featured the user interface is. Sandra Matts -----Original Message----- From: Jay Martin [mailto:jkm@underscore.com] Sent: Tuesday, November 23, 1999 5:33 PM To: Sandra Matts Cc: Universal Printer Driver Subject: Re: UPD> FW: XPToolkit spec frozen Should we be worried that the page referenced in your message is dated early October 1998 (near the top of the page)? ...jay Sandra Matts wrote: > > Norbert sent me this message and I wanted the reply to > the entire UPDF group. > > The XPToolkit is not frozen. They are adding widgets > but very slowly. Here is a link to a list of widgets > supported so far. > http://www.mozilla.org/newlayout/doc/widgets.html > > They list radio buttons, tab, combo box. Almost > everything we need. > > Sandra Matts > > From nschade at xionics.com Wed Nov 24 09:43:05 1999 From: nschade at xionics.com (Norbert Schade) Date: Wed May 6 14:04:48 2009 Subject: UPD> widget set Message-ID: <000801bf368a$3855d840$c31343ce@gca-2.xionics.com> All, starting from mozilla.org jump to projects. In the list you see XPToolkit and NewLayout directly followed by each other. I haven't been able to exactly determine the essense and differences between them, but I mainly live in the XPToolkit path these days. You can easily see that these pages are up-to-date. I can't get rid of the feeling that the one (NewLayout) is the plan and the other (XPToolkit) is the real work. The widget set in the XPToolkit path is smaller than the one in the NewLayout/Technical documentation path. Norbert From sandram at boi.hp.com Mon Nov 29 15:25:46 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:48 2009 Subject: UPD> widget set In-Reply-To: <000801bf368a$3855d840$c31343ce@gca-2.xionics.com> Message-ID: I believe the XPToolkit is real work too. I feel it's important to just some list going into our UPDF and then see what we have to add. We may have to periodically follow mozilla and add new widgets when needed. I have a proto started which uses just the basic widgets so far - tab, check box, frame, radio buttons, cmdButtons. I will show it at the next meeting. Things I haven't added to the prototype yet but should be considered are: a UI constraint model, localization strings. Sandra Matts -----Original Message----- From: owner-upd@pwg.org [mailto:owner-upd@pwg.org]On Behalf Of Norbert Schade Sent: Wednesday, November 24, 1999 7:43 AM To: UPD group Subject: UPD> widget set All, starting from mozilla.org jump to projects. In the list you see XPToolkit and NewLayout directly followed by each other. I haven't been able to exactly determine the essense and differences between them, but I mainly live in the XPToolkit path these days. You can easily see that these pages are up-to-date. I can't get rid of the feeling that the one (NewLayout) is the plan and the other (XPToolkit) is the real work. The widget set in the XPToolkit path is smaller than the one in the NewLayout/Technical documentation path. Norbert From nschade at xionics.com Tue Dec 7 17:10:04 1999 From: nschade at xionics.com (Norbert Schade) Date: Wed May 6 14:04:48 2009 Subject: UPD> UPDF constraints Message-ID: <001501bf40ff$d9b32e20$c31343ce@gca-2.xionics.com> All, I have done some research and thinking about constraints and I want to share it at this point. I would appreciate first comments this week to be able to work it over. I haven't concentrated to much on writing good XML so far. I may try that the next days in case we agree about the general direction. I will arrive in LA Wednesday night very late, will have a breakfast late Thursday morning and could talk about constraints further more in detail after that, if people are interested and available. If you have WinWord available you may want to read the attached doc file. I have copied it below. But the tabs are translated badly and the 'rectangles' stand for bullets. Start of WinWord document UI constraints in UPDF I thought about it a while and want to start the discussion to prepare a section in the spec. Up to now I limit myself to contraints in the UI, although we are facing similar problems when printing, too. But this often results in CallBack functions. That?s why I call it ?UI constraints?. Statement 1 (to be discussed): Constraints handle limitations and automatic switches To provide consistent functionality, we do not only handle limitations and exclusions like ?if DialogElement1 is set to Setting1, DialogElement2 cannot show Setting2?, but also automatic switches like ?if DialogElement1 is set to Setting1, DialogElement2 is to be set to Setting2?. I do not think this needs a lot of extra work either, but would ease the understanding of even complex UI behavior. Statement 2 (to be discussed): Installed options are to be identified InstalledOptions must be declared as such so they can be identified for specific functionality. Statement 3 (to be discussed): All interdependencies between driver elements are handled as constraints Only the model itself or InstalledOptions like an Input or Output option can own another driver element. So only the model and any InstalledOption can have lists of paper sources, sizes, media types, duplex modes, etc. This might be a kind of a revolution for some people, but it keeps the printer?s description and later the driver very straightforward. It means that the model owns e.g. paper sources and paper sizes in separate lists, but this part of the UPDF does not tell that certain sources do only support certain sizes. I know that this would require a significant change of the sample XML of M.Yeung. But paper sources and even other driver elements have so many different attributes between different manufacturers nowadays that it would extremely hard to find a generic way to describe these interdependencies within the listings of driver elements. Now while I seriously think about constraints it looks more reasonable to me to provide a separate constraint section and tell there as a constraint that the envelope tray does not feed Letter and many other sizes. Statement 4 (to be discussed): The list of conditional sets combined to a constraint is infinite We want to allow maximum flexibility. With combining two conditional sets to a constraint this is only possible in a limited way. So we could tell that duplex is only available with a certain amount of RAM and depending on certain paper sizes and only from certain paper sources. Simplifying that and ignoring perfect XML syntax at the moment this could result in two constraints like: Constraints Model Constraint Set Condition RAM <= 2MB /Condition /Set Set Condition (PaperWidth x PaperHeight) > 2MB /Condition /Set Set Condition Duplex != Off /Condition /Set /Constraint Constraint Set Condition PaperSource != Manual /Condition /Set Set Condition Duplex != Off /Condition /Set /Constraint /Model /Constraints I?d like to define some rules with this simplified sample: Rule 1: InstalledOptions will not be changed by constraints. So condition 1 of constraint 1 will not result in any change in the UI. This explaines Statement 2. Rule 2: The definition of the constraint defines the order in which it will be resolved. This can be ignored in case of exactly two conditional sets per constraint. In case of more conditional sets it may happen that a certain selection in the UI is activating condition 1 of constraint 1. May be that resolving condition 2 of constraint 1 is already resolving the complete constraint. So condition 3 of constraint 1 can be skipped. That means the order of conditions is Top-Bottom. The top condition is to be resolved first and so on. That allows control about priorities. Rule 3: The order of constraints define their priorities. Not very obvious that we need that rule. But resolving a certain constraint may activate another constraint. Hoping we will never get into an infinite loop, it?s now important, what to do first and next. Defining a global default element or message could help avoid crashing the driver. Rule 4: InstalledOptions have their own constraints. They do not change or extend constraints of the basic models. In case an InstalledOption is going to be merged into a basic UPDF file, the corresponding block of constraints should be added after all other blocks already listed. In the example above no InstalledOption is listed. So I only show the Model section. The string Model is a technical variable, not the UI string (I have seen cases, where models had different names in different locales). This procedure keeps it easier to handle InstalledOptions. Certain constraint blocks can be easily removed without being afraid to break anything. In case there are constraints between different InstalledOptions ? and this is known ? the constraint blocks for both InstalledOptions should list the corresponding constraints. To-do-list ? We have to decide whether we define the good or the bad elements. In my examples I defined the bad combinations in all the constraints. This is causing some problems when trying to define automatic switches. See further below in this document. ? Some syntax issues must be discussed. Up to here that?s the basic part. You may have wondered why I braced the conditions with ?Set?. ? I can well imagine that we realize an OR by simply listing several conditions: Set Condition PaperSource = Tray1 /Condition Condition PaperSource = Tray2 /Condition Condition PaperSource = EnvelopeTray /Condition /Set Set Condition Duplex != Off /Condition /Set ? I can well imagine we want to handle other settings within a set. Samples could be ?Action? and ?Message?. The Action tag ? The action to resolve could be to mark the bad element. This could result in a red cross next to the bad element, e.g. in a combo box. Action Mark = RedCross.JPG ? The action to resolve could be to gray the bad element. This would show the bad element gray, but the others normal black. Action Gray = 75% ? The action to resolve could be to hide the bad element, apparantly the default, in case neither Mark, Gray nor Hide is listed under the Action tag. Action Hide = TRUE ? The action to resolve could be to show an info button to allow the user to activate a detailed message. Action Info = INFO.JPG ? The action to resolve could be to select a certain driver element active. In case Select is not listed under the Action tag, the first element of the driver element list of this UI element will be activated. I can well imagine several Select lines per constraint Set. This would result in a kind of a fallback selection in case the first listed Select line cannot be used because of a certain driver configuration. Action Select = Manual I can well imagine that several lines are combined to define a complex action: Set Condition UIElement1 != DriverElementX /Condition Action Mark = MARK.JPG Action Gray = 75% Action Info = INFO.JPG /Set Set Condition UIElement2 != DriverElementY /Condition Action Info = INFO.JPG Action Select = DriverElementZ1 Action Select = DriverElementZ2 /Set In case the driver provides all required functionality this would be resolved in case UIElement1 is to be changed: DriverElementX would be grayed and marked. An Info button would be visible next to the UI element, even when the combo box is not open. In case UIElement2 is to be changed: DriverElementY would be hidden. The selected driver element would not be the first in the list, but DriverElementZ1 ? if available. Otherwise DriverElementZ2. Info button as above. The Message tag This would only be used in case there is an Action Info line defined. ? We want to activate a certain text. Message Text = Constraint_PaperSource_Duplex ? We may want to activate different levels of message boxes. ? Exit: Just the message and and Exit button. Default. ? Exit_Show: The message, an Exit button and a Show button. Pressing the Show button would should another window with more detailed info. I think of the list of constraints that has been used for the UIElement, where the technical variables would be replaced by the locale specific strings. Although this would still be quite a technical information in a strict syntax it provides a lot of details with generic functionality. Just an idea. ? Exit_Show_Save: As Exit_Show, except that the detailed info can be saved to a file. Might be useful for the support or if somebody wants to manipulate his UPDF file. Message Window = Exit So the latest example could be extended to something like Set Condition UIElement1 != DriverElementX /Condition Action Mark = MARK.JPG Action Gray = 75% Action Info = INFO.JPG Message Text = Constraint_UIElement1_UIElement2 Message Window = Exit_Show /Set Set Condition UIElement2 != DriverElementY /Condition Action Info = INFO.JPG Action Select = DriverElementZ1 Action Select = DriverElementZ2 Message Text = Constraint_UIElement1_UIElement2 Message Window = Exit_Show /Set I think it is realistic to assume the same message text for both sets to save translation effort. Automatic switches This is not much more than an idea up to now. The general problem to realize something like ?if this is selected here, something else should happen there? is very similar to constraints in the basic sense. So I wonder whether we can use this or a very similar kind of syntax not only for the negative combinations (this and that cannot be combined), but also for activating certain selections depending on others. I will keep an eye on that. End of WinWord Document -------------- next part -------------- A non-text attachment was scrubbed... Name: UI constraints in UPDF.doc Type: application/msword Size: 35328 bytes Desc: not available Url : http://www.pwg.org/archives/upd/attachments/19991207/c21332d1/UIconstraintsinUPDF.doc From nschade at xionics.com Tue Dec 28 10:57:58 1999 From: nschade at xionics.com (Norbert Schade) Date: Wed May 6 14:04:48 2009 Subject: UPD> constraints Message-ID: <000301bf514c$503b6f60$c31343ce@gca-2.xionics.com> the more I think about it the more I am sure about that statement: There is no OR in XML. Everything is interpreted as AND. So the only solution for something like "if paper size is Letter OR A4 then ..." is to build two separate constraints. Feedback please. Norbert From sandram at boi.hp.com Tue Jan 12 18:12:15 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> subgroups Message-ID: <01BE3E46.529B60E0@hpb13858.boi.hp.com> Hi All, At the last meeting we spoke about defining subgroups to concentrate on the investigation / definition of the UPDF. Some obvious groups are User Interface and localization; Fonts; Rendering; dynamic configuration and transport of UPDF across networks. Any other suggestion? Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Tue Jan 12 18:16:13 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> agenda for Monday Message-ID: <01BE3E46.E0C089E0@hpb13858.boi.hp.com> Here's a prelim agenda for Monday's meeting in Hawaii. Please send me suggestions for more items to discuss. Also if people know anything about XML and want to share - that would be great. 8:30 - 9:00am Intros and misc. 9:00 - 10:00am Requirements 10:00 - 11:30am Apple presentation 11:30 - 1:00pm Lunch 1:00 - 1:30pm subgroups 1:30 - 2:00pm use cases 2:00 - 3:30pm XML stuff ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Wed Jan 13 13:59:13 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> minutes and misc posted to ftp site Message-ID: <01BE3EEC.2428A500@hpb13858.boi.hp.com> Hi, I've posted minutes from the last meeting to the ftp site. I also posted Adobe's Job Ticket spec to Archive/Specs and pdf versions of the presentations to Archive/1998. I'm still working on converting Bill Wyman's Job ticket presentation to pdf format. I am also working on the UPDG web page and I should post a current word format of the requirements doc tomorrow. Did I forget anything? If you are expecting more - let me know what you would like posted. thanks, Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From nschade at xionics.com Thu Jan 14 11:59:14 1999 From: nschade at xionics.com (NSchade) Date: Wed May 6 14:05:04 2009 Subject: UPD> subgroup proposals Message-ID: <001201be3fdf$3749e880$1c1343ce@nschade.xionics.com> Hi all, I worked on collecting some stuff the last weeks. So I'd like to make a proposal for subgroups, which is filled with some life already. There are some basic topics, which are listed below: 1. I distinguish between some levels of work. This affects the rights of subgroups, too. I do not think that the complete plenum wants to decide on each and every byte of the format. The levels are Conceptional work, Architectural work, Structural work, Functional work. 1.1. Conceptional work Discussed and decided in the plenum. Some topics are Unicode for UI and printing, definition of all numeric values in virtual units and a sophisticated parameter converter used within command sequences. 1.2. Architectural work Discussed and decided in the plenum. Some topics are to think as modular as possible, global filter functionality including constraints and error messages, global identifyers for ALL modules. The use of global identifyers is very obvious in paper size handling. There should be a number of predefined identifyers for all device descriptions (Letter=1, A4=2, etc.), a reversed area or proprietary definitions used company wide by printer manufacturers and a reserved area for user defined defintions. This architecture is useful for all modules. We will also discuss the overall architecture to be able to define mandatory modules and a proper way to include proprietary modules in this open structure. 1.3. Structural work Decided in the plenum. Discussed in the subgroups. Mandatory modules and predefined values are developed here. 1.4. Functional work Discussed and decided in the subgroups. In order to function correctly some assumptions must be made. The details should be work out in the subgroups with the detailed understanding. 2. Some assumptions have to be made. 2.1. Driver assumptions Although the driver is out of scope we have to consider how it will work. Otherwise our description is useless. Some topics are support of vector graphics, support of overlays/watermarks and the way the spooler works. The driver may maintain three sets of features (Device properties, Application defaults, Job settings). 2.2. Tooling assumptions For all the boring and time consuming repeating stuff we should think about tools and their development. I really would like to see a driver, which allows easy translation. We may seriously recommend functionality to switch the driver to a translation mode (perhaps with an additional library) to allow editing in the dialog. We may think about short cut handling. 2.3. Operating system assumtions The OS may offer some global strings like for paper sizes in various languages or pictures like for duplex modes. We have to clearly find out what we can expect concerning dialog handling. We have to know how to detect character sets info. The OS may offer lists for composed characters. The OS may offer a list of paper sizes concerning dimensions. 3. We have to decide in detail what is Out of scope at least for version 1 of the format. Some topics may be Workload balance, Application workarounds, Paper preview, Printer preview, Subdialogs. We may extend the list during development. Based on that we may define some subgroups. I'd like to see Global decisions, User interface and Localization, Paper handling, Fonts, Color, Configuration and Communication. 1. Global decisions This is a quite big group. We may split it. Some topics may be the General model description (somehow a tree), Global flags (like the exact printer language level), Optional units (input, output, duplex, RAM, ROM font cartriges, Flash ROM, Hard disks and all kinds of combinations), Positioning, Raster graphics (rendering), Memory, Overlays/Watermarks, Driver sets (Global sets, Job settings, MasterPages), Print file structure (Job Start/End, Page Start/End, Download, Overlays/Watermarks). 2. User interface and Localization Some topics are AVD (automatic version detection), Human languages, Icons/Pictures, Defaults (ranking including fallback mechanisms), UI structure, UI element description (minimum for global, extended for proprietary), String length limitations (you cannot show a paper size with 50 characters, OS specific), Short cuts, Balloon help. 3. Paper handling Some topics may be Size, Minimum margins, Orientation (these three build the minimum set of the seven values), N-up/Booklet, Logical/Physical zooming, Input, MediaType, Output, Copies including Collation. 4. Color Including halftoning. Not yet elaborated. 5. Configuration and Communication Some topics are Networking, Bidirectional communication, Model timings, PnP ID, Check sum for high speed bidi. Not yet elaborated. As you can easily see I want to come to something we can hold in our hands as soon as possible and let the spec grow during development. Regards Norbert From sandram at boi.hp.com Fri Jan 29 15:23:06 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: No subject Message-ID: <01BE4B8A.82347AC0@hpb13858.boi.hp.com> Hi All, At the last UPDF meetings we decided to have a bi-weekly phone conference to discuss the subgroups. The phone number for our phone conference is 612-315-6802 The access code is 058459494 I will activate the number on Feb 2 from 10-12 Pacific time. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From nschade at xionics.com Mon Feb 1 09:34:11 1999 From: nschade at xionics.com (NSchade) Date: Wed May 6 14:05:04 2009 Subject: UPD> draft samples for UPDF sections Message-ID: <001001be4def$ef7fb880$1c1343ce@nschade.xionics.com> All, I feel we should work on something real when discussing the UPDF spec, the sections we implement, other printer descriptions used as a base and the defintion of subgroups. I hope the attached four ASCII files (Windows International char set) are helpful showing the differences we have to deal with and ways to go. These are two descriptions (Paper source and Power save), each provided one general and once filled with parameters. I did not care about syntax. I did not care about a real structure. I did not care about completeness or perfect correctness. My major concern was to start a discussion about an open structure (you can add proprietary sections and/or delete optional sections without injuring the format). Some details are that the short cuts are not included in the string (like an ampercent) to ease translations or to rank elements of a module per language to provide an easy fallback mechanism for defaults. Xionics will be participating with some people in tomorrow's teleconference. We may refer to these documents. If I am not clear enough in some areas, please ask me directly for further explanations. Regards Norbert -------------- next part -------------- Legend ModuleClassifications M_ // mandatory, predefined by UPDF // must be supported O_ // optional, predefined by UPDF // can be supported P_ // optional, proprietary, defined by manufacturer // can be supported ParameterClassifications G_ // global, predefined by UPDF // the first 500 reserved P_ // proprietary, defined by manufacturer // the second 500 reserved U_ // user defined // the third 500 reserved This module is called ID_PaperSource with all the available input trays as elements. Some descriptions are general for the module. Later you see those descriptions specific to each element of the module. The general descriptions of this module are: M_Basics O_Comment M_PrinterConnector O_OwnsElements O_ElementsPaperSource M_Dialog M_Style M_Attributes M_Margins M_Left M_Right M_Top M_Bottom M_StoreData M_MemberOfSet M_MemberOfGroup M_RelatedToElement M_Position // relative to M_RelatedToElement M_Horizontal M_Vertical M_ElementTitle M_Style M_Margins M_Left M_Right M_Top M_Bottom M_Attributes M_Position M_Horizontal M_Vertical M_Language // per Language O_BalloonHelp // per Language O_Help O_CheckRelatedElementSizes O_Preview O_ElementImage FunctionCall M_Functions Init CallBack1 O_Communication O_Errors O_Event O_Message // per Language O_Config O_JobStatus These are the element specific descriptions: O_ElementsPaperSource M_ElementBasics O_ElementComment // per Element M_TechnicalElementID // per Element M_ValueLimitations M_MinimumWidth // per Element unit: mm/10 M_MaximumWidth // per Element unit: mm/10 M_MinimumLength // per Element unit: mm/10 M_MaximumLength // per Element unit: mm/10 O_LeftOffset // per Element unit: mm/10 O_RightOffset // per Element unit: mm/10 M_Ranking // per Language M_ElementLanguage // per Element per Language O_Preview O_PaperPathPreview FunctionCall sample parameters: FeedingAngle FrontPage O_PrinterConfigPreview FunctionCall sample parameters: ImageSelected ImageDeselected M_Print O_SequenceJobHeader O_Ranking O_Redundancy O_SequenceJobTrailer O_Ranking O_Redundancy O_SequenceJobStart // after JobHeader O_Ranking O_Redundancy O_SequenceJobEnd // before JobEnd O_Ranking O_Redundancy O_SequencePageStart O_Ranking O_Redundancy O_SequencePageEnd O_Ranking O_Redundancy O_Filters O_ActiveFilters sample parameters: FeedingAngle, ID_PaperSize, ID_HWMargins // combined filter O_Condition O_Message // per Language ID_PrintMedia O_Condition O_Message // per Language ID_Duplex O_Condition O_Message // per Language O_PassiveFilters sample parameters: ID_InputOptions O_Message O_Communication O_Errors O_Event O_Message // per Language O_Config -------------- next part -------------- ID_PaperSource Sample for 2 human languages (US English, German), 2 elements (Tray 1, Manual) M_Basics O_Comment Paper sources of model Sirius M_PrinterConnector Connected to the lower connector, the same connector is provided at its bottom for other paper sources O_OwnsElements O_ElementsPaperSource M_Dialog M_Style Combo box with max 5 entries at a time M_Attributes Change to static text control, if 1 entry M_Margins // around the combo box M_Left 5 pixel M_Right 5 pixel M_Top 5 pixel M_Bottom 5 pixel M_StoreData dmDefaultSource M_MemberOfSet QuickSets M_MemberOfGroup TabGroup_Paper M_RelatedToElement ID_PaperSize M_Position M_Horizontal Same M_Vertical Down O_CheckRelatedElementSizes ID_PaperSize M_ElementTitle M_Style StaticText M_Margins // around the text prompt M_Left 5 pixel M_Right 5 pixel M_Top 5 pixel M_Bottom 5 pixel M_Attributes Short cut M_Position M_Horizontal Left M_Vertical Same M_Language US English: Paper Source (7), German: Papierschacht (7) // the bracket shows the short cut position within the string O_BalloonHelp US English: Select a paper source. German: Waehlen Sie einen Schacht aus. O_Help HLP_PaperSource // entry point for the help fle O_CheckRelatedElementSizes ID_PaperSize /* This dialog section says that paper source is to be shown within the Paper tab below the paper size control, not smaller than the paper size control. Paper source is to be provided as a combo box with the prompt left to it, no small picture next to the control. A margin of 5 pixel shall be used around the combo box as well as around the text. */ M_Functions Init use standard initialization O_ElementsPaperSource M_ElementBasics O_ElementComment Tray 1 of Sirius M_TechnicalElementID Input1 // predefined M_ValueLimitations M_MinimumWidth 1000 unit: mm/10 M_MaximumWidth 2159 unit: mm/10 M_MinimumLength 1000 unit: mm/10 M_MaximumLength 3556 unit: mm/10 M_Ranking US English: 1 German: 2 M_ElementLanguage US English: Tray 1 German: Schacht 1 O_Preview O_PaperPathPreview FunctionCall sample parameters: FeedingAngle the feeding angle for the selected paper size FrontPage Face down O_PrinterConfigPreview FunctionCall sample parameters: ImageSelected BMP_Highlight_Tray1 ImageDeselected BMP_Tray1 M_Print O_SequencePageStart esc & l 1 H O_Ranking as second command sequence at page start O_Redundancy only to be sent, if different O_SequencePageEnd FormFeed O_Ranking as first command sequence at page end O_Redundancy Sent always O_Filters O_ActiveFilters FeedingAngle, ID_PaperSize, ID_HWMargins List O_Condition Short-edge, Letter, each min margin = 75 Short-edge, A4, each min margin = 71 O_PassiveFilters // passive filters are acceleration fields ID_InputOptions List // automatically filled by definition of active filters //of ID_InputOptions M_ElementBasics O_ElementComment Manual Tray of Sirius M_TechnicalElementID Manual // predefined M_ValueLimitations M_MinimumWidth 1000 unit: mm/10 M_MaximumWidth 2970 unit: mm/10 M_MinimumLength 1000 unit: mm/10 M_MaximumLength 4200 unit: mm/10 M_Ranking US English: 2 German: 1 M_ElementLanguage US English: Manual German: Manuell O_Preview O_PaperPathPreview FunctionCall sample parameters: FeedingAngle the feeding angle for the selected paper size FrontPage Face down O_PrinterConfigPreview FunctionCall sample parameters: ImageSelected BMP_Highlight_Manual ImageDeselected BMP_Manual M_Print O_SequencePageStart esc & l 2 H O_Ranking as second command sequence at page start O_Redundancy only to be sent, if different O_SequencePageEnd FormFeed O_Ranking as first command sequence at page end O_Redundancy Sent always O_Filters O_ActiveFilters FeedingAngle, ID_PaperSize, ID_HWMargins List O_Condition Long-edge, Letter, each min margin = 75 Long-edge, A4, each min margin = 71 Short-edge, A3, each margin = 71 O_PassiveFilters // passive filters are acceleration fields ID_InputOptions List // automatically filled by definition of active filters //of ID_InputOptions -------------- next part -------------- Legend ModuleClassifications M_ // mandatory, predefined by UPDF // must be supported O_ // optional, predefined by UPDF // can be supported P_ // optional, proprietary, defined by manufacturer // can be supported ParameterClassifications G_ // global, predefined by UPDF // the first 500 reserved P_ // proprietary, defined by manufacturer // the second 500 reserved U_ // user defined // the third 500 reserved This module is called ID_PowerSave just with 2 settings as elements. Some descriptions are general for the module. Later you see those descriptions specific to each element of the module. The general descriptions of this module are: M_Basics O_Comment O_OwnsElements O_ElementsPowerSave M_Dialog M_Style M_Attributes M_Margins M_Left M_Right M_Top M_Bottom M_StoreData M_MemberOfSet M_MemberOfGroup M_RelatedToElement M_Position // relative to M_RelatedToElement M_Horizontal M_Vertical M_ElementTitle M_Style M_Margins M_Left M_Right M_Top M_Bottom M_Attributes M_Position M_Horizontal M_Vertical M_Language // per Language O_BalloonHelp // per Language O_Help O_CheckRelatedElementSizes O_Preview O_ElementImage FunctionCall M_Functions Init CallBack1 O_Communication O_Errors O_Event O_Message // per Language O_Config O_JobStatus These are the element specific descriptions: O_ElementsPowerSave M_ElementBasics O_ElementComment // per Element M_TechnicalElementID // per Element M_Ranking // per Language M_ElementLanguage // per Element per Language M_Print O_SequenceJobHeader O_Ranking O_Redundancy O_SequenceJobTrailer O_Ranking O_Redundancy O_Filters O_ActiveFilters O_PassiveFilters sample parameters: ID_Model O_Message O_Communication O_Errors O_Event O_Message // per Language O_Config -------------- next part -------------- ID_PowerSave Sample for 2 human languages (US English, German), 2 elements (On, Off) M_Basics O_Comment Power save modes of model Sirius O_OwnsElements O_ElementsPowerSave M_Dialog M_Style Combo box with max 2 entries at a time M_Attributes Change to static text control, if 1 entry M_Margins // around the combo box M_Left 5 pixel M_Right 5 pixel M_Top 5 pixel M_Bottom 5 pixel M_StoreData XDMPowerSave M_MemberOfSet QuickSets M_MemberOfGroup TabGroup_PermanentSettings M_RelatedToElement zero // This is the first element in the group M_Position M_Horizontal Left M_Vertical Top O_CheckRelatedElementSizes zero // ignore all other controls in this dialog for the size // of this control M_ElementTitle M_Style StaticText M_Margins // around the text prompt M_Left 5 pixel M_Right 5 pixel M_Top 5 pixel M_Bottom 5 pixel M_Attributes Short cut M_Position M_Horizontal Left M_Vertical Same M_Language US English: Power Save (1), German: Sparmodus (2) // the bracket shows the short cut position within the string O_BalloonHelp US English: Select the power save mode. German: Waehlen Sie den Sparmodus. O_Help HLP_PowerSave // entry point for the help fle O_CheckRelatedElementSizes zero O_Preview O_ElementImage BMP_PLUG FunctionCall /* This dialog section says that power save is to be shown within the Permanent settings tab at the upper left corner. Power save is to be provided as a combo box with the prompt left to it, a small picture of a plug next to the control. A margin of 5 pixel shall be used around the combo box as well as around the text. */ M_Functions Init use standard initialization O_ElementsPowerSave M_ElementBasics O_ElementComment Power save on M_TechnicalElementID ON // predefined M_Ranking US English: 1 German: 2 M_ElementLanguage US English: On German: An M_Print O_SequenceJobHeader @PJL SET POWERSAVE=ON O_Ranking as third command sequence in job header O_Redundancy sent always O_Filters O_PassiveFilters // passive filters are acceleration fields ID_Model List // automatically filled by definition of active filters //of ID_Model M_ElementBasics O_ElementComment Power save off M_TechnicalElementID OFF // predefined M_Ranking US English: 1 German: 2 M_ElementLanguage US English: Off German: Aus M_Print O_SequenceJobHeader @PJL SET POWERSAVE=OFF O_Ranking as third command sequence in job header O_Redundancy sent always O_Filters O_PassiveFilters // passive filters are acceleration fields ID_InputOptions List // automatically filled by definition of active filters //of ID_InputOptions From nschade at xionics.com Mon Feb 8 05:12:18 1999 From: nschade at xionics.com (NSchade) Date: Wed May 6 14:05:04 2009 Subject: UPD> conclusion of last teleconference Message-ID: <001701be534b$826ebaa0$1c1343ce@nschade.xionics.com> All, I'd like to put some info together to remember the discussion and probably make some decisions. Statements to be decided: 1. Virtual units Every UPDF has a basic field ID_M_VirtualUnit. Sample parameter: 7200. Conceptional idea: The universal driver will work with this virtual unit for most of the variable parameters for print output without further caring for resolutions in the UPDF. Sample 1: Horizontal positioning Target: To be able to define formulas, which generally tell about the specific unit to calculate in. The formulas will be handled by a driver routine called ParameterConverter (quite simple routine). Sample formula for horizontal positioning (final syntax to be agreed on): esc * p formula(ID_M_HorizontalPosition * ID_M_DeviceResolution / ID_M_VirtualUnit) X Rounding and truncating to be discussed. Print output: correct positioning command sequence for the current device resolution in consistent units overall the complete driver. Can be reused for future models, which may even work in higher device resolutions. Sample 2: Specification of width values for bitmap fonts Sampe char: "A" Assumption: the width of "A" is 20 pixel in 300 dpi Specified value in UPDF: 480 (comment: 7200 / 300 = 24). Advantage: 480 virtual units are valid for each device resolution (300 dpi, 600 dpi, even future resoutions). Conclusion: This would unify a lot of parameter specifications. A universal driver can nearly always think in virtual units. The implementation of future models with higher resolutions saves a tremendous time. If the parameter spec is correct once, it must be correct for other future device resolutions working with the same virtual unit. This will dramatically decrease test and maintenance effort. 2. ID-classification Sample ID's: ID_M_VirtualUnits, ID_M_HorizontalPosition, ID_M_PaperSource, ID_M_PaperSize, ID_O_PrintMedia, ID_P_HolePunching Legend: M_ Mandatory. This ID is necessary to establish a correctly working universal driver. The list will be defined by UPDF. O_ Optional. This ID is not necessary to establish a correctly working universal driver. One universal driver on one operating system may support it, another driver on another operating system may not yet support it. The ID may not be supported by any universal driver yet. But it will make driver extensions more reliable. It will encourage universal driver developers to support more optional ID's. The list will be defined by UPDF. It may grow from time to time. Optional ID's may be supported by one, some or all universal drivers. P_ Proprietary. This ID may only be supported by proprietary drivers, probably developed by a printer manufacturer while implementing the rules of UPDF. This will be defined by e.g. a peripheral manufacturer. A universal driver may support this control without knowing what it means, if it is a simple toggle or something similar. Conclusion: This is not really changing the way a universal driver will work, but it makes it easier to write a UPDF looking at some lists. Xionics' requirement: UPDF must be an open standard to allow proprietary solutions while following the standard rules of UPDF. We do not assume that the universal driver provided by every operating system fulfilles all necessities of Xionics from beginning on. We think this will heavily improve the acceptance of UPDF. 3. Parameter classification Sample ID: ID_M_PaperSize Sample parameters: Parm_G_Letter, Parm_G_A4, Parm_O_A5, Parm_P_CompanyXYZFormat1, Parm_U_UserDefined1 Legend: G_ Global. This parameter will be detected by every universal printer driver. A side effect may be that the UI strings for those parameters may be provided by the operating system to ensure consistent UI strings throughout all drivers. A side effect may be that values for paper width and length may be provided by the operating system to ensure consistent values thtoughout all drivers. The list will be defined by UPDF. We will define a range big enough for future extensions. O_ Optional. This list will be defined by UPDF. It is not ensured that a paper size with an optional parameter will be supported by an operating system global UI string or global values. We will define a range big enough for future extensions. If an optional parameter proves its worldwide use over the times, it will be the target to move more of these to the global list, until the global list is somehow complete. P_ Proprieatary. This parameter may be defined by e.g. a printer manufacturer. It is not ensured that a document saved with a proprietary parameter for paper size will be detected later by another UPDF, although the other one may support the same physical paper size, but with a different parameter. Proprietary parameters may move to the optional list after having proven its reliability and necessity. UPDF will define a range for this list, but not the list itself. U_ User defined. This list is not predefined at all. UPDF will define a range for this list. These are reserved parameters for paper sizes defined by the end user, if a certain paper source allows that. Conclusion: I can imagine numeric values or alphanumeric values. 4. Tree structure of UPDF One UPDF will define one model. The UPDF is somehow a tree. I can well imagine several hierarchic levels (e.g Fonts may be listed on level 1, while the font attributes, which assemble a font, will be listed on level 2). The universal driver will detect ID's by its name and may jump over ID's, which definition it cannot completely support. This is the concept of an open format. It allows to add branches to the tree without injuring correct functionality of other branches. 5. Unique and central definition per module All specification is only done once. A module like a paper source ID is specified in one block with all components. 5.1. A module may have a basic component. 5.2. A module may have a dialog component. 5.3. A module may have a print component. 5.4. Function call backs like initialization or specific functionality may be a separate component or to be handled within the other components. 5.5. Other components to be discussed. Samples: ID_M_PaperSource and ID_M_PaperSize are typical modules for 5.1. (owns a list of paper sources), 5.2. (is represented in the dialog) and 5.3. (some bytes have to be sent to the device). A general printer language init (esc E) is a typical module for 5.3., but not necessarily for 5.1. and normally not for 5.2. A group box is a typical module for 5.2., but not necessarily for 5.1. and definitely not for 5.3. 6. Default driver settings A standard problem of multilingual drivers provided for different derivates of operating systems (International, East European, Arabic, Japanese, etc.) is the default setting. Standard problems to be solved for a universal driver are that not all parameters are supported by some operating systems (e.g. Graphic modes like Raster and GL/2 in PCL5e). As we do not want to specify operating system specific defaults, we need a kind of a fallback, which allows the definition of priorities. Countries may require different defaults (e.g. Letter size for US, A4 for Europe). A fallback mechanism may even help in this case. A ranking has to be defined per country/language, which allow the global default specification for each module per each country/language, even if some elements may not be available under certain operating systems or certain configurations. We may think about grouping countries/languages to bigger groups like Europe to avoid to many listings. Feedback appreciated. Sandra, as these items are basic conceptional decisions, they must be clear right from beginning. Perhaps we can agree on that in Miami. Regards Norbert From sandram at boi.hp.com Wed Feb 24 15:00:47 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> minutes Message-ID: <01BE5FF5.B31E82A0@hpb13858.boi.hp.com> Hi All, I've copied the minutes from the last meeting to the web page and archive. I've also copied electronic versions of the presentations. They are at www.pwg.org/updf/index.html Let me know if you want anything else copied. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Wed Feb 24 15:11:06 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> subgroups for UPDF Message-ID: <01BE5FF7.23AF3B80@hpb13858.boi.hp.com> Hi All, I'm assuming we still want to create subgroups for UPDF Spec definition. I would like to elicit feedback on how to proceed. The following subgroups are defined: 1. Global 2. Font handling 3. Paper handling 4. Color handling 5. Localization 6. Communication 7. User Interface 8. Callback mechanism 9. Device capabilities 10. PDL It seems to me first we should all work on the Global and decide what goes into the Global and also set the rules (ie syntax req., guidelines, and so on) for the subgroups. We should spend some time in Miami to hammer this out. When exactly do the subgroups meet? I prefer Wed and Thur. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From mattsf3 at ix.netcom.com Fri Feb 26 13:02:42 1999 From: mattsf3 at ix.netcom.com (mattsf3@ix.netcom.com) Date: Wed May 6 14:05:04 2009 Subject: UPD> Warning! meeting charges Message-ID: <199922610461641@ix.netcom.com> Hi All, I was just informed by the marriott that they will not accept individual credit cards. I am paying for the meeting on my AmEx. People will have to pay Brian Batchelder on Monday, Tuesday, and Wednesday by check or cash. On Thursday and Friday, I will be there so you can pay me. If you write a check, please make it out to "Sandra Matts" The meeting charges are $38 / day. Sorry for the inconvenience. If you don't have checks or cannot get enough cash, give me or Brian Batchelder your name and company and you can pay me later in the month. Sandra Matts From sandram at boi.hp.com Tue Mar 2 10:32:14 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> phone conference Message-ID: <01BE6487.2D805420@hpb13858.boi.hp.com> Hi, I've received questions on whether there is a call today or not. I believe there is no call scheduled during the PWG week. I will send out emails before the next one. Here's March's schedule: March 9 and 23rd Pacific time 10-12 (Tuesdays) Phone number is: 612-315-6802 Access code is: 687920064 Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Wed Mar 10 12:15:53 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> phone conf Tuesday 3-16 Message-ID: <01BE6ADE.FB9E6BA0@hpb13858.boi.hp.com> Hi All, At the last meeting the UPDF group decided to have the phone call Tues 3-16 instead of 3-9. I apologize for the last minute notice - my son has been sick and this is my first day at work. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From sandram at hpbs1061.boi.hp.com Wed Mar 10 13:51:07 1999 From: sandram at hpbs1061.boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> phone conference Message-ID: <9903101851.AA00644@hpbs1061.boi.hp.com> Hi, It was decided at the last UPDF meeting to have the phone call on Tues. 3-16 10-12 pacific. Sandra Matts From sandram at hpbs1061.boi.hp.com Wed Mar 10 18:05:55 1999 From: sandram at hpbs1061.boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> my email address Message-ID: <9903102305.AA01367@hpbs1061.boi.hp.com> Hi, For some reason my current email address is not functioning so I have not received any email for the last three days. If you have sent me any email please resend to sandram@hpbs1061.boi.hp.com. I will let you know when my real email (sandram@boi.hp.com) is working. thanks, Sandra Matts From sandram at hpbs1061.boi.hp.com Wed Mar 10 18:29:47 1999 From: sandram at hpbs1061.boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> UPDF spec Message-ID: <9903102329.AA01436@hpbs1061.boi.hp.com> Hi, I've copied the UPDF Spec version 0.4 to ftp://ftp.pwg.org/pub/pwg/upd/Archive/Specs. There are several files: UPDF Functional Specification.doc Updf.dtd cmfp.xml Sandra Matts From Michael_Yeung at cissc.canon.com Wed Mar 10 18:38:51 1999 From: Michael_Yeung at cissc.canon.com (Yeung, Michael) Date: Wed May 6 14:05:04 2009 Subject: UPD> XML Editors Message-ID: > URL Links for XML editor > > > "XML 1.2 - Demo Version" > Vervet Logic > http://www.vervet.com/ > go! XML Pro Demo Download > > "XML NotePad > Microsoft > http://www.microsoft.com/workshop/c-frame.htm#/xml/default.asp > go! Genaeral Information - XML NotePad > > > > Mike > From sandram at boi.hp.com Thu Mar 11 11:27:10 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: FW: UPD> my email address Message-ID: <01BE6BA1.57B46760@hpb13858.boi.hp.com> Hi, My original email address is now working. You can send email to sandram@boi.hp.com and I will get it. Sandra Matts -----Original Message----- From: Sandra Matts [SMTP:sandram@hpbs1061.boi.hp.com] Sent: Wednesday, March 10, 1999 4:06 PM To: upd@pwg.org Subject: UPD> my email address Hi, For some reason my current email address is not functioning so I have not received any email for the last three days. If you have sent me any email please resend to sandram@hpbs1061.boi.hp.com. I will let you know when my real email (sandram@boi.hp.com) is working. thanks, Sandra Matts From sandram at boi.hp.com Thu Mar 11 16:13:29 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> fixed link to UPDF spec Message-ID: <01BE6BC9.574FD200@hpb13858.boi.hp.com> Hi, The link is slightly incorrect for the UPDFspec. Try this: ftp://ftp.pwg.org/pub/pwg/upd/Archive/Specs/ Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Thu Mar 11 17:47:46 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> minutes from Miami meeting Message-ID: <01BE6BD6.82D93940@hpb13858.boi.hp.com> Hi, I posted minutes from the Miami meeting on the web page at http://www.pwg.org/updf/ ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Mon Mar 15 11:24:44 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> Tues phone conference Message-ID: <01BE6EC5.A9FA04E0@hpb13858.boi.hp.com> Hi All, UPDF will have a phone conference on Tuesday 10-12 Pacific time. Phone number is: (612) 315-6802 Access code is: 058459494 Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Tue Mar 16 10:43:32 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> agenda for phone conf today Message-ID: <01BE6F89.133E3840@hpb13858.boi.hp.com> Hi, Here's the items I would like to discuss. People are always welcome to add items they want to discuss during the phone conference. Mac OS and Linux support. Discuss the subgroup work slated for New Orleans. UPDF specification. Is there anything in the header to be added or is it complete as is? Furthur comments on UPDF spec. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Tue Mar 23 12:46:19 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> break out rooms for Philly Message-ID: <01BE751A.637712A0@hpb13858.boi.hp.com> Hi All, I'm setting up the additional meeting room for the UPDF UI and Imaging meetings. Unlike the New Orleans hotel, we will have to pay $275 / day for the room. I would like people to ping me if they will be attending so that I can calculate about how much to charge everyone. Also do people want breakfast included with the room at an additional charge or do you prefer breakfast on your own. Its about 15.00 / person for breakfast. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Thu Mar 25 13:01:39 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> break out room for Philly Message-ID: <01BE76AE.DC105EC0@hpb13858.boi.hp.com> Hi, A couple of days ago I sent out a message concerning break out rooms for the UI and Imaging meetings for UPD. So far no one has responded that they will attend. I'm in the process of signing the contract for the rooms and I need to know if people are going to the UI and Imaging meeting. The extra room costs $275 /day or total is $550. The cost will be divided amoungst the attendees. If ten people attend that's 27.50 per day. This is less than the main meeting. Can people please let me know if they will attend. Marriott would like the contract back today. Remember - Wed after Plenery is UI and Thursday is Imaging Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Mon Mar 29 16:39:07 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> phone conf or not Message-ID: <01BE79F1.E7175DA0@hpb13858.boi.hp.com> Hi, Tomorrow the UPDF group has a phone conference scheduled. There hasn't been much activity since the last phone conference. Unless people feel a real strong need to have the conf. I propose that we do not have a phone conference and just meet in New Orleans on Wed for the User Interface portion of the UPDF meeting. Reply with your thoughts. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From charles.a.adams at exgate.tek.com Mon Mar 29 17:15:21 1999 From: charles.a.adams at exgate.tek.com (charles.a.adams@exgate.tek.com) Date: Wed May 6 14:05:04 2009 Subject: UPD> phone conf or not Message-ID: <6B57A2A3212BD2119C2600805F6F141301A33D64@us-wv-m11.wv.tek.com> I am also guilty. I have had little time to work on UPDF. But at the same time I am not going to make the meeting in New Orleans. Is there a chance of getting something together for a conference call next week? Chuck Adams Tektronix, Inc. > -----Original Message----- > From: Sandra Matts [SMTP:sandram@boi.hp.COM] > Sent: Monday, March 29, 1999 1:39 PM > To: Universal Printer Driver (E-mail) > Subject: UPD> phone conf or not > > Hi, > Tomorrow the UPDF group has a phone conference scheduled. There > hasn't been much activity since the last phone conference. Unless people > feel a real strong need to have the conf. I propose that we do not have > a phone conference and just meet in New Orleans on Wed for the User > Interface portion of the UPDF meeting. > > Reply with your thoughts. > > > Sandra Matts > > ------------------------ > Sandra Matts > Hewlett-Packard > Engineer Scientist > sandram@boi.hp.com > (208) 396-4755 phone > (208) 396-5161 fax From sandram at boi.hp.com Tue Mar 30 13:55:27 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: FW: UPD> phone conf or not Message-ID: <01BE7AA4.34BD50C0@hpb13858.boi.hp.com> No conference call today. Everyone agreed in reply. Those who replied anyway. Sandra Matts -----Original Message----- From: Farrell, Lee [SMTP:Lee_Farrell@cissc.canon.com] Sent: Tuesday, March 30, 1999 10:50 AM To: 'Sandra Matts' Subject: RE: UPD> phone conf or not I assume that the final decision is no conference call today? (There didn't seem to be a notice after your proposal below.) lee -----Original Message----- From: Sandra Matts [mailto:sandram@boi.hp.com] Sent: Monday, March 29, 1999 1:39 PM To: Universal Printer Driver (E-mail) Subject: UPD> phone conf or not Hi, Tomorrow the UPDF group has a phone conference scheduled. There hasn't been much activity since the last phone conference. Unless people feel a real strong need to have the conf. I propose that we do not have a phone conference and just meet in New Orleans on Wed for the User Interface portion of the UPDF meeting. Reply with your thoughts. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Thu Apr 15 19:35:34 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> minutes from UI and imaging mtg Message-ID: <01BE8766.5F1B6F40@hpb13858.boi.hp.com> Hi, I copied the minutes from our UI meeting and Imaging meeting to the ftp site in minutes\1999\updf_mtg.doc. I will also bring a hard copy to Friday's meeting. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Mon Apr 26 19:11:07 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> phone conf tomorrow Message-ID: <01BE9007.C6DB8A80@hpb13858.boi.hp.com> Hi All, We usually have a phone conference the second Tuesday after the PWG meeting. Unfortunately I haven't even put the notes from the meeting on the web page yet or updated the UPDF spec. I plan on doing those tasks this week. Do people still want to have the phone conference or can we delay for two weeks? In two weeks I will have a modified version of the UPDF and notes from the PWG meeting - so I vote for a phone conf. in two weeks. Send your opinion please. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Tue Apr 27 12:48:51 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> phone conference cancelled Message-ID: <01BE909B.8A2EB500@hpb13858.boi.hp.com> Hi All, Today's phone conference is cancelled. We will have a phone conf on Tuesday May 11. I will send out an agenda the week before the conf. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Mon May 10 18:56:16 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> no phone conf. tomorrow Message-ID: <01BE9B06.0543EFC0@hpb13858.boi.hp.com> Hi All, It appears I have to give a presentation tomorrow from 10am - 2 pm and cannot hold the UPDF phone conference. I apologize for the late notice. I will send out notes from the last meeting and start the agenda for the meeting in Philly. If anybody has specific agenda items - please email them. thanks, Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Mon May 17 17:19:55 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> minutes from last meeting on ftp site Message-ID: <01BEA078.B86FB1C0@hpb13858.boi.hp.com> Hi, I've copied the minutes from the last meeting into ftp://ftp.pwg.org/pub/pwg/upd/minutes/1999/upd990416.html I will create pdf and doc versions soon and I should have the web page updated tomorrow. Thank you, Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Wed May 26 14:57:53 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> new locale doc on ftp site Message-ID: <01BEA777.6A84FDC0@hpb13858.boi.hp.com> Hi, I"ve copied a white paper for Locale to ftp.pwg.org/pub/pwg/upd/Archive/Specs/Locale.pdf I will bring hard copies to the meeting Friday but if you want to read it now - download the pdf version. I also fixed some typos in the UPDF spec and posted the new version at ftp.pwg.org/pub/upd/Archive/Specs/UPDF_Spec/v0.51 Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Wed May 26 18:03:27 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> ISO std for Paper sizes Message-ID: <01BEA791.4DA35980@hpb13858.boi.hp.com> Hi, I haven't been able to find a listing of the ISO standard for paper sizes. I can order the standard from ISO but does anyone know of a document that already lists them so I can get started sooner. Also there are several paper size standards. Which one does IPP use? thanks, Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From Robert.Herriot at pahv.xerox.com Fri Jun 4 18:54:16 1999 From: Robert.Herriot at pahv.xerox.com (Herriot, Robert) Date: Wed May 6 14:05:04 2009 Subject: UPD> ISO std for Paper sizes Message-ID: <51B8ABCE456FD111899900805F6FD6EE035C2ADF@mercury.ADOC.xerox.com> IPP Appendix C copied the media and media sizes from ISO 10175 (DPA). IPP contains all values from DPA. The only sizes that are obviously missing are for A, B, C, D and E. A is 8.5x11. Each additional size doubles the short dimension. Tom will add these sizes to the next release of the IPP document which will be ready in a few days. Is there other information you need beyond what IPP Appendix C has? Bob Herriot -----Original Message----- From: Sandra Matts [mailto:sandram@boi.hp.com] Sent: Wednesday, May 26, 1999 3:03 PM To: Universal Printer Driver (E-mail) Subject: UPD> ISO std for Paper sizes Hi, I haven't been able to find a listing of the ISO standard for paper sizes. I can order the standard from ISO but does anyone know of a document that already lists them so I can get started sooner. Also there are several paper size standards. Which one does IPP use? thanks, Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From cmanros at cp10.es.xerox.com Fri Jun 4 20:27:59 1999 From: cmanros at cp10.es.xerox.com (Manros, Carl-Uno B) Date: Wed May 6 14:05:04 2009 Subject: UPD> ISO std for Paper sizes Message-ID: <918C79AB552BD211A2BD00805F15CE85014EAD23@x-crt-es-ms1.cp10.es.xerox.com> Bob, What do you mean with A being 8.5x11? Maybe I am not understanding what you A, B, C etc. refer to. ISO A4 is 210x297 mm, A3 is 297x420 mm, etc. Carl-Uno > -----Original Message----- > From: Herriot, Robert [mailto:Robert.Herriot@pahv.xerox.com] > Sent: Friday, June 04, 1999 3:54 PM > To: Sandra Matts; Universal Printer Driver (E-mail) > Subject: RE: UPD> ISO std for Paper sizes > > > IPP Appendix C copied the media and media sizes from ISO > 10175 (DPA). IPP > contains all values from DPA. The only sizes that are > obviously missing are > for A, B, C, D and E. A is 8.5x11. Each additional size > doubles the short > dimension. Tom will add these sizes to the next release of > the IPP document > which will be ready in a few days. > > Is there other information you need beyond what IPP Appendix C has? > > Bob Herriot > > -----Original Message----- > From: Sandra Matts [mailto:sandram@boi.hp.com] > Sent: Wednesday, May 26, 1999 3:03 PM > To: Universal Printer Driver (E-mail) > Subject: UPD> ISO std for Paper sizes > > > Hi, > I haven't been able to find a listing of the ISO standard > for paper sizes. I can order the standard from ISO but does > anyone know of a document that already lists them so > I can get started sooner. > > Also there are several paper size standards. Which > one does IPP use? > > thanks, > Sandra > > ------------------------ > Sandra Matts > Hewlett-Packard > Engineer Scientist > sandram@boi.hp.com > (208) 396-4755 phone > (208) 396-5161 fax > From Robert.Herriot at pahv.xerox.com Fri Jun 4 20:32:07 1999 From: Robert.Herriot at pahv.xerox.com (Herriot, Robert) Date: Wed May 6 14:05:04 2009 Subject: UPD> ISO std for Paper sizes Message-ID: <51B8ABCE456FD111899900805F6FD6EE035C2AEC@mercury.ADOC.xerox.com> I was referring to English engineering sizes of A (same as letter), B (same as ledger), C, D and E. Bob Herriot -----Original Message----- From: Manros, Carl-Uno B [mailto:cmanros@cp10.es.xerox.com] Sent: Friday, June 04, 1999 5:28 PM To: Herriot, Robert; Sandra Matts; Universal Printer Driver (E-mail) Subject: RE: UPD> ISO std for Paper sizes Bob, What do you mean with A being 8.5x11? Maybe I am not understanding what you A, B, C etc. refer to. ISO A4 is 210x297 mm, A3 is 297x420 mm, etc. Carl-Uno > -----Original Message----- > From: Herriot, Robert [mailto:Robert.Herriot@pahv.xerox.com] > Sent: Friday, June 04, 1999 3:54 PM > To: Sandra Matts; Universal Printer Driver (E-mail) > Subject: RE: UPD> ISO std for Paper sizes > > > IPP Appendix C copied the media and media sizes from ISO > 10175 (DPA). IPP > contains all values from DPA. The only sizes that are > obviously missing are > for A, B, C, D and E. A is 8.5x11. Each additional size > doubles the short > dimension. Tom will add these sizes to the next release of > the IPP document > which will be ready in a few days. > > Is there other information you need beyond what IPP Appendix C has? > > Bob Herriot > > -----Original Message----- > From: Sandra Matts [mailto:sandram@boi.hp.com] > Sent: Wednesday, May 26, 1999 3:03 PM > To: Universal Printer Driver (E-mail) > Subject: UPD> ISO std for Paper sizes > > > Hi, > I haven't been able to find a listing of the ISO standard > for paper sizes. I can order the standard from ISO but does > anyone know of a document that already lists them so > I can get started sooner. > > Also there are several paper size standards. Which > one does IPP use? > > thanks, > Sandra > > ------------------------ > Sandra Matts > Hewlett-Packard > Engineer Scientist > sandram@boi.hp.com > (208) 396-4755 phone > (208) 396-5161 fax > From sandram at boi.hp.com Tue Jun 8 10:18:05 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> ISO std for Paper sizes Message-ID: <01BEB187.6FB84080@hpb13858.boi.hp.com> thanks - that will give us a start. I will put a list in the UPDF spec. and send it out. Sandra -----Original Message----- From: Herriot, Robert [SMTP:Robert.Herriot@pahv.xerox.com] Sent: Friday, June 04, 1999 4:54 PM To: Sandra Matts; Universal Printer Driver (E-mail) Subject: RE: UPD> ISO std for Paper sizes IPP Appendix C copied the media and media sizes from ISO 10175 (DPA). IPP contains all values from DPA. The only sizes that are obviously missing are for A, B, C, D and E. A is 8.5x11. Each additional size doubles the short dimension. Tom will add these sizes to the next release of the IPP document which will be ready in a few days. Is there other information you need beyond what IPP Appendix C has? Bob Herriot -----Original Message----- From: Sandra Matts [mailto:sandram@boi.hp.com] Sent: Wednesday, May 26, 1999 3:03 PM To: Universal Printer Driver (E-mail) Subject: UPD> ISO std for Paper sizes Hi, I haven't been able to find a listing of the ISO standard for paper sizes. I can order the standard from ISO but does anyone know of a document that already lists them so I can get started sooner. Also there are several paper size standards. Which one does IPP use? thanks, Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Tue Jun 8 11:10:34 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> phone conf Message-ID: <01BEB18E.C4A9FE60@hpb13858.boi.hp.com> I will activate the phone conference at 10am Pacific time today if people want to talk. I didn't have time to set up an agenda but people might want to find out about the last meeting. And discuss items for this month. Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Tue Jun 8 11:34:47 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> phone number Message-ID: <01BEB192.26C15AA0@hpb13858.boi.hp.com> Phone number is: 1-612-315-6802 access code: 058459494 -----Original Message----- From: Sandra Matts [SMTP:sandram@boi.hp.com] Sent: Tuesday, June 08, 1999 9:11 AM To: Universal Printer Driver (E-mail) Subject: UPD> phone conf I will activate the phone conference at 10am Pacific time today if people want to talk. I didn't have time to set up an agenda but people might want to find out about the last meeting. And discuss items for this month. Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Tue Jun 8 12:10:43 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> phone conf Message-ID: <01BEB197.2C1E16A0@hpb13858.boi.hp.com> Since I sent such short notice on the phone conf., We can set up a another one for next Tuesday if that works for most people. I will send out an agenda by thur this week. Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Fri Jun 11 12:01:19 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> Tuesday phone conf Message-ID: <01BEB3F1.5B12C6C0@hpb13858.boi.hp.com> Hi All, I'm trying to set up a phone conf for either next Tuesday or the following Tuesday. The two dates are: June 15 10-12 am Pacific or June 22 10-12 am. agenda so far: Process for moving open issues to closed. Locale: Proposal is to use the ISO standards for language / country. Update on 2 or three letter acronym. Look at creating actual XML for Locale and Default Paper Handling for UPDF spec. PDL registration and specification Font metrics List of things to go into implementor's guide so far. If people have a strong opinion of which Tuesday to hold the phone conf. - reply to this email. Otherwise I will pick one. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From Michael_Yeung at cissc.canon.com Fri Jun 11 13:45:24 1999 From: Michael_Yeung at cissc.canon.com (Yeung, Michael) Date: Wed May 6 14:05:04 2009 Subject: UPD> Tuesday phone conf Message-ID: <6C940F5153E5D211937A0090274E8D8B165AC9@cissc.cisoc.canon.com> I would prefer June 22, because of Java0ne (Starts next week!) Mike -----Original Message----- From: Sandra Matts [mailto:sandram@boi.hp.com] Sent: Friday, June 11, 1999 9:01 AM To: Universal Printer Driver (E-mail) Subject: UPD> Tuesday phone conf Hi All, I'm trying to set up a phone conf for either next Tuesday or the following Tuesday. The two dates are: June 15 10-12 am Pacific or June 22 10-12 am. agenda so far: Process for moving open issues to closed. Locale: Proposal is to use the ISO standards for language / country. Update on 2 or three letter acronym. Look at creating actual XML for Locale and Default Paper Handling for UPDF spec. PDL registration and specification Font metrics List of things to go into implementor's guide so far. If people have a strong opinion of which Tuesday to hold the phone conf. - reply to this email. Otherwise I will pick one. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Fri Jun 11 16:02:42 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> Tuesday phone conf Message-ID: <01BEB413.137EADC0@hpb13858.boi.hp.com> We will have the phone conference on June 22 10-12am Pacific. thanks, Sandra -----Original Message----- From: Sandra Matts [SMTP:sandram@boi.hp.com] Sent: Friday, June 11, 1999 10:01 AM To: Universal Printer Driver (E-mail) Subject: UPD> Tuesday phone conf Hi All, I'm trying to set up a phone conf for either next Tuesday or the following Tuesday. The two dates are: June 15 10-12 am Pacific or June 22 10-12 am. agenda so far: Process for moving open issues to closed. Locale: Proposal is to use the ISO standards for language / country. Update on 2 or three letter acronym. Look at creating actual XML for Locale and Default Paper Handling for UPDF spec. PDL registration and specification Font metrics List of things to go into implementor's guide so far. If people have a strong opinion of which Tuesday to hold the phone conf. - reply to this email. Otherwise I will pick one. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From BEN_BREZINSKI at HP-Vancouver-om1.om.hp.com Mon Jun 14 14:50:24 1999 From: BEN_BREZINSKI at HP-Vancouver-om1.om.hp.com (BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com) Date: Wed May 6 14:05:04 2009 Subject: UPD> Tuesday phone conf In-Reply-To: <01BEB3F1.5B12C6C0@hpb13858.boi.hp.com> Message-ID: Item Subject: UPD> Tuesday phone conf June 22 would work for me. I am booked June 15. I vote for the ISO standards for language/country, 3 letter codes. I have no opinion on font metrics. Here is what I wrote down so far for the implementor's guide. No UI controls are required in the UPDF. The driver implementers may choose to implement whatever controls he chooses. Dynamic nature of the UPDF file. The driver implemter should be aware that the UPDF file reflect the current configuration, and may change as accessories are added or deleted. The frequency of update is not specified, but should be reasonable. Mapping of UPDF language_country codes to operating systems. Ben Brezinski ______________________________ Reply Separator _________________________________ Subject: UPD> Tuesday phone conf Author: sandram-at-boi (sandram@boi.hp.com) at HP-Vancouver,shargw1 Date: 6/11/99 9:01 AM Hi All, I'm trying to set up a phone conf for either next Tuesday or the following Tuesday. The two dates are: June 15 10-12 am Pacific or June 22 10-12 am. agenda so far: Process for moving open issues to closed. Locale: Proposal is to use the ISO standards for language / country. Upd ate on 2 or three letter acronym. Look at creating actual XML for Locale and De fault Paper Handling for UPDF spec. PDL registration and specification Font metrics List of things to go into implementor's guide so far. If people have a strong opinion of which Tuesday to hold the phone conf. - reply to this email. Otherwise I will pick one. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Mon Jun 14 15:45:43 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: FW: UPD> Tuesday phone conf Message-ID: <01BEB66C.3325EFC0@hpb13858.boi.hp.com> ok so I left out a few details. 612-315-6802 access code: 058459494 Sandra Matts -----Original Message----- From: BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com [SMTP:BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com] Sent: Monday, June 14, 1999 1:29 PM To: sandram@boi.hp.com Subject: RE: UPD> Tuesday phone conf And the number is.......? Ben B ______________________________ Reply Separator _________________________________ Subject: RE: UPD> Tuesday phone conf Author: sandram-at-boi (sandram@boi.hp.com) at HP-Vancouver,shargw1 Date: 6/11/99 1:02 PM We will have the phone conference on June 22 10-12am Pacific. thanks, Sandra -----Original Message----- From: Sandra Matts [SMTP:sandram@boi.hp.com] Sent: Friday, June 11, 1999 10:01 AM To: Universal Printer Driver (E-mail) Subject: UPD> Tuesday phone conf Hi All, I'm trying to set up a phone conf for either next Tuesday or the following Tuesday. The two dates are: June 15 10-12 am Pacific or June 22 10-12 am. agenda so far: Process for moving open issues to closed. Locale: Proposal is to use the ISO standards for language / country. Upd ate on 2 or three letter acronym. Look at creating actual XML for Locale and De fault Paper Handling for UPDF spec. PDL registration and specification Font metrics List of things to go into implementor's guide so far. If people have a strong opinion of which Tuesday to hold the phone conf. - reply to this email. Otherwise I will pick one. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Wed Jun 16 12:53:37 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> minutes on ftp site Message-ID: <01BEB7E6.7D4CD160@hpb13858.boi.hp.com> Hi All, I copied the minutes from the last meeting onto the ftp site. It's at: ftp://ftp.pwg.org/pub/pwg/upd/minutes/1999/upd990528.htm I'm working on updating the Locale white paper a bit and the issues doc. I will copy those to the Archive section of the ftp site when I'm done. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at hpbs1061.boi.hp.com Fri Jun 18 17:16:26 1999 From: sandram at hpbs1061.boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> new dtd and xml Message-ID: <9906182116.AA12036@hpbs1061.boi.hp.com> Hi All, I copied a new dtd and Color laserJet 4500 xml file that has a stab at the start of Locale using the ISO standards. Please take a look at it and email comments. It's in ftp.pwg.org/pub/pwg/upd/Archive/1999/990618 There are pdf versions of the files with changes in yellow highlight. There is also the updf.dtd file and an xml file showing implementation. Sandra Matts Engineer Scientist Hewlett-Packard sandram@boi.hp.com From sandram at hpbs1061.boi.hp.com Mon Jun 21 17:47:34 1999 From: sandram at hpbs1061.boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> XML based UI work Message-ID: <9906212147.AA25252@hpbs1061.boi.hp.com> Hi All, I found a couple of very interesting sites defining User Interface components in XML. They look quite promising for our work and I believe we can leverage their work. The first one is at: www.oasis-open.org/cover/uiml.html The group is defining a language for the actual interface elements in a graphical interface like Windows and Motif. The second one is at: www.oasis-open.org/cover/xul.html This work appears to be defining an XToolkit and I don't know how tied to Unix it is. Sandra Matts Engineer Scientist Hewlett-Packard 208-396-4755 From charles.a.adams at exgate.tek.com Tue Jul 27 10:40:34 1999 From: charles.a.adams at exgate.tek.com (charles.a.adams@exgate.tek.com) Date: Wed May 6 14:05:04 2009 Subject: UPD> DTD's vs. Schema's Message-ID: <6B57A2A3212BD2119C2600805F6F1413027873A2@us-wv-m11.wv.tek.com> More food for thought. * EXTREME XML: Describe Your Data - DTD or schema? http://msdn.microsoft.com/voices/xml.asp Charles "Chuck" Adams adamsc@pogo.wv.tek.com Tektronix, Inc. From sandram at boi.hp.com Thu Aug 12 13:15:31 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> notes from Denmark and new docs Message-ID: <01BEE4B3.FE23F1C0@hpb13858.boi.hp.com> Hi All, I have just returned from a 4.5 week vacation and I now realize my out of office reply did not work correctly. I apologize if people sent me email and I did not reply. Anyway I am trying to copy documents from the Denmark meeting to the ftp site and haven't been successful. We are trying to get it resolved currently. In the meantime - do people want me to attach pdf versions to an email message? I know the email reflector does not like large emails and they tend to bounce if they are too big. I can also try to copy from my home machine which has no security at all and see if I can get through. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Thu Aug 12 13:32:37 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> re-scope of UPDF Message-ID: <01BEE4B6.618F13A0@hpb13858.boi.hp.com> Hi, Even though the UPDF spec is coming along - the work is not as focused as it could be. I believe there are a couple of reasons for this. One being there sheer size of the task. We did an excellent job dividing the job into sections - UI, Localization, etc - but I haven't done a very good job keeping the work focused on a specific area. Another issue has been the usefulness of the project itself. Is UPDF really needed when IPP can retrieve some of the info from the printer? Can IPP and UPDF complement each other or is there maybe too much overlap? There also has been some thought about steering UPDF towards a Linux (and other Unix flavors) printing solution and not really a "Universal" solution. What do people think about that? Chuck sent out the DTD vs Schema link. This is something to look at. Also please check out the UIML and XUL documents for User Interface specification in UPDF. thanks, Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Fri Aug 13 14:57:50 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:05 2009 Subject: UPD> updated docs Message-ID: <01BEE58B.73CBBF20@hpb13858.boi.hp.com> Hi, Attached are the latest dtd and xml documents that contain the locale syntax. The locale list is not all inclusive but only a short example list currently. I was able to copy slides from the Denmark meeting to ftp.pwg.org/pub/pwg/upd/minutes/1999/updf_mtg990709.pdf and .ppt Also I copied a new document that shows a mapping of UPDF to PPD keywords. ftp.pwg.org/pub/pwg/upd/Archive/Specs/mapping_updf_ppd.pdf and .doc And lastly I copied an updated version of locale.doc and pdf. Unfortunately, Windows is not as case sensitive as Unix and there are two copies of the docs: Locale and locale. I wasn't able to telnet in to rename so please get the doc with the latest date. I'm working on minutes from the Denmark meeting and an updated UPDF spec. I will post when done and I will also bring copies to the Alaska meeting. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax begin 600 CLJ4500.xml M/#]X;6P@=F5R2!B87-I8R!54$1&(&9I M;&4@=VET:"!J=7-T('1H92!M:6YI;75M(')E<75I7,@551&+3@N#0H-"B @("!,;V-A;&5S('-U M<'!O2!T:&ES(%501$8@9FEL92X-"CPA+2T@+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+B M+3X-"B @(" \3&]C86QE3&ES=#X-"B @(" @(" @/$QO8V%L92!, M;V-A;&5)9#TB96Y?054B/CPO3&]C86QE/@T*(" @(" @(" \3&]C86QE($QO M8V%L94ED/2)E;E]'0B(^/"],;V-A;&4^#0H@(" @(" @(#Q,;V-A;&4@3&]C M86QE260](F5N7U53(CX\+TQO8V%L93X-"B @(" @(" @/$QO8V%L92!,;V-A M;&5)9#TB9&%?1$LB/CPO3&]C86QE/@T*(" @(" @(" \0W5S=&]M3&]C86QE M#0H@(" @(" @(" @("!#=7-T;VU,;V-A;&5)9#TB96Y?54LB/CPO0W5S=&]M M3&]C86QE/@T*(" @(" @(" \0W5S=&]M3&]C86QE#0H@(" @(" @(" @("!# M=7-T;VU,;V-A;&5)9#TB86%?0D(B/CPO0W5S=&]M3&]C86QE/@T*(" @(#PO M3&]C86QE3&ES=#X-"@T*(" @(#Q&:6QE3F%M93Y#3$HT-3 P+GAM;#PO1FEL M94YA;64^#0H-"B @(" \0W5S=&]M1&5V:6-E0V%P5&%G7!E-#(B+SX-"B @(" \+T-U M2!M=6QT:7!L92!L86YG=6%G97,@ M+2!A="!L96%S="!T:')E90T*/"$M+2 N+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN("TM/@T* M(" @(" @(" @(" @(" @(#Q,86YG=6%G92Y01$P@#0H@(" @(" @(" @(" @ M(" @(" @("!01$Q-86IOF5+8CTB,S(W-C@B#0H@(" @(" @(" @(" @(" @(" @(" @("!204U);G1E M7-I8V%L/@T*(" @(" @(" @(" @/%!L M871F;W)M/@T*(" @(" @(" @(" @(" @(#Q-;V1U;&5.86UE7,^/"]/=F5R;&%Y T*(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" \54E#;VYT4UA;F%G93X\+U!R M:6YT97)-96UOF4Z($QE='1E MF4](D1-4$%015)?030B+SX-"B @(" @(" @(" @(" @ M(" @(" @(" @(" @(" \+T100W5S=&]M3&]C86QE/@T*(" @(" @(" @(" @ M(" @(" @(" @(" @/"]$969A=6QT4&%P97(^#0H-"@T*(" @(" @(" @(" @ M(" @(" @(" @(" @/%!A<&5R(&1M<&%P97)S:7IE/2)$35!!4$527TQ%5%1% M4B(^3&5T=&5R#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @/%!A<&5R M+D%R96$^#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @/"$M+2TM+2TM M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM M+2T-"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @25-3544Z("I) M;6%G96%B;&5!&5L#0H@(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @("!L969T/2(Q,BXP,"(@=&]P/2(Q,BXQ M,B(@&5L#0H@(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @;&5F=#TB,3(N,# B('1O<#TB,3(N,3(B(')I M9VAT/2(U.#,N,#@B(&)O='1O;3TB.#(Y+C8X(B\^#0H@(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(#Q087!E#TB M,3$Q,2(@>3TB,3$Q,2(O/@T*(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(#PO4&%P97(N07)E83X-"B @(" @(" @(" @(" @(" @(" @(" @(#PO4&%P M97(^#0H@(" @(" @(" @(" @(" @(" @(" @(" \4&%P97(@9&UP87!EF4](D1-4$%015)?3$5'04PB/DQE9V%L#0H@(" @(" @(" @(" @(" @(" @ M(" @(" @(" @/%!A<&5R+D%R96$^#0H@(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(#Q087!E&5L('@](C8Q,B(@>3TB M,3 P."(O/@T*(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" \4&%P M97(N07)E82YR8TUA&5L#0H@(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @;&5F=#TB,3(N,# B('1O<#TB,3(N,3(B(')I M9VAT/2(U.3DN.#@B(&)O='1O;3TB.3DU+CDP(B\^#0H@(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(#Q087!E#TB M,3$Q,2(@>3TB,3$Q,2(O/@T*(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(#PO4&%P97(N07)E83X-"B @(" @(" @(" @(" @(" @(" @(" @(#PO4&%P M97(^#0H-"B @(" @(" @(" @(" @(" @(" @(" @(#Q087!E&5L#0H@(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @;&5F=#TB,3(N,# B('1O<#TB M,3(N,3(B(')I9VAT/2(U,#DN.#@B(&)O='1O;3TB-S0S+CDP(B\^#0H@(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q087!E#TB,3$Q,2(@>3TB,3$Q,2(O/@T*(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(#PO4&%P97(N07)E83X-"B @(" @(" @(" @(" @(" @(" @ M(" @(#PO4&%P97(^#0H-"B @(" @(" @(" @(" @(" @(" @(" @(#Q087!E M#TB-#(P M(B!Y/2(U.34B+SX-"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M/%!A<&5R+D%R96$NF5-;3$P M('@](C$Q,3$B('D](C$Q,3$B+SX-"B @(" @(" @(" @(" @(" @(" @(" @ M(" @(" \+U!A<&5R+D%R96$^#0H@(" @(" @(" @(" @(" @(" @(" @(" \ M+U!A<&5R/@T*#0H@(" @(" @(" @(" @(" @(" @(" @(" \4&%P97(@9&UP M87!EF4](D1-4$%015)?0C4B/D(U("A*25,I#0H@(" @(" @(" @(" @ M(" @(" @(" @(" @(" @/%!A<&5R+D%R96$^#0H@(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(#Q087!E&5L('@](C4Q M-B(@>3TB-S(Y(B\^#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(#Q087!E#TB-#DY(B!Y/2(W,#DB+SX-"B @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @/%!A<&5R+D%R96$NF5-;3$P('@](C$Q,3$B('D](C$Q,3$B+SX-"B @(" @(" @(" @(" @ M(" @(" @(" @(" @(" \+U!A<&5R+D%R96$^#0H@(" @(" @(" @(" @(" @ M(" @(" @(" \+U!A<&5R/@T*#0H@(" @(" @(" @(" @(" @(" @(" @(" \ M4&%P97(@9&UP87!EF4](D1-4$%015)?14Y67S$P(CY%;G9E;&]P92 C M,3 -"B @(" @(" @(" @(" @(" @(" @(" @(" @(" \4&%P97(N07)E83X- M"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @/%!A<&5R+D%R96$N M<'1!#TB,CDW(B!Y/2(V.#0B+SX-"B @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @/%!A<&5R+D%R96$NF5-;3$P('@](C$Q,3$B('D](C$Q,3$B+SX-"B @(" @ M(" @(" @(" @(" @(" @(" @(" @(" \+U!A<&5R+D%R96$^#0H@(" @(" @ M(" @(" @(" @(" @(" @(" \+U!A<&5R/@T*#0H@(" @(" @(" @(" @(" @ M(" @(" @(" \4&%P97(@9&UP87!EF4](D1-4$%015)?14Y67T,U(CY% M;G9E;&]P92!#-0T*(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q087!E M&5L#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @;&5F=#TB,3(N,# B('1O<#TB,3(N,3(B(')I9VAT/2(T-#3TB-C(T(B\^ M#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q087!E&5L M('@](C(W.2(@>3TB-30P(B\^#0H@(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(#Q087!E"!T1'5P;&5X/2)/3B(^/"]$=7!L97@^#0H@(" @(" @(" @(" @(" @ M(" @(#Q";V]K;&5T('1";V]K;&5T/2)/1D8B+SX-"B @(" @(" @(" @(" @ M(" @(" @/$-E;G1E7-T96US+"!);F,@(" @(" @(" @(" @(" @(" @(" @(" M+3X-"CPA+2T@ M4')I;G1EF5?96YU;2 -"@DG*"!&04Q317P-"@E$35!!4$527TQ% M5%1%4GP-"@E$35!!4$527TQ%5%1%4E--04Q,? T*"41-4$%015)?5$%"3$]) M1'P-"@E$35!!4$527TQ%1$=%4GP-"@E$35!!4$527TQ%1T%,? T*"41-4$%0 M15)?4U1!5$5-14Y4? T*"41-4$%015)?15A%0U54259%? T*"41-4$%015)? M03-\#0H)1$U005!%4E]!-'P-"@E$35!!4$527T$T4TU!3$Q\#0H)1$U005!% M4E]!-7P-"@E$35!!4$527T(T? T*"41-4$%015)?0C5\#0H)1$U005!%4E]& M3TQ)3WP-"@E$35!!4$527U%505)43WP-"@E$35!!4$527S$P6#$T? T*"41- M4$%015)?,3%8,3=\#0H)1$U005!%4E].3U1%? T*"41-4$%015)?14Y67SE\ M#0H)1$U005!%4E]%3E9?,3!\#0H)1$U005!%4E]%3E9?,3%\#0H)1$U005!% M4E]%3E9?,3)\#0H)1$U005!%4E]%3E9?,31\#0H)1$U005!%4E]#4TA%151\ M#0H)1$U005!%4E]$4TA%151\#0H)1$U005!%4E]%4TA%151\#0H)1$U005!% M4E]%3E9?1$Q\#0H)1$U005!%4E]%3E9?0S5\#0H)1$U005!%4E]%3E9?0S-\ M#0H)1$U005!%4E]%3E9?0S1\#0H)1$U005!%4E]%3E9?0S9\#0H)1$U005!% M4E]%3E9?0S8U? T*"41-4$%015)?14Y67T(T? T*"41-4$%015)?14Y67T(U M? T*"41-4$%015)?14Y67T(V? T*"41-4$%015)?14Y67TE404Q9? T*"41- M4$%015)?14Y67TU/3D%20TA\#0H)1$U005!%4E]%3E9?4$524T].04Q\#0H) M1$U005!%4E]&04Y&3TQ$7U53? T*"41-4$%015)?1D%.1D],1%]35$1?1T52 M34%.? T*"41-4$%015)?1D%.1D],1%],1TQ?1T5234%.? T*"41-4$%015)? M25-/7T(T? T*"41-4$%015)?2D%004Y%4T5?4$]35$-!4D1\#0H)1$U005!% M4E\Y6#$Q? T*"41-4$%015)?,3!8,3%\#0H)1$U005!%4E\Q-5@Q,7P-"@E$ M35!!4$527T5.5E])3E9)5$5\#0H)1$U005!%4E]215-%4E9%1%\T.'P-"@E$ M35!!4$527U)%4T525D5$7S0Y? T*"41-4$%015)?3$545$527T585%)!? T* M"41-4$%015)?3$5'04Q?15A44D%\#0H)1$U005!%4E]404),3TE$7T585%)! M? T*"41-4$%015)?031?15A44D%\#0H)1$U005!%4E],151415)?5%)!3E-6 M15)317P-"@E$35!!4$527T$T7U1204Y35D524T5\#0H)1$U005!%4E],1514 M15)?15A44D%?5%)!3E-615)317P-"@E$35!!4$527T%?4$Q54WP-"@E$35!! M4$527T)?4$Q54WP-"@E$35!!4$527TQ%5%1%4E]03%53? T*"41-4$%015)? M031?4$Q54WP-"@E$35!!4$527T$U7U1204Y35D524T5\#0H)1$U005!%4E]" M-5]44D%.4U9%4E-%? T*"41-4$%015)?03-?15A44D%\#0H)1$U005!%4E]! M-5]%6%1207P-"@E$35!!4$527T(U7T585%)!? T*"41-4$%015)?03)\#0H) M1$U005!%4E]!,U]44D%.4U9%4E-%? T*"41-4$%015)?03-?15A44D%?5%)! M3E-615)317P-"@E$35!!4$527U5315)\#0H)1$U005!%4E]*05!!3D5315]% M3E9?631\#0H)1$U005!%4E]*05!!3D5315]%3E9?63)\#0H)1$U005!%4E]* M05!!3D5315]%3E9?2S(I)SX-"CPA14Y42519("4@9&UP87!EF5?871T MF5?96YU;3L@(D9!3%-% M(B<^#0H-"CPA14Y42519("4@9&UP7!E("A.3TY% M?$9L87-H?$A$1"D@(DY/3D4B( T*"0D)4W1OF4@3DU43TM%3B B M,"(^#0H)/"$M+2 N+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BTM/@T*"3PA+2T@3U,O2$]3 M5" @0V]L;W(@36%N86=E;65N="]296YD97)I;F<@(" @(" @(" @(" @(" @ M(" @(" @(" @(" M+3X-"@D\(2TM("XN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+2T^#0H) M/"%%3$5-14Y4(%!L871F;W)M("A-;V1U;&5.86UEF%T:6]N(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" M+3X- M"@D\(2TM("XN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+2T^#0H)/"%%3$5-14Y4($QO8V%L M:7IA=&EO;B!%35!462 ^#0H)/"$M+2 N+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BTM/@T* M"3PA+2T@1VQO8F%L(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" M+3X-"@D\(2TM("XN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+2T^#0H@(" @/"%%3$5-14Y4($=L;V)A;" H57-E4UA;F%G92Q004=%4%)/5$5#5%,L4D533TQ55$E/3E,L#0H@(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @("!43TY%4E-!5D53+"!334]/5$A) M3D=-3T1%4RQ$251(15)334]/5$A)3D=3+ T*(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @1$E42$524RP@54E#;VYS=')A:6YT'Q,:7-T*3X-"B @ M(" @(" @/"%%3$5-14Y4($)U='1O;B!%35!463X-"B @(" @(" @/"%%3$5- M14Y4(%)A9&EO0G5T=&]N1W)O=7 @*%)A9&EO0G5T=&]N*RD^#0H@(" @(" @ M(#PA05143$E35"!2861I;T)U='1O;D=R;W5P#0H@(" @(" @(" @("!.=6U" M=71T;VYS($Y-5$]+14X@(C$B/@T*(" @(" @(" @(" @/"%%3$5-14Y4(%)A M9&EO0G5T=&]N($5-4%19/@T*(" @(" @(" @(" @/"%!5%1,25-4(%)A9&EO M0G5T=&]N#0H@(" @(" @(" @(" @(" @54E,86)E;"!#1$%402 C24U03$E% M1 T*(" @(" @(" @(" @(" @($-O;6UA;F0@0T1!5$$@(TE-4$Q)140^#0H@ M(" @(" @(#PA14Q%345.5"!#:&5C:T)O>"!%35!463X-"B @(" @(" @/"%% M3$5-14Y4($QI4UA;F%G92 H(U!#1$%4 M02D^#0H@(" @(" @(#PA05143$E35"!04UA;F%G94ED("A.3TY%?$UA>&E- M96U\365T?$UE;6]R>4)O;W-T97(I(").3TY%(CX-"B @(" @(" @/"%%3$5- M14Y4(%!!1T504D]414-44R H4&%G95!R;W1E8W0J*3X-"B @(" @(" @/"%! M5%1,25-4(%!!1T504D]414-44R -"B @(" @(" @(" @(&9086=E4')O=&5C M=" E8F]O;%]A='1R:6)U=&5?9F%L6]U=" -"@D)"0D)1W)A>6]U=$ED("A04DE.5$521$5&055,5'Q4 M97AT1W)A<&AI8WQ497AT?$]F9GQ$969A=6QT?$=R87!H:6-\26UA9V5\5&5X M=$EM86=E?$=R87!H:6-);6%G97Q!;&PI(")04DE.5$521$5&055,5"(@/@T* M"0D)/"$M+2!$:71H97)S(&5N9" M+3X-"@T*"0D\(45,14U%3E0@54E#;VYS M=')A:6YT&EN9TUO9&4L2&E296=I6]U="HI/@T* M"0D)/"%!5%1,25-4($Q!64]55%,@#0H)"0D)=$QA>6]U=" E&5L+ T*"0D)"0D)"5!A<&5R+D%R96$N<'13 M:7IE36TQ,"Q087!EF5);F-H,3 P( T*"0D)"0D))7!O:6YT7V%T M=')I8G5T97,[/@T*"0D)"0D\(45,14U%3E0@4&%P97(N07)E82YP=$%R96%- M;3$P($5-4%19(#X-"@D)"0D)/"%!5%1,25-4(%!A<&5R+D%R96$N<'1!6]U=$9L86<@ M14U05%D^#0H)"0D)/"%!5%1,25-4(%!A<&5R+DQA>6]U=$9L86<@#0H)"0D) M"69!F5-;3$P+%5$4$EN9F\N<'1-87A3 M:7IE36TQ,"D^#0H)"0D)/"%%3$5-14Y4(%5$4$EN9F\N<'1$9693:7IE36TQ M,"!%35!462 ^#0H)"0D)/"%!5%1,25-4(%5$4$EN9F\N<'1$9693:7IE36TQ M," -"@D)"0D))7!O:6YT7V%T=')I8G5T97,[/@T*"0D)"3PA14Q%345.5"!5 M1%!);F9O+G)C36%R9VEN36TQ,"!%35!462 ^#0H)"0D)/"%!5%1,25-4(%5$ M4$EN9F\NF5-;3$P($5-4%19(#X- M"@D)"0D\(4%45$Q)4U0@541026YF;RYP=$UI;E-I>F5-;3$P( T*"0D)"0DE M<&]I;G1?871T7Q#;V%T961\3&%B96QS*2 B4%))3E1%4D1%1D%53%0B(#X-"@D@(" @/"$M M+2 N+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+2T^#0H)(" @(#PA+2T@4&%P97)(86YD;&EN9R @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @("TM M/@T*"2 @(" \(2TM("XN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXM+3X-"@D)/"%%3$5-14Y4(%!A M<&5R2&%N9&QI;F<@*%!!4$524T]54D-%4RQ005!%4D1%4U1)3D%424].4RD^ M#0H)"3PA+2T@+2T^#0H)"3PA14Q%345.5"!005!%4E-/55)#15,@*$1E9F%U M;'1087!E#\L0F]O:VQE=#\L0V5N M=&5R1F]L9$%N9%-T87!L93\L4F5V97)S94]R9&5R/RQ*;V)/9F9S970_+$-O M;&QA=&4L1W)O=7 _+$UA:6Q";W@_+%-T87!L93\L1D],1%,_+$AO;&50=6YC M:#\I/@T*"0D\(4%45$Q)4U0@1DE.25-(24Y'4R -"@D)"71&:6YI"!%35!463X-"@D)"3PA05143$E35"!$=7!L97@@#0H)"0D)=$1U<&QE M>" E7!E/RD^#0H) M"0D\(4%45$Q)4U0@0V]L;&%T92 -"@D)"0ET0V]L;&%T92 E" -"@D)"0ET36%I;$)O>" E$YU;2 H(U!#1$%402D^#0H)"0D)/"%%3$5-14Y4(%-T M87!L92Y,3T-!5$E/3E,@*%-T87!L92Y,;V-A=&EO;BHI/@T*"0D)"3PA0514 M3$E35"!3=&%P;&4N3$]#051)3TY3( T*"0D)"0E3=&%P;&4N3G5M3&]C871I M;VX@3DU43TM%3B B,"(^#0H)"0D)"3PA14Q%345.5"!3=&%P;&4N3&]C871I M;VX@*"-00T1!5$$I/@T*"0D)"0D\(4%45$Q)4U0@4W1A<&QE+DQO8V%T:6]N M( T*"0D)"0D)4W1A<&QE+DQO8V%T:6]N260@)7-T87!L96QO8V%T:6]N7V%T M=')I8G5T95]D969A=6QT.SX-"@D)"3PA14Q%345.5"!&3TQ$4R H1F]L9"HI M/@T*"0D)/"%!5%1,25-4($9/3$13( T*"0D)"71&;VQD("5S=&%T93-?871T M7!E*3X-"@D)"0D)/"%%3$5-14Y4 M($9O;&0N5'EP92!%35!463X@#0H)"0D)"3PA05143$E35"!&;VQD+E1Y<&4@ M#0H)"0D)"0E&;VQD5'EP94ED("A.3TY%?%I&;VQD?%-A9&1L97Q$;W5B;&5' M871E?$QE9G1'871E?%)I9VAT1V%T97Q,971T97)&;VQD?%A&;VQD*2 B3D]. M12(-"@D)"0D)"4UA>$YU;0E.351/2T5.("-)35!,245$/@T*"0D)/"%%3$5- M14Y4($AO;&50=6YC:" H2&]L95!U;F-H+DUA>$YU;3\I/@T*"0D)/"%!5%1, M25-4($AO;&50=6YC: T*"0D)"71(;VQE4'5N8V@@)7-T871E,U]A='1R:6)U M=&5?9&5F875L=#L^#0H)"0D)/"%%3$5-14Y4($AO;&50=6YC:"Y-87A.=6T@ M*"-00T1!5$$I/@T*#0H@(" @(" @(#PA+2T@+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BTM/@T* M(" @(" @(" \(2TM($-O;&]R&5L1&5P=&A)9"!.351/2T5. M("-)35!,245$( T*"0D)"4-O;&]R4W!A8V5)9" E8V]L;W)S<&%C95]E;G5M M.R B3D].12(^#0H)(" @(#PA+2T@+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BTM/@T*"0D\(2TM M($5X<&%N'!&;VYT0V%R9"Y&3TY44R -"@D)"0D) M"45X<$9O;G1.=6T@3DU43TM%3B C24U03$E%1#X-"@D)"0D)"3PA+2T@14Q% M345.5"!&;VYT("@C4$-$051!*2TM/@T*"0D)#0H)"0D\(45,14U%3E0@15A0 M1%503$584R H17AP1'5P;&5X*BD^#0H)"0D\(4%45$Q)4U0@15A01%503$58 M4R -"@D)"0EF17AP1'5P;&5X("5B;V]L7V%T=')I8G5T95]F86QS93L@#0H) M"0D)3G5M17AP1'5P;&5X($Y-5$]+14X@(C B/@T*"0D)"3PA14Q%345.5"!% M>'!$=7!L97@@*%!#1$%402Q005!%4E,I/@T*"0D)"0D\(2TM(#\_/S\_($9) M3DE32$E.1U,@+2T^#0H)"0D)"3PA+2T@14Q%345.5"!005!%4E,@*%!A<&5R M*2LM+3X-"@D)"0T*"0D)/"%%3$5-14Y4($584%!!4$524T]54D-%4R H17AP M4&%P97)3;W5R8V4J*3X-"@D)"3PA05143$E35"!%6%!005!%4E-/55)#15,@ M#0H)"0D)9D5X<%!A<&5R4V]U re-scope of UPDF In-Reply-To: <01BEE4B6.618F13A0@hpb13858.boi.hp.com> Message-ID: Item Subject: UPD> re-scope of UPDF I don't see any much overlap between IPP and UPDF. UPDF is the description of the printer, and is (should be?) transport independent. As far as I know, we haven't made IPP a required component of UPDF. I agree that we need to re-clarify. IPP is capable of retreiving facts about the printer, but UPDF expresses not only the facts, but how they relate to one another. If we steer toward Linux and Unix, then we need to drop the "U" from the comittee name, as it will no longer be universal, and will be of a much more limited interest to me. Regards, Ben B ______________________________ Reply Separator _________________________________ Subject: UPD> re-scope of UPDF Author: sandram-at-boi (sandram@boi.hp.com) at HP-Vancouver,shargw1 Date: 8/12/99 10:32 AM Hi, Even though the UPDF spec is coming along - the work is not as focused as it could be. I believe there are a couple of reasons for this. One being ther e sheer size of the task. We did an excellent job dividing the job into sections - UI, Localization, etc - but I haven't done a very good job keeping the work focused on a specific area. Another issue has been the usefulness of the project itself. Is UPDF really needed when IPP can retrieve some of the info from the printer? Can IPP and UPDF complement each other or is there maybe too much overlap? There also has been some thought about steering UPDF towards a Linux (and other Unix flavors) printing solution and not really a "Universal" solution. What do people think about that? Chuck sent out the DTD vs Schema link. This is something to look at. Als o please check out the UIML and XUL documents for User Interface specification in UPDF. thanks, Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From qaisi at apple.com Fri Aug 13 19:36:34 1999 From: qaisi at apple.com (Abdallah Qaisi) Date: Wed May 6 14:05:05 2009 Subject: UPD> re-scope of UPDF Message-ID: <199908132335.QAA25516@scv2.apple.com> Ben, Sandra, see my comments below. Abdallah Qaisi Apple Computer >Item Subject: UPD> re-scope of UPDF > I don't see any much overlap between IPP and UPDF. UPDF is the > description of the printer, and is (should be?) transport independent. > As far as I know, we haven't made IPP a required component of UPDF. > > I agree that we need to re-clarify. IPP is capable of retreiving > facts about the printer, but UPDF expresses not only the facts, but > how they relate to one another. > > If we steer toward Linux and Unix, then we need to drop the "U" from > the comittee name, "U" can stand for Unix too;) Dropping it causes a clash with Adobe PDF. > as it will no longer be universal, and will be of a > much more limited interest to me. > > Regards, > Ben B > > >______________________________ Reply Separator >_________________________________ >Subject: UPD> re-scope of UPDF >Author: sandram-at-boi (sandram@boi.hp.com) at HP-Vancouver,shargw1 >Date: 8/12/99 10:32 AM > > >Hi, > Even though the UPDF spec is coming along - the work is not as >focused >as it could be. I believe there are a couple of reasons for this. One >being ther >e >sheer size of the task. We did an excellent job dividing the job into >sections - > >UI, Localization, etc - but I haven't done a very good job keeping the work >focused on a specific area. > Another issue has been the usefulness of the project itself. Is >UPDF really needed when IPP can retrieve some of the info from >the printer? Can IPP and UPDF complement each other or is there maybe >too much overlap? > > There also has been some thought about steering UPDF towards >a Linux (and other Unix flavors) printing solution and not really a >"Universal" >solution. What do >people think about that? > > If UPDF is limited to Unix, how is it better than today's solution - PPD? I understand that one of the goals for UPDF is to support both Postscript and non-Postscript printers. But while PPD handles PS only, it does it nicely on all platforms not just Unix. My other thought: Is non-Postscript printing on Unix the biggest problem that UPDF is aiming to solve or the easiest problem to solve? If it's the biggest problem, then you may be heading in the right direction as long as you promise adding more platforms later. If on the other hand, you are doing it just for the sake of scoping down the project then I disagree with the direction. Finally, as you know, Apple's Mac OS X at the low level is Unix based so there may be ways we can support your new direction but I cannot say for sure until I see a better definition of the new UPDF proposal. At minimum, the XML portion of a UPDF file could easily be handled on OS X since the new OS already handles XML parsing at the system level. I'm not sure about the optional code modules (the UI and rendering plugins) - whether these binaries will be compatible or not. These are my thoughts at this time. Sorry for not being able to contribute much to this project. But I'm still watching and tracking it with interest. Thanks. Abdallah > > Chuck sent out the DTD vs Schema link. This is something to look >at. Als >o >please check out the UIML and XUL documents for User Interface >specification in >UPDF. > >thanks, >Sandra > >------------------------ >Sandra Matts >Hewlett-Packard >Engineer Scientist >sandram@boi.hp.com >(208) 396-4755 phone >(208) 396-5161 fax > From egglestn at lexmark.com Mon Aug 16 15:56:24 1999 From: egglestn at lexmark.com (egglestn@lexmark.com) Date: Wed May 6 14:05:05 2009 Subject: UPD> test Message-ID: <199908161956.PAA23782@interlock2.lexmark.com> This is just a test -Roger From sandra_matts at am.exch.hp.com Mon Aug 16 16:17:44 1999 From: sandra_matts at am.exch.hp.com (MATTS,SANDRA (HP-Boise,ex1)) Date: Wed May 6 14:05:05 2009 Subject: UPD> re-scope of UPDF Message-ID: Here is the copy of my email. For some reason it never makes it to the UPD email reflector. sandra -----Original Message----- From: MATTS,SANDRA (HP-Boise,ex1) Sent: Monday, August 16, 1999 1:08 PM To: 'upd@pwg.org' Subject: FW: UPD> re-scope of UPDF comments inline. -----Original Message----- From: Abdallah Qaisi [SMTP:qaisi@apple.com] Sent: Friday, August 13, 1999 5:37 PM To: BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com; sandram@boi.hp.com Cc: upd@pwg.org Subject: Re: UPD> re-scope of UPDF Ben, Sandra, see my comments below. Abdallah Qaisi Apple Computer >Item Subject: UPD> re-scope of UPDF > I don't see any much overlap between IPP and UPDF. UPDF is the > description of the printer, and is (should be?) transport independent. > As far as I know, we haven't made IPP a required component of UPDF. [Sandra Matts] It's true we haven't made IPP a requirement - UPDF is supposed to be protocol independent. However, that means we will have to create the xml that can be used with any network protocol and then provide the mapping from UPDF to the different protocols. This will be a large job and will require more time to do. We would have to schedule work time between meetings to get this done. In the interest of making UPDF useful to the largest number of printers - I believe this is the right thing to do. However, it would be helpful if I felt people would contribute input when we do the bi-di work. > > I agree that we need to re-clarify. IPP is capable of retreiving > facts about the printer, but UPDF expresses not only the facts, but > how they relate to one another. > > If we steer toward Linux and Unix, then we need to drop the "U" from > the comittee name, "U" can stand for Unix too;) Dropping it causes a clash with Adobe PDF. > as it will no longer be universal, and will be of a > much more limited interest to me. > > Regards, > Ben B > > [Sandra Matts] stuff deleted. > > There also has been some thought about steering UPDF towards >a Linux (and other Unix flavors) printing solution and not really a >"Universal" >solution. What do >people think about that? > > If UPDF is limited to Unix, how is it better than today's solution - PPD? I understand that one of the goals for UPDF is to support both Postscript and non-Postscript printers. But while PPD handles PS only, it does it nicely on all platforms not just Unix. [Sandra Matts] Good point. If we start scoping down the project in order to get it done, we have to make sure we don't eliminate the features that make it better and that solve the original problem. My other thought: Is non-Postscript printing on Unix the biggest problem that UPDF is aiming to solve or the easiest problem to solve? If it's the biggest problem, then you may be heading in the right direction as long as you promise adding more platforms later. If on the other hand, you are doing it just for the sake of scoping down the project then I disagree with the direction. Finally, as you know, Apple's Mac OS X at the low level is Unix based so there may be ways we can support your new direction but I cannot say for sure until I see a better definition of the new UPDF proposal. At minimum, the XML portion of a UPDF file could easily be handled on OS X since the new OS already handles XML parsing at the system level. I'm not sure about the optional code modules (the UI and rendering plugins) - whether these binaries will be compatible or not. [Sandra Matts] In order to keep it useful for the largest number of OSs - we should do as much specification in XML and only resort to binaries when absolutely needed. These are my thoughts at this time. Sorry for not being able to contribute much to this project. But I'm still watching and tracking it with interest. Thanks. Abdallah > > Chuck sent out the DTD vs Schema link. This is something to look >at. Als >o >please check out the UIML and XUL documents for User Interface >specification in >UPDF. > >thanks, >Sandra > >------------------------ >Sandra Matts >Hewlett-Packard >Engineer Scientist >sandram@boi.hp.com >(208) 396-4755 phone >(208) 396-5161 fax > From egglestn at lexmark.com Mon Aug 16 15:52:48 1999 From: egglestn at lexmark.com (egglestn@lexmark.com) Date: Wed May 6 14:05:05 2009 Subject: No subject Message-ID: <199908162020.QAA01221@pwg.org> This is just a test.... -Roger From sandra_matts at am.exch.hp.com Mon Aug 16 15:07:39 1999 From: sandra_matts at am.exch.hp.com (MATTS,SANDRA (HP-Boise,ex1)) Date: Wed May 6 14:05:05 2009 Subject: FW: UPD> re-scope of UPDF Message-ID: comments inline. -----Original Message----- From: Abdallah Qaisi [SMTP:qaisi@apple.com] Sent: Friday, August 13, 1999 5:37 PM To: BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com; sandram@boi.hp.com Cc: upd@pwg.org Subject: Re: UPD> re-scope of UPDF Ben, Sandra, see my comments below. Abdallah Qaisi Apple Computer >Item Subject: UPD> re-scope of UPDF > I don't see any much overlap between IPP and UPDF. UPDF is the > description of the printer, and is (should be?) transport independent. > As far as I know, we haven't made IPP a required component of UPDF. [Sandra Matts] It's true we haven't made IPP a requirement - UPDF is supposed to be protocol independent. However, that means we will have to create the xml that can be used with any network protocol and then provide the mapping from UPDF to the different protocols. This will be a large job and will require more time to do. We would have to schedule work time between meetings to get this done. In the interest of making UPDF useful to the largest number of printers - I believe this is the right thing to do. However, it would be helpful if I felt people would contribute input when we do the bi-di work. > > I agree that we need to re-clarify. IPP is capable of retreiving > facts about the printer, but UPDF expresses not only the facts, but > how they relate to one another. > > If we steer toward Linux and Unix, then we need to drop the "U" from > the comittee name, "U" can stand for Unix too;) Dropping it causes a clash with Adobe PDF. > as it will no longer be universal, and will be of a > much more limited interest to me. > > Regards, > Ben B > > [Sandra Matts] stuff deleted. > > There also has been some thought about steering UPDF towards >a Linux (and other Unix flavors) printing solution and not really a >"Universal" >solution. What do >people think about that? > > If UPDF is limited to Unix, how is it better than today's solution - PPD? I understand that one of the goals for UPDF is to support both Postscript and non-Postscript printers. But while PPD handles PS only, it does it nicely on all platforms not just Unix. [Sandra Matts] Good point. If we start scoping down the project in order to get it done, we have to make sure we don't eliminate the features that make it better and that solve the original problem. My other thought: Is non-Postscript printing on Unix the biggest problem that UPDF is aiming to solve or the easiest problem to solve? If it's the biggest problem, then you may be heading in the right direction as long as you promise adding more platforms later. If on the other hand, you are doing it just for the sake of scoping down the project then I disagree with the direction. Finally, as you know, Apple's Mac OS X at the low level is Unix based so there may be ways we can support your new direction but I cannot say for sure until I see a better definition of the new UPDF proposal. At minimum, the XML portion of a UPDF file could easily be handled on OS X since the new OS already handles XML parsing at the system level. I'm not sure about the optional code modules (the UI and rendering plugins) - whether these binaries will be compatible or not. [Sandra Matts] In order to keep it useful for the largest number of OSs - we should do as much specification in XML and only resort to binaries when absolutely needed. These are my thoughts at this time. Sorry for not being able to contribute much to this project. But I'm still watching and tracking it with interest. Thanks. Abdallah > > Chuck sent out the DTD vs Schema link. This is something to look >at. Als >o >please check out the UIML and XUL documents for User Interface >specification in >UPDF. > >thanks, >Sandra > >------------------------ >Sandra Matts >Hewlett-Packard >Engineer Scientist >sandram@boi.hp.com >(208) 396-4755 phone >(208) 396-5161 fax > From sandram at boi.hp.com Mon Aug 16 11:24:13 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:05 2009 Subject: FW: UPD> re-scope of UPDF Message-ID: <01BEE7C9.1B8E35A0@hpb13858.boi.hp.com> -----Original Message----- From: Sandra Matts [SMTP:sandram@boi.hp.com] Sent: Sunday, August 15, 1999 12:17 PM To: 'Abdallah Qaisi'; BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com Cc: upd@pwg.org Subject: RE: UPD> re-scope of UPDF comments inline. -----Original Message----- From: Abdallah Qaisi [SMTP:qaisi@apple.com] Sent: Friday, August 13, 1999 5:37 PM To: BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com; sandram@boi.hp.com Cc: upd@pwg.org Subject: Re: UPD> re-scope of UPDF Ben, Sandra, see my comments below. Abdallah Qaisi Apple Computer >Item Subject: UPD> re-scope of UPDF > I don't see any much overlap between IPP and UPDF. UPDF is the > description of the printer, and is (should be?) transport independent. > As far as I know, we haven't made IPP a required component of UPDF. [Sandra Matts] It's true we haven't made IPP a requirement - UPDF is supposed to be protocol independent. However, that means we will have to create the xml that can be used with any network protocol and then provide the mapping from UPDF to the different protocols. This will be a large job and will require more time to do. We would have to schedule work time between meetings to get this done. In the interest of making UPDF useful to the largest number of printers - I believe this is the right thing to do. However, it would be helpful if I felt people would contribute input when we do the bi-di work. > > I agree that we need to re-clarify. IPP is capable of retreiving > facts about the printer, but UPDF expresses not only the facts, but > how they relate to one another. > > If we steer toward Linux and Unix, then we need to drop the "U" from > the comittee name, "U" can stand for Unix too;) Dropping it causes a clash with Adobe PDF. > as it will no longer be universal, and will be of a > much more limited interest to me. > > Regards, > Ben B > > [Sandra Matts] stuff deleted. > > There also has been some thought about steering UPDF towards >a Linux (and other Unix flavors) printing solution and not really a >"Universal" >solution. What do >people think about that? > > If UPDF is limited to Unix, how is it better than today's solution - PPD? I understand that one of the goals for UPDF is to support both Postscript and non-Postscript printers. But while PPD handles PS only, it does it nicely on all platforms not just Unix. [Sandra Matts] Good point. If we start scoping down the project in order to get it done, we have to make sure we don't eliminate the features that make it better and that solve the original problem. My other thought: Is non-Postscript printing on Unix the biggest problem that UPDF is aiming to solve or the easiest problem to solve? If it's the biggest problem, then you may be heading in the right direction as long as you promise adding more platforms later. If on the other hand, you are doing it just for the sake of scoping down the project then I disagree with the direction. Finally, as you know, Apple's Mac OS X at the low level is Unix based so there may be ways we can support your new direction but I cannot say for sure until I see a better definition of the new UPDF proposal. At minimum, the XML portion of a UPDF file could easily be handled on OS X since the new OS already handles XML parsing at the system level. I'm not sure about the optional code modules (the UI and rendering plugins) - whether these binaries will be compatible or not. [Sandra Matts] In order to keep it useful for the largest number of OSs - we should do as much specification in XML and only resort to binaries when absolutely needed. These are my thoughts at this time. Sorry for not being able to contribute much to this project. But I'm still watching and tracking it with interest. Thanks. Abdallah > > Chuck sent out the DTD vs Schema link. This is something to look >at. Als >o >please check out the UIML and XUL documents for User Interface >specification in >UPDF. > >thanks, >Sandra > >------------------------ >Sandra Matts >Hewlett-Packard >Engineer Scientist >sandram@boi.hp.com >(208) 396-4755 phone >(208) 396-5161 fax > From egglestn at lexmark.com Tue Aug 17 08:54:24 1999 From: egglestn at lexmark.com (egglestn@lexmark.com) Date: Wed May 6 14:05:05 2009 Subject: UPD> Test Message-ID: <199908171254.IAA05711@interlock2.lexmark.com> This is just a test.... -Roger From egglestn at lexmark.com Wed Aug 18 08:50:42 1999 From: egglestn at lexmark.com (egglestn@lexmark.com) Date: Wed May 6 14:05:05 2009 Subject: UPD> Test Message-ID: <199908181251.IAA08605@interlock2.lexmark.com> This is just a test -Roger From egglestn at lexmark.com Wed Aug 18 10:49:40 1999 From: egglestn at lexmark.com (egglestn@lexmark.com) Date: Wed May 6 14:05:05 2009 Subject: UPD> test Message-ID: <199908181450.KAA06298@interlock2.lexmark.com> Testing...please ignore -Roger From sandram at boi.hp.com Fri Aug 20 10:33:28 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:05 2009 Subject: UPD> test - ignore Message-ID: <01BEEAE6.ADD8D940@hpb13858.boi.hp.com> My email is bouncing - just testing. ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandram at boi.hp.com Sun Aug 15 14:16:50 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:05 2009 Subject: UPD> re-scope of UPDF Message-ID: <01BEE718.0E823C00@hpb13858.boi.hp.com> comments inline. -----Original Message----- From: Abdallah Qaisi [SMTP:qaisi@apple.com] Sent: Friday, August 13, 1999 5:37 PM To: BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com; sandram@boi.hp.com Cc: upd@pwg.org Subject: Re: UPD> re-scope of UPDF Ben, Sandra, see my comments below. Abdallah Qaisi Apple Computer >Item Subject: UPD> re-scope of UPDF > I don't see any much overlap between IPP and UPDF. UPDF is the > description of the printer, and is (should be?) transport independent. > As far as I know, we haven't made IPP a required component of UPDF. [Sandra Matts] It's true we haven't made IPP a requirement - UPDF is supposed to be protocol independent. However, that means we will have to create the xml that can be used with any network protocol and then provide the mapping from UPDF to the different protocols. This will be a large job and will require more time to do. We would have to schedule work time between meetings to get this done. In the interest of making UPDF useful to the largest number of printers - I believe this is the right thing to do. However, it would be helpful if I felt people would contribute input when we do the bi-di work. > > I agree that we need to re-clarify. IPP is capable of retreiving > facts about the printer, but UPDF expresses not only the facts, but > how they relate to one another. > > If we steer toward Linux and Unix, then we need to drop the "U" from > the comittee name, "U" can stand for Unix too;) Dropping it causes a clash with Adobe PDF. > as it will no longer be universal, and will be of a > much more limited interest to me. > > Regards, > Ben B > > [Sandra Matts] stuff deleted. > > There also has been some thought about steering UPDF towards >a Linux (and other Unix flavors) printing solution and not really a >"Universal" >solution. What do >people think about that? > > If UPDF is limited to Unix, how is it better than today's solution - PPD? I understand that one of the goals for UPDF is to support both Postscript and non-Postscript printers. But while PPD handles PS only, it does it nicely on all platforms not just Unix. [Sandra Matts] Good point. If we start scoping down the project in order to get it done, we have to make sure we don't eliminate the features that make it better and that solve the original problem. My other thought: Is non-Postscript printing on Unix the biggest problem that UPDF is aiming to solve or the easiest problem to solve? If it's the biggest problem, then you may be heading in the right direction as long as you promise adding more platforms later. If on the other hand, you are doing it just for the sake of scoping down the project then I disagree with the direction. Finally, as you know, Apple's Mac OS X at the low level is Unix based so there may be ways we can support your new direction but I cannot say for sure until I see a better definition of the new UPDF proposal. At minimum, the XML portion of a UPDF file could easily be handled on OS X since the new OS already handles XML parsing at the system level. I'm not sure about the optional code modules (the UI and rendering plugins) - whether these binaries will be compatible or not. [Sandra Matts] In order to keep it useful for the largest number of OSs - we should do as much specification in XML and only resort to binaries when absolutely needed. These are my thoughts at this time. Sorry for not being able to contribute much to this project. But I'm still watching and tracking it with interest. Thanks. Abdallah > > Chuck sent out the DTD vs Schema link. This is something to look >at. Als >o >please check out the UIML and XUL documents for User Interface >specification in >UPDF. > >thanks, >Sandra > >------------------------ >Sandra Matts >Hewlett-Packard >Engineer Scientist >sandram@boi.hp.com >(208) 396-4755 phone >(208) 396-5161 fax > From sandram at boi.hp.com Mon Aug 30 10:46:17 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:05 2009 Subject: UPD> phone conf tomorrow Message-ID: <01BEF2C4.B1135AA0@hpb13858.boi.hp.com> Hi, At the last meeting we discussed having a phone conference to discuss UI requirements and specifics. The phone number for our phone conference is 612-315-6802 The access code is 058459494 I will activate the number on August 31 from 10-12 Pacific time. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From charles.a.adams at exgate.tek.com Mon Aug 30 13:18:32 1999 From: charles.a.adams at exgate.tek.com (charles.a.adams@exgate.tek.com) Date: Wed May 6 14:05:05 2009 Subject: UPD> UPDF User Interface Requirements Document Message-ID: <6B57A2A3212BD2119C2600805F6F14130278751A@us-wv-m11.wv.tek.com> Folks, Sorry things were a bit hectic last week. So the requirements document has not gotten the work it deserves. But I thought we might discuss it (such that it is) tomorrow and then I can put more work into it this week. <> Charles "Chuck" Adams adamsc@pogo.wv.tek.com Tektronix, Inc. Color Printing and Imaging Division -------------- next part -------------- A non-text attachment was scrubbed... Name: updf_ui_reqs.doc Type: application/msword Size: 22528 bytes Desc: not available Url : http://www.pwg.org/archives/upd/attachments/19990830/312c06d3/updf_ui_reqs-0001.doc From jkm at underscore.com Mon Aug 30 13:37:09 1999 From: jkm at underscore.com (Jay Martin) Date: Wed May 6 14:05:05 2009 Subject: UPD> UPDF User Interface Requirements Document References: <6B57A2A3212BD2119C2600805F6F14130278751A@us-wv-m11.wv.tek.com> Message-ID: <37CAC145.269BBC0C@underscore.com> How does UPDF differ/compare with Adobe's PPD files? On the surface (to the uninformed reader) this effort appears to simply replace what exists in PPD files. Surely, I'm missing something here, so any enlightenment would be appreciated. ...jay From charles.a.adams at exgate.tek.com Mon Aug 30 14:54:32 1999 From: charles.a.adams at exgate.tek.com (charles.a.adams@exgate.tek.com) Date: Wed May 6 14:05:05 2009 Subject: UPD> UPDF User Interface Requirements Document Message-ID: <6B57A2A3212BD2119C2600805F6F14130278751E@us-wv-m11.wv.tek.com> The requirements are a super-set of PPD's functionality. Specifically, PPD's have a very limited UI capability. In addition, since UPDF is XML-based I believe we will be able to take advantage of the development of UI tools being done for XML. Chuck Adams > -----Original Message----- > From: Jay Martin [SMTP:jkm@underscore.com] > Sent: Monday, August 30, 1999 10:37 AM > To: Adams, Charles A > Cc: upd@pwg.org > Subject: Re: UPD> UPDF User Interface Requirements Document > > How does UPDF differ/compare with Adobe's PPD files? > On the surface (to the uninformed reader) this effort > appears to simply replace what exists in PPD files. > Surely, I'm missing something here, so any enlightenment > would be appreciated. > > ...jay From sandra_matts at am.exch.hp.com Tue Aug 31 13:04:40 1999 From: sandra_matts at am.exch.hp.com (MATTS,SANDRA (HP-Boise,ex1)) Date: Wed May 6 14:05:05 2009 Subject: UPD> phone conf Message-ID: Hi, Is anybody joining the conf today? Sandra Sandra Matts Engineer Scientist Hewlett-Packard sandram@boi.hp.com (208) 396-4755 phone From charles.a.adams at exgate.tek.com Tue Sep 7 16:25:39 1999 From: charles.a.adams at exgate.tek.com (charles.a.adams@exgate.tek.com) Date: Wed May 6 14:05:05 2009 Subject: UPD> UPDF User Interface Requirements Document Update Message-ID: <6B57A2A3212BD2119C2600805F6F141302787566@us-wv-m11.wv.tek.com> Folks, The attached update is based on the teleconference feedback. Hope this captured all the issues raised. Charles "Chuck" Adams adamsc@pogo.wv.tek.com Tektronix, Inc. <> -------------- next part -------------- A non-text attachment was scrubbed... Name: updf_ui_reqs.doc Type: application/msword Size: 38912 bytes Desc: not available Url : http://www.pwg.org/archives/upd/attachments/19990907/a876869f/updf_ui_reqs-0001.doc From sandram at boi.hp.com Mon Sep 13 12:03:48 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:05 2009 Subject: UPD> phone conf tomorrow Message-ID: <01BEFDCF.4653B0A0@hpb13858.boi.hp.com> Hi, At the last meeting we discussed having a phone conference to discuss UI requirements and specifics. The phone number for our phone conference is 612-315-6802 The access code is 058459494 I will activate the number on September 14 (Tuesday) from 10-11 Pacific time. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From mwu at kodak.com Tue Sep 14 13:53:50 1999 From: mwu at kodak.com (mwu@kodak.com) Date: Wed May 6 14:05:05 2009 Subject: UPD> IPP> ANNOUNCEMENT: Common UNIX Printing System 1.0 Beta 9 Message-ID: <852567EC.0061DA06.00@knotes.kodak.com> From: Michael Wu FYI ---------------------- Forwarded by Michael Wu/414061/OI/EKC on 09/14/99 01:56 PM --------------------------- Michael Sweet on 09/03/99 05:30:31 PM To: IPP Mailing List cc: (bcc: Michael Wu/414061/OI/EKC) Subject: IPP> ANNOUNCEMENT: Common UNIX Printing System 1.0 Beta 9 -------------- next part -------------- The 8th beta release of the Common UNIX Printing System ("CUPS") is now available for download from the CUPS web site at: http://www.cups.org Binaries for several platforms are also available! The Common UNIX Printing System provides a portable printing layer for UNIX? operating systems. It has been developed by Easy Software Products to promote a standard printing solution for all UNIX vendors and users. CUPS provides the System V and Berkeley command-line interfaces. CUPS uses the Internet Printing Protocol (IETF-IPP) as the basis for managing print jobs and queues. The Line Printer Daemon (LPD, RFC1179), Server Message Block (SMB), and AppSocket protocols are also supported with reduced functionality. CUPS adds network printer browsing and PostScript Printer Description ("PPD")-based printing options to support real world applications under UNIX. CUPS also includes a customized version of GNU GhostScript (currently based off GNU GhostScript 4.03) and an image file RIP that can be used to support non-PostScript printers. Sample drivers are provided for HP DeskJet and LaserJet printers. Drivers for over 1500 printers are available in our ESP Print Pro software. CUPS is licensed under the GNU General Public License. Please contact Easy Software Products for commercial support and "binary distribution" rights. Changes since the last release include: - The IPP backend wasn't appending a 0-length chunk when needed. - You couldn't add a printer if there was a remote class of the same name, and visa-versa. - The setgid() and setuid() calls were backwards in the scheduler. - The scheduler didn't always log printer status messages; this should be fixed now. - Filter creation and death are now logged (debug level only.) This should better aid filter debugging. - The image library code was using lseek() after rewind() to ensure that the file descriptor was at the beginning of the file. This was needed for the TIFF image handler but broke the rest of the file formats. Moved the lseek() to the TIFF image handler... -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike@easysw.com Printing Software for UNIX http://www.easysw.com From sandram at boi.hp.com Tue Sep 21 20:30:06 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:05 2009 Subject: UPD> investigation results of UIML and XUL Message-ID: <01BF045F.54B4C300@hpb13858.boi.hp.com> Hi, At the last phone conference it was decided to see if either UIML or XUL is a good fit for UPDF User Interface definition. Mike Yeung from Canon wrote up results of his investigation of UIML and I did the XUL. I've copied both of these to the ftp site. ftp://ftp.pwg.org/pub/upd/Archive/1999/ XULstudy.doc and UserInterfaceMarkupLanguagestudy.doc are the files. Please download for discussion on Friday's UPDF meeting. I will try to bring hard copies to the meeting if needed. thanks, Sandra ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From sandra_matts at am.exch.hp.com Mon Oct 4 13:40:30 1999 From: sandra_matts at am.exch.hp.com (MATTS,SANDRA (HP-Boise,ex1)) Date: Wed May 6 14:05:05 2009 Subject: UPD> UPDF phone conf. Message-ID: Hi All, We are scheduled to have a UPDF phone conference tomorow - Tuesday from 10-11am Pacific tme. We will discuss the last UPDF meetings and any action items from that meeting. Phone number is 612-315-6802 access code is 058459494 I do have minutes done from the last meeting. I just have to copy them to the ftp site. I will do that today. Sandra Matts Sandra Matts Engineer Scientist Hewlett-Packard sandram@boi.hp.com (208) 396-4755 phone From charles.a.adams at exgate.tek.com Tue Oct 5 14:03:50 1999 From: charles.a.adams at exgate.tek.com (charles.a.adams@exgate.tek.com) Date: Wed May 6 14:05:05 2009 Subject: UPD> Tools for XML and XSL Message-ID: <6B57A2A3212BD2119C2600805F6F1413027875EE@us-wv-m11.wv.tek.com> Folks, Here is a not so recent article on tools for XML. Several of them also handle CSS and XSL. http://www.internetwk.com/lead/lead081099.htm Charles "Chuck" Adams adamsc@pogo.wv.tek.com Tektronix, Inc. From sandram at boi.hp.com Tue Oct 19 11:12:39 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:05 2009 Subject: UPD> phone conference today Message-ID: <01BF1A12.A19519E0@hpb13858.boi.hp.com> Hi All, Sorry for late reminder - but we are scheduled for a phone conference today at 10am Pacific time. We are supposed to discuss style sheets and how they fit in with the UPDF UI XML. The phone number for our phone conference is 612-315-6802 The access code is 058459494 Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax From nschade at xionics.com Tue Oct 19 07:27:01 1999 From: nschade at xionics.com (Norbert Schade) Date: Wed May 6 14:05:05 2009 Subject: UPD> Arbortext contact Message-ID: <001e01bf1a24$dd6cc0a0$c31343ce@gca-2.xionics.com> All, I contacted Arbortext today. They will send me a sample package for evaluation very soon. It will mainly include info about the ADEPT series. I will keep you informed about it. The homepage is just arbortext.com. Norbert From BEN_BREZINSKI at HP-Vancouver-om1.om.hp.com Tue Oct 19 14:16:43 1999 From: BEN_BREZINSKI at HP-Vancouver-om1.om.hp.com (BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com) Date: Wed May 6 14:05:05 2009 Subject: UPD> Error in line 658 using XMLPro Message-ID: I have found out that this error message is referring to a line number in the DTD. By deleting the offending lines I was able to get clj4500.xml to load. I have not found the specific errors, but will keep you posted. Regards, Ben Brezinski Hewlett Packard From BEN_BREZINSKI at HP-Vancouver-om1.om.hp.com Tue Oct 19 14:26:20 1999 From: BEN_BREZINSKI at HP-Vancouver-om1.om.hp.com (BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com) Date: Wed May 6 14:05:05 2009 Subject: UPD> More info on "Error in Line 658" using XMLPro Message-ID: The error message "whitespace expected" is literal. In the offending line, there really needs to be a whitespace between EXPUNITS and the '('. There is a similar mistake further up aroune line 258. Regards, Ben Brezinski Hewlett Packard From sandram at boi.hp.com Thu Oct 21 11:58:37 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:05 2009 Subject: UPD> current dtd and xml file Message-ID: <01BF1BAA.D959E240@hpb13858.boi.hp.com> Hi All, I believe people are using an older dtd and color laserjet 4500 updf file. I'm attaching the version I'm using currently. I just loaded it with the shareware version of XML Pro and it seemed to work. Sandra Matts ------------------------ Sandra Matts Hewlett-Packard Engineer Scientist sandram@boi.hp.com (208) 396-4755 phone (208) 396-5161 fax begin 600 CLJ4500.xml M/#]X;6P@=F5R2!B87-I8R!54$1&(&9I M;&4@=VET:"!J=7-T('1H92!M:6YI;75M(')E<75I7,@551&+3@N#0H-"B @("!,;V-A;&5S('-U M<'!O2!T:&ES(%501$8@9FEL92X-"CPA+2T@+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+B M+3X-"B @(" \3&]C86QE3&ES=#X-"B @(" @(" @/$QO8V%L92!, M;V-A;&5)9#TB96Y?054B/CPO3&]C86QE/@T*(" @(" @(" \3&]C86QE($QO M8V%L94ED/2)E;E]'0B(^/"],;V-A;&4^#0H@(" @(" @(#Q,;V-A;&4@3&]C M86QE260](F5N7U53(CX\+TQO8V%L93X-"B @(" @(" @/$QO8V%L92!,;V-A M;&5)9#TB9&%?1$LB/CPO3&]C86QE/@T*(" @(" @(" \0W5S=&]M3&]C86QE M#0H@(" @(" @(" @("!#=7-T;VU,;V-A;&5)9#TB96Y?54LB/CPO0W5S=&]M M3&]C86QE/@T*(" @(" @(" \0W5S=&]M3&]C86QE#0H@(" @(" @(" @("!# M=7-T;VU,;V-A;&5)9#TB86%?0D(B/CPO0W5S=&]M3&]C86QE/@T*(" @(#PO M3&]C86QE3&ES=#X-"@T*(" @(#Q&:6QE3F%M93Y#3$HT-3 P+GAM;#PO1FEL M94YA;64^#0H-"B @(" \0W5S=&]M1&5V:6-E0V%P5&%G7!E-#(B+SX-"B @(" \+T-U M7-I8V%L/@T*(" @(" @(" @(" @(" @(#Q%;F=I M;F4^/"]%;F=I;F4^#0H@(" @(" @(" @(" @(" @/%)!32!F4D%-/2)44E5% M(CX-"B @(" @(" @(" @(" @(" @(" @/%)!32Y);G1EF5+ M8CTB-# Y-B(^/"]204TN26YT97)N86P^#0H@(" @(" @(" @(" @(" @/"]2 M04T^#0H@(" @(" @(" @(" @(" @/%)/32!F4D]-/2)&04Q312(^/"]23TT^ M#0H@(" @(" @(" @(" @(" @/$-O;&]R('1#;VQOF50=#TB,3 B( T*(" @(" @(" @(" @(" @(" @("!$969A=6QT1F]N M=$1"0U,](DYO;F4B/D-O=7)I97(-"B @(" @(" @(" @(" @(" \+T1E9F%U M;'1&;VYT/@T*(" @(" @(" @(" @(" @(#Q);G1EF4-"B @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q524-O;G1R;VP^#0H@ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @/$QIF4] M(E12544B#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @2&5L<%1E>'0](DAE;'!-92(-"B @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @("!3:&]R=&-U=$ME>3TB>2(O/DQA>6]U= T*(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @/%5)0V]N=')O;#X- M"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" \4F%D M:6]"=71T;VY'3TB4"(-"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @($-O;6UA;F0](F-M9"(O/@T*(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" \4F%D:6]"=71T;VX- M"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(%5)3&%B96P](DQA;F1S8V%P92(-"B @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(%-H;W)T8W5T2V5Y/2),(@T* M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @0V]M;6%N9#TB8VUD(B\^#0H@(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @/"]2861I;T)U='1O;D=R;W5P/@T*(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @/"]524-O;G1R;VP^#0H@(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" \54E#;VYT#X\+T-H96-K0F]X/@T*(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @/"]524-O;G1R;VP^#0H@(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(#PO54E&96%T=7)E/@T*(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" \54E&96%T=7)E/@T*(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" \54E!='1R:6)U=&5S#0H@(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @54E$:7-P;&%Y3F%M93TB4&%P97(@ M4V]UF4](E12544B#0H@(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @2&5L<%1E>'0](DAE;'!-92(-"B @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @("!3:&]R=&-U=$ME>3TB M3R(O/E!A<&5R4V]U3TB9"(O/D1U<&QE> T*(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" \54E#;VYT'0](DAE;'!-92(O/DUE9&EA#0H@(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(#Q524-O;G1R;VP^#0H@(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" \3&ES=#X-"B @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" \271E;4EN3&ES= T*(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @("!524QA M8F5L/2)0;&%I;B(-"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @0V]M;6%N9#TB8VUD(B\^#0H@(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" \+TQIF4](D1-4$%015)?3$545$52(B\^#0H@(" @(" @(" @(" @ M(" @(" @(" @(" @(" @/"]$4$QO8V%L93X-"B @(" @(" @(" @(" @(" @ M(" @(" @(" @(" \1%!,;V-A;&4-"B @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @3&]C86QE260](F1A7T1+(CX-"B @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @/$104PT*(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @1&5F875L=%!A<&5R4VEZ93TB1$U005!%4E]!-"(O/@T* M(" @(" @(" @(" @(" @(" @(" @(" @(" @(#PO1%!,;V-A;&4^#0H@(" @ M(" @(" @(" @(" @(" @(" @(" @(" @/$103&]C86QE#0H@(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @($QO8V%L94ED/2)E;E]'0B(^#0H@(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q$4%,-"B @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @($1E9F%U;'1087!EF4](D1- M4$%015)?030B+SX-"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M/$104PT*(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @1&5F M875L=%!A<&5R4VEZ93TB1$U005!%4E],151415(B+SX-"B @(" @(" @(" @ M(" @(" @(" @(" @(" @(" \+T103&]C86QE/@T*(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(#Q$4$-U#TB-C$R(B!Y/2(W.3(B+SX- M"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @/%!A<&5R+D%R96$N M#TB-3DU(B!Y/2(X-#(B+SX-"B @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @/%!A<&5R+D%R96$NF5-;3$P('@](C$Q,3$B('D](C$Q,3$B+SX- M"B @(" @(" @(" @(" @(" @(" @(" @(" @(" \+U!A<&5R+D%R96$^#0H@ M(" @(" @(" @(" @(" @(" @(" @(" \+U!A<&5R/@T*(" @(" @(" @(" @ M(" @(" @(" @(" @/%!A<&5R(&1M<&%P97)S:7IE/2)$35!!4$527TQ%1T%, M(CY,96=A; T*(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q087!EF5-;3$P('@](C$Q,3$B('D](C$Q,3$B+SX- M"B @(" @(" @(" @(" @(" @(" @(" @(" @(" \+U!A<&5R+D%R96$^#0H@ M(" @(" @(" @(" @(" @(" @(" @(" \+U!A<&5R/@T*#0H@(" @(" @(" @ M(" @(" @(" @(" @(" \4&%P97(@9&UP87!EF4](D1-4$%015)?15A% M0U54259%(CY%>&5C=71I=F4-"B @(" @(" @(" @(" @(" @(" @(" @(" @ M(" \4&%P97(N07)E83X-"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @/%!A<&5R+D%R96$N<'1!#TB-3(R(B!Y/2(W-38B+SX- M"B @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @/%!A<&5R+D%R96$N MF5-;3$P('@](C$Q,3$B('D] M(C$Q,3$B+SX-"B @(" @(" @(" @(" @(" @(" @(" @(" @(" \+U!A<&5R M+D%R96$^#0H@(" @(" @(" @(" @(" @(" @(" @(" \+U!A<&5R/@T*#0H@ M(" @(" @(" @(" @(" @(" @(" @(" \4&%P97(@9&UP87!EF4](D1- M4$%015)?034B/D$U#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @/%!A M<&5R+D%R96$^#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q0 M87!E&5L('@](C0R,"(@>3TB-3DU(B\^#0H@(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q087!E&5L#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @;&5F=#TB,3(N,# B('1O<#TB,3(N,3(B(')I9VAT/2(U,#,N.#@B M(&)O='1O;3TB-S$U+CDR(B\^#0H@(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(#Q087!E#TB,3$Q,2(@>3TB,3$Q M,2(O/@T*(" @(" @(" @(" @(" @(" @(" @(" @(" @(#PO4&%P97(N07)E M83X-"B @(" @(" @(" @(" @(" @(" @(" @(#PO4&%P97(^#0H-"B @(" @ M(" @(" @(" @(" @(" @(" @(#Q087!E&5L('@](C0Y.2(@>3TB-S Y M(B\^#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q087!E&5L('@](C(Y M-R(@>3TB-C@T(B\^#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(#Q087!E#TB-#4Y(B!Y/2(V-#DB+SX-"B @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @/%!A<&5R+D%R96$NF5-;3$P('@](C$Q,3$B('D](C$Q,3$B+SX-"B @(" @(" @(" @(" @ M(" @(" @(" @(" @(" \+U!A<&5R+D%R96$^#0H@(" @(" @(" @(" @(" @ M(" @(" @(" \+U!A<&5R/@T*#0H@(" @(" @(" @(" @(" @(" @(" @(" \ M4&%P97(@9&UP87!EF4](D1-4$%015)?14Y67T1,(CY%;G9E;&]P92!$ M3 T*(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q087!E&5L#0H@ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @;&5F=#TB M,3(N,# B('1O<#TB,3(N,3(B(')I9VAT/2(R.3DN-C0B(&)O='1O;3TB-C$Q M+C0R(B\^#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(#Q087!E M#TB,3$Q,2(@>3TB,3$Q,2(O/@T*(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(#PO4&%P97(N07)E83X-"B @(" @(" @ M(" @(" @(" @(" @(" @(#PO4&%P97(^#0H-"B @(" @(" @(" @(" @(" @ M(" @(" @(#Q087!E&5L#0H@(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @;&5F=#TB,3(N,# B('1O<#TB,3(N,3(B(')I9VAT/2(R M-C8N-S8B(&)O='1O;3TB-3(W+CDP(B\^#0H@(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(#Q087!E#TB,3$Q,2(@ M>3TB,3$Q,2(O/@T*(" @(" @(" @(" @(" @(" @(" @(" @(" @(#PO4&%P M97(N07)E83X-"B @(" @(" @(" @(" @(" @(" @(" @(#PO4&%P97(^#0H- M"B @(" @(" @(" @(" @(" @(" @/"]005!%4E,^#0H-"B @(" @(" @(" @ M(" @(" @(" @/"$M+2 N+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN("TM/@T*(" @(" @(" @ M(" @(" @(" @(" \(2TM(%5S97(@1&5F:6YE(%!A<&5R($EN9F\@(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @+2T^#0H@(" @(" @ M(" @(" @(" @(" @(#PA+2T@+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+B M+3X-"B @(" @ M(" @(" @(" @(" @(" @/%5$4$E.1D]3(&951%!);F9O/2)&04Q312(^#0H@ M(" @(" @(" @(" @(" @(" @(#PO541024Y&3U,^#0H@(" @(" @(" @(" @ M(" @(" @(#PA+2T@+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+B M+3X-"B @(" @(" @(" @ M(" @(" @(" @/"$M+2!-961I82!S:&]U;&0@8F4@82!G2(^5')A;G-P87)E;F-Y/"]-961I83X-"B @(" @(" @(" @(" @ M(" @(" @(" @(#Q-961I82 -"B @(" @(" @(" @(" @(" @(" @(" @(" @ M("!-961I84ED/2),86)E;',B/DQA8F5L#TB3TXB M/CPO1'5P;&5X/@T*(" @(" @(" @(" @(" @(" @(" \0F]O:VQE="!T0F]O M:VQE=#TB3T9&(B\^#0H@(" @(" @(" @(" @(" @(" @(#Q#96YT97)&;VQD M06YD4W1A<&QE/CPO0V5N=&5R1F]L9$%N9%-T87!L93X-"B @(" @(" @(" @ M(" @(" @(" @/%)E=F5R#X-"B @(" @(" @(" @ M(" @(" @(" @/%-T87!L93X\+U-T87!L93X-"B @(" @(" @(" @(" @(" @ M(" @/$9/3$13/CPO1D],1%,^#0H@(" @(" @(" @(" @(" @(" @(#Q(;VQE M4'5N8V@^/"](;VQE4'5N8V@^#0H@(" @(" @(" @(" @(" @/"]&24Y)4TA) M3D=3/@T*(" @(" @(" @(" @(" @(#Q#;VQO7-T96US+"!);F,@(" @(" @(" @(" @(" @(" @(" @(" M+3X-"CPA+2T@ M4')I;G1EF5?96YU;2 -"@DG*"!&04Q317P-"@E$35!!4$527TQ% M5%1%4GP-"@E$35!!4$527TQ%5%1%4E--04Q,? T*"41-4$%015)?5$%"3$]) M1'P-"@E$35!!4$527TQ%1$=%4GP-"@E$35!!4$527TQ%1T%,? T*"41-4$%0 M15)?4U1!5$5-14Y4? T*"41-4$%015)?15A%0U54259%? T*"41-4$%015)? M03-\#0H)1$U005!%4E]!-'P-"@E$35!!4$527T$T4TU!3$Q\#0H)1$U005!% M4E]!-7P-"@E$35!!4$527T(T? T*"41-4$%015)?0C5\#0H)1$U005!%4E]& M3TQ)3WP-"@E$35!!4$527U%505)43WP-"@E$35!!4$527S$P6#$T? T*"41- M4$%015)?,3%8,3=\#0H)1$U005!%4E].3U1%? T*"41-4$%015)?14Y67SE\ M#0H)1$U005!%4E]%3E9?,3!\#0H)1$U005!%4E]%3E9?,3%\#0H)1$U005!% M4E]%3E9?,3)\#0H)1$U005!%4E]%3E9?,31\#0H)1$U005!%4E]#4TA%151\ M#0H)1$U005!%4E]$4TA%151\#0H)1$U005!%4E]%4TA%151\#0H)1$U005!% M4E]%3E9?1$Q\#0H)1$U005!%4E]%3E9?0S5\#0H)1$U005!%4E]%3E9?0S-\ M#0H)1$U005!%4E]%3E9?0S1\#0H)1$U005!%4E]%3E9?0S9\#0H)1$U005!% M4E]%3E9?0S8U? T*"41-4$%015)?14Y67T(T? T*"41-4$%015)?14Y67T(U M? T*"41-4$%015)?14Y67T(V? T*"41-4$%015)?14Y67TE404Q9? T*"41- M4$%015)?14Y67TU/3D%20TA\#0H)1$U005!%4E]%3E9?4$524T].04Q\#0H) M1$U005!%4E]&04Y&3TQ$7U53? T*"41-4$%015)?1D%.1D],1%]35$1?1T52 M34%.? T*"41-4$%015)?1D%.1D],1%],1TQ?1T5234%.? T*"41-4$%015)? M25-/7T(T? T*"41-4$%015)?2D%004Y%4T5?4$]35$-!4D1\#0H)1$U005!% M4E\Y6#$Q? T*"41-4$%015)?,3!8,3%\#0H)1$U005!%4E\Q-5@Q,7P-"@E$ M35!!4$527T5.5E])3E9)5$5\#0H)1$U005!%4E]215-%4E9%1%\T.'P-"@E$ M35!!4$527U)%4T525D5$7S0Y? T*"41-4$%015)?3$545$527T585%)!? T* M"41-4$%015)?3$5'04Q?15A44D%\#0H)1$U005!%4E]404),3TE$7T585%)! M? T*"41-4$%015)?031?15A44D%\#0H)1$U005!%4E],151415)?5%)!3E-6 M15)317P-"@E$35!!4$527T$T7U1204Y35D524T5\#0H)1$U005!%4E],1514 M15)?15A44D%?5%)!3E-615)317P-"@E$35!!4$527T%?4$Q54WP-"@E$35!! M4$527T)?4$Q54WP-"@E$35!!4$527TQ%5%1%4E]03%53? T*"41-4$%015)? M031?4$Q54WP-"@E$35!!4$527T$U7U1204Y35D524T5\#0H)1$U005!%4E]" M-5]44D%.4U9%4E-%? T*"41-4$%015)?03-?15A44D%\#0H)1$U005!%4E]! M-5]%6%1207P-"@E$35!!4$527T(U7T585%)!? T*"41-4$%015)?03)\#0H) M1$U005!%4E]!,U]44D%.4U9%4E-%? T*"41-4$%015)?03-?15A44D%?5%)! M3E-615)317P-"@E$35!!4$527U5315)\#0H)1$U005!%4E]*05!!3D5315]% M3E9?631\#0H)1$U005!%4E]*05!!3D5315]%3E9?63)\#0H)1$U005!%4E]* M05!!3D5315]%3E9?2S(I)SX-"CPA14Y42519("4@9&UP87!EF5?871T MF5?96YU;3L@(D9!3%-% M(B<^#0H-"CPA14Y42519("4@9&UP7!E("A.3TY% M?$9L87-H?$A$1"D@(DY/3D4B( T*"0D)4W1OF4@3DU43TM%3B B M,"(^#0H)/"$M+2 N+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BTM/@T*"3PA+2T@3U,O2$]3 M5" @0V]L;W(@36%N86=E;65N="]296YD97)I;F<@(" @(" @(" @(" @(" @ M(" @(" @(" @(" M+3X-"@D\(2TM("XN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+2T^#0H) M/"%%3$5-14Y4(%!L871F;W)M("A-;V1U;&5.86UEF%T:6]N(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" M+3X- M"@D\(2TM("XN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+2T^#0H)/"%%3$5-14Y4($QO8V%L M:7IA=&EO;B!%35!462 ^#0H)/"$M+2 N+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BTM/@T* M"3PA+2T@1VQO8F%L(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @(" M+3X-"@D\(2TM("XN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+2T^#0H@(" @/"%%3$5-14Y4($=L;V)A;" H57-E'0@ M0T1!5$$@(TE-4$Q)140-"B @(" @(" @(" @(%-H;W)T8W5T2V5Y($-$051! M("-)35!,245$/B @#0H@(" @(" @(#PA14Q%345.5"!524-O;G1R;VP@*$)U M='1O;GQ2861I;T)U='1O;D=R;W5P?$-H96-K0F]X?$QI"P@(" @(" @ M(" M+3X-"B @(" @(" @/"$M+2!38W)O;&Q"87(L(%-P:6Y#;VYT2!#1$%402 C24U03$E%1 T*(" @(" @(" @(" @ M(" @($-O;6UA;F0@0T1!5$$@(TE-4$Q)140^#0H@(" @(" @(#PA14Q%345. M5"!#:&5C:T)O>"!%35!463X-"B @(" @(" @/"%%3$5-14Y4($QI4UA;F%G92 -"B @(" @(" @ M(" @(%!R:6YT97)-96UO5]A='1R M:6)U=&5?9&5F875L=#L^#0H@(" @(" @(#PA14Q%345.5"!43TY%4E-!5D53 M("A4;VYE6]U="HI/@T*"0D)/"%!5%1, M25-4($=205E/5513( T*"0D)"69'6]U="!.351/2T5.("(P(CX-"@D)"0D\(45, M14U%3E0@1W)A>6]U=" H(U!#1$%402D^#0H)"0D)/"%!5%1,25-4($=R87EO M=70@#0H)"0D)"4=R87EO=71)9" H4%))3E1%4D1%1D%53%1\5&5X=$=R87!H M:6-\5&5X='Q/9F9\1&5F875L='Q''1);6%G97Q' M6]U=$ED("A.3TY%?$9I='Q3=')E=&-H?%IO;VU\,E50 M?#154'Q4=VEC92D@(DY/3D4B/@T*(" @(" @(" \(2TM("XN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXM+3X-"B @(" @(" @/"$M+2!087!E&5L+%!A<&5R+D%R96$N MF5);F-H,3 P+ T*"0D)"0D)"5!A<&5R+D%R96$N M<'1!&5L($5-4%19(#X-"@D)"0D) M/"%!5%1,25-4(%!A<&5R+D%R96$N<'1!&5L( T*"0D)"0D))7)E8W1?871TF5-;3$P( T*"0D)"0D) M)7!O:6YT7V%T=')I8G5T97,[/@T*"0D)"0D\(45,14U%3E0@4&%P97(N07)E M82YP=%-I>F5);F-H,3 P($5-4%19(#X-"@D)"0D)/"%!5%1,25-4(%!A<&5R M+D%R96$N<'13:7IE26YC:#$P," -"@D)"0D)"25P;VEN=%]A='1R:6)U=&5S M.SX-"@D)"0D)/"%%3$5-14Y4(%!A<&5R+D%R96$N<'1!F5-;3$P+%5$4$EN9F\N7!E($5-4%19/@T* M"0D)"3PA05143$E35"!#;VQL871E5'EP92 -"@D)"0D)0V]L;&%T951Y<&5) M9" H05543WQ*4WQ(87)D=V%R92D@(D%55$\B/@T*"0D)"3PA+2U%3$5-14Y4 M($-O;&QA=&4N36%X3G5M("@C4$-$051!*2TM/@T*"0D)/"%%3$5-14Y4($=R M;W5P($5-4%19/@T*"0D)/"%!5%1,25-4($=R;W5P( T*"0D)"71'$YU;3\I/@T*"0D)/"%!5%1,25-4($UA:6Q";W@@ M#0H)"0D)=$UA:6Q";W@@)7-T871E,U]A='1R:6)U=&5?9&5F875L=#L^#0H) M"0D)/"%%3$5-14Y4($UA:6YL0F]X+DUA>$YU;2 H(U!#1$%402D^#0H)"0D\ M(45,14U%3E0@4W1A<&QE("A3=&%P;&4N36%X3G5M/RQ3=&%P;&4N3$]#051) M3TY3/RD^#0H)"0D\(4%45$Q)4U0@4W1A<&QE( T*"0D)"713=&%P;&4@)7-T M871E,U]A='1R:6)U=&5?9&5F875L=#L^#0H)"0D)/"%%3$5-14Y4(%-T87!L M92Y-87A.=6T@*"-00T1!5$$I/@T*"0D)"3PA14Q%345.5"!3=&%P;&4N3$]# M051)3TY3("A3=&%P;&4N3&]C871I;VXJ*3X-"@D)"0D\(4%45$Q)4U0@4W1A M<&QE+DQ/0T%424].4R -"@D)"0D)4W1A<&QE+DYU;4QO8V%T:6]N($Y-5$]+ M14X@(C B/@T*"0D)"0D\(45,14U%3E0@4W1A<&QE+DQO8V%T:6]N("@C4$-$ M051!*3X-"@D)"0D)/"%!5%1,25-4(%-T87!L92Y,;V-A=&EO;B -"@D)"0D) M"5-T87!L92Y,;V-A=&EO;DED("5S=&%P;&5L;V-A=&EO;E]A='1R:6)U=&5? M9&5F875L=#L^#0H)"0D\(45,14U%3E0@1D],1%,@*$9O;&0J*3X-"@D)"3PA M05143$E35"!&3TQ$4R -"@D)"0ET1F]L9" E$YU;2 H(U!#1$%402D@+2T^#0H)"0D)/"%%3$5- M14Y4($9O;&0@*$9O;&0N5'EP92D^#0H)"0D)"3PA14Q%345.5"!&;VQD+E1Y M<&4@14U05%D^( T*"0D)"0D\(4%45$Q)4U0@1F]L9"Y4>7!E( T*"0D)"0D) M1F]L9%1Y<&5)9" H3D].17Q:1F]L9'Q3861D;&5\1&]U8FQE1V%T97Q,969T M1V%T97Q2:6=H=$=A=&5\3&5T=&5R1F]L9'Q81F]L9"D@(DY/3D4B#0H)"0D) M"0E-87A.=6T)3DU43TM%3B C24U03$E%1#X-"@D)"3PA14Q%345.5"!(;VQE M4'5N8V@@*$AO;&50=6YC:"Y-87A.=6T_*3X-"@D)"3PA05143$E35"!(;VQE M4'5N8V@-"@D)"0ET2&]L95!U;F-H("5S=&%T93-?871T'!A;G-I M;VX@56YI=',@(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @(" @+2T^#0H)(" @(#PA+2T@+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BTM/@T*"0D\(45, M14U%3E0@15A054Y)5%,H15A04D%-4RQ%6%!&3TY40T%21%,L15A01%503$58 M4RQ%6%!005!%4E-/55)#15,L15A04$%015)$15-424Y!5$E/3E,L15A024Y3 M15)415)3+$584%-43U)!1T53*3X-"@D)"3PA14Q%345.5"!%6%!204U3("A% M>'!204TJ*3X-"@D)"3PA05143$E35"!%6%!204U3( T*"0D)"69%>'!204T@ M)6)O;VQ?871T'!204T@3DU43TM% M3B B,"(^( T*"0D)"3PA14Q%345.5"!%>'!204T@*"-00T1!5$$I/@T*"0D) M"3PA05143$E35"!%>'!204T@#0H)"0D)16YT'!&;VYT0V%R9" E M8F]O;%]A='1R:6)U=&5?9F%L'!&;VYT0V%R9"Y&3TY44RD^#0H)"0D)/"%!5%1,25-4($5X<$9O;G1# M87)D( T*"0D)"0E%>'!&;VYT0V%R9$ED($Y-5$]+14X@(TE-4$Q)140^#0H) M"0D)"3PA14Q%345.5"!%>'!&;VYT0V%R9"Y&3TY44R H1F]N="HI/@T*"0D) M"0D\(4%45$Q)4U0@17AP1F]N=$-A'!&;VYT M3G5M($Y-5$]+14X@(TE-4$Q)140^#0H)"0D)"0D\(2TM($5,14U%3E0@1F]N M=" H(U!#1$%402DM+3X-"@D)"0T*"0D)/"%%3$5-14Y4($584$154$Q%6%,@ M*$5X<$1U<&QE>"HI/@T*"0D)/"%!5%1,25-4($584$154$Q%6%,@#0H)"0D) M9D5X<$1U<&QE>" E8F]O;%]A='1R:6)U=&5?9F%L"!.351/2T5.("(P(CX-"@D)"0D\(45,14U%3E0@17AP1'5P;&5X M("A00T1!5$$L4$%015)3*3X-"@D)"0D)/"$M+2 _/S\_/R!&24Y)4TA)3D=3 M("TM/@T*"0D)"0D\(2TM($5,14U%3E0@4$%015)3("A087!E'!087!E'!087!E'!087!E'!087!E'!) M;G-E'!3=&]R M86=E($Y-5$]+14X@(C B/@T*"0D)"3PA+2U%3$5-14Y4(%-T;W)A9V4@*"-0 M0T1!5$$I+2T^#0H-"CPA+2T@+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BX@+2T^#0H\ M(2TM($9!6$-!4"!I$-A<"Y(96%D M97(L1F5A='5R97,I/B -"CPA14Q%345.5"!&87A#87 N2&5A9&5R("A&87@L M3&%N9W5A9V4L36]D=6QE3F%M97,I/@T*"3PA14Q%345.5"!&87@@*"-00T1! M5$$I/@T*/"$M+2 N+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+B M+3X-"CPA+2T@1F%X M($9E871U updated web page Message-ID: Hi All, I've updated the UPDF web page at http://www.pwg.org/updf I also added links to the current DTD and XML file at the bottom of the page. I've decided to move it higher in the page though so it's easier to see. The DTD still dosn't load completely in Visual Basic - but I will work on it later today. Sandra Matts --------------------------------------- Sandra Matts Engineer Scientist Hewlett-Packard sandram@boi.hp.com 208-396-4755 phone Boise, ID 83714 -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 1696 bytes Desc: not available Url : http://www.pwg.org/archives/upd/attachments/19991116/020c0635/winmail-0001.bin From sandram at boi.hp.com Wed Nov 17 14:27:28 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:05 2009 Subject: UPD> UPDF.dtd now works in VB Message-ID: Hi, I've updated the ftp site with a updf.dtd and CLJ4500.xml file that produces NO errors in Visual Basic. Whew! I guess I learned my lesson using XML Pro. There were a bunch of problems in the DTD and XML file. I also deleted some lines from the DTD in the interest of getting it to parse correctly. I do have previous versions of the DTD checked into my source control at work. We can always pull it out later after the UI work is done. Current versions are at : ftp.pwg.org/pub/pwg/upd/updf.dtd ftp.pwg.org/pub/pwg/upd/CLJ4500.xml Sandra Matts Sandra Matts Engineer Scientist Hewlett-Packard sandram@boi.hp.com 208-396-4755 phone Boise, ID 83714 -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 1860 bytes Desc: not available Url : http://www.pwg.org/archives/upd/attachments/19991117/8c65e4c2/winmail-0001.bin From sandram at boi.hp.com Wed Nov 17 14:37:31 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:05 2009 Subject: UPD> XUL uses dtd in non standard way Message-ID: Hi, I've run across a problem trying to use XUL in the MS XML parser. XUL has the XML describing the user interface in a file with the .xul extension. It's pretty standard XML and XML schema code. I think so anyway. They are localizing using !ENTITIES in a dtd file. In reality, XUL is not using the DTD to describe the grammer for the user interface code in the .xul file. The problem is Visual Basic won't parse the .xul file since it is expecting the DTD. If I don't include the DTD in the xul file then of course the parser complains because it can't find the ENTITY defines. The XPFE - cross platform front engine must be a home-grown parser and can handle the DTD inconsistencies. Unless everyone wants to use the XPFE, we can't use XUL directly. I don't want to be forced to use the XPFE, I think the advantage of having a XML based format is to use parsers already out there. If we can't directly use XUL - it looks like we have to leverage. Concerns??? Suggestions??? Sandra Matts Sandra Matts Engineer Scientist Hewlett-Packard sandram@boi.hp.com 208-396-4755 phone Boise, ID 83714 -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 2140 bytes Desc: not available Url : http://www.pwg.org/archives/upd/attachments/19991117/067c83d8/winmail-0001.bin From sandram at boi.hp.com Fri Nov 19 17:41:57 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:05 2009 Subject: UPD> UPDF phone conference Message-ID: Please respond to this email if you want to have a UPDF phone conference this Tuesday. Reply to upd@pwg.org. Due to the low turnout last time, I want to make sure people will participate. Sandra Matts From nschade at xionics.com Mon Nov 22 10:11:34 1999 From: nschade at xionics.com (Norbert Schade) Date: Wed May 6 14:05:05 2009 Subject: Fw: UPD> UPDF phone conference Message-ID: <001801bf34fb$dda9ed80$c31343ce@gca-2.xionics.com> to make it public -----Original Message----- From: Norbert Schade To: Sandra Matts Date: Monday, November 22, 1999 10:09 AM Subject: Re: UPD> UPDF phone conference >Sandra, >I have a chance to spend most of the time of this short week on Mozilla. >So a call next week Tuesday would be more productive for me. > >Just to confirm: >We do not expect any driver to rely on Mozilla being installed for realizing >any UI. We just use that spec to describe our stuff. Correct? > >Concerning the LA conference I get my booking done this Wednesday. >If I don't hear any other schedule, I'll arrive Wednesday evening. So I'd be >available all Thursday, if required. >One day earlier would not be a problem, but I don't want to hang around. >regards >Norbert >-----Original Message----- >From: Sandra Matts >To: Universal Printer Driver >Date: Friday, November 19, 1999 5:43 PM >Subject: UPD> UPDF phone conference > > >>Please respond to this email if you want >>to have a UPDF phone conference this Tuesday. >>Reply to upd@pwg.org. >>Due to the low turnout last time, I want >>to make sure people will participate. >> >>Sandra Matts >> > From sandram at boi.hp.com Mon Nov 22 19:48:00 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:05 2009 Subject: UPD> updf phone conference Message-ID: Hi, Since only two people replied, we won't be having a phone conference on Tuesday. I am still working on creating a proof of concept for LA with style sheets, so I will just keep plugging away. I will send out what I have on Wed. the week before the PWG meeting so that people can look at it. Sandra Matts From sandram at boi.hp.com Tue Nov 23 19:21:51 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:05 2009 Subject: UPD> FW: XPToolkit spec frozen Message-ID: Norbert sent me this message and I wanted the reply to the entire UPDF group. The XPToolkit is not frozen. They are adding widgets but very slowly. Here is a link to a list of widgets supported so far. http://www.mozilla.org/newlayout/doc/widgets.html They list radio buttons, tab, combo box. Almost everything we need. Sandra Matts -----Original Message----- From: Norbert Schade [mailto:nschade@xionics.com] Sent: Tuesday, November 23, 1999 11:23 AM To: Sandra Matts Subject: XPToolkit spec frozen Sandra, what's your information status about XPToolkit? Is it frozen concerning the feature set or are they redesigning it every now and then? I'm surprised not to find some basics described like edit boxes, combo boxes, list boxes and radio buttons at least. If you have a direct contact, could you ask? I'd be very surprised, if they'd leave it out for the first version, as many homepages already work with that. Let's work on a prioritized list of missing widgets: 1. edit boxes, combo boxes, list boxes, radio buttons 2. spin controls, switch groups (can probably be realized by tabs) 3. Preview (page, printer config, etc.) To be extended. We may stay with Mozilla's help options for now. Norbert From jkm at underscore.com Tue Nov 23 19:33:06 1999 From: jkm at underscore.com (Jay Martin) Date: Wed May 6 14:05:05 2009 Subject: UPD> FW: XPToolkit spec frozen References: Message-ID: <383B3242.4CA5EF47@underscore.com> Should we be worried that the page referenced in your message is dated early October 1998 (near the top of the page)? ...jay Sandra Matts wrote: > > Norbert sent me this message and I wanted the reply to > the entire UPDF group. > > The XPToolkit is not frozen. They are adding widgets > but very slowly. Here is a link to a list of widgets > supported so far. > http://www.mozilla.org/newlayout/doc/widgets.html > > They list radio buttons, tab, combo box. Almost > everything we need. > > Sandra Matts > > -----Original Message----- > From: Norbert Schade [mailto:nschade@xionics.com] > Sent: Tuesday, November 23, 1999 11:23 AM > To: Sandra Matts > Subject: XPToolkit spec frozen > > Sandra, > what's your information status about XPToolkit? > Is it frozen concerning the feature set or are they redesigning it every now > and then? > I'm surprised not to find some basics described like edit boxes, combo > boxes, list boxes and radio buttons at least. > If you have a direct contact, could you ask? I'd be very surprised, if > they'd leave it out for the first version, as many homepages already work > with that. > Let's work on a prioritized list of missing widgets: > 1. edit boxes, combo boxes, list boxes, radio buttons > 2. spin controls, switch groups (can probably be realized by tabs) > 3. Preview (page, printer config, etc.) > To be extended. > We may stay with Mozilla's help options for now. > Norbert From sandram at boi.hp.com Tue Nov 23 20:02:25 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:05 2009 Subject: UPD> FW: XPToolkit spec frozen In-Reply-To: <383B3242.4CA5EF47@underscore.com> Message-ID: Yes - it is odd. At the bottom of the page the "real" last modified is Jan 14, 1999. It appears that documentation is behind the implementation. I will download the latest Milestone binary and see how full featured the user interface is. Sandra Matts -----Original Message----- From: Jay Martin [mailto:jkm@underscore.com] Sent: Tuesday, November 23, 1999 5:33 PM To: Sandra Matts Cc: Universal Printer Driver Subject: Re: UPD> FW: XPToolkit spec frozen Should we be worried that the page referenced in your message is dated early October 1998 (near the top of the page)? ...jay Sandra Matts wrote: > > Norbert sent me this message and I wanted the reply to > the entire UPDF group. > > The XPToolkit is not frozen. They are adding widgets > but very slowly. Here is a link to a list of widgets > supported so far. > http://www.mozilla.org/newlayout/doc/widgets.html > > They list radio buttons, tab, combo box. Almost > everything we need. > > Sandra Matts > > From nschade at xionics.com Wed Nov 24 09:43:05 1999 From: nschade at xionics.com (Norbert Schade) Date: Wed May 6 14:05:05 2009 Subject: UPD> widget set Message-ID: <000801bf368a$3855d840$c31343ce@gca-2.xionics.com> All, starting from mozilla.org jump to projects. In the list you see XPToolkit and NewLayout directly followed by each other. I haven't been able to exactly determine the essense and differences between them, but I mainly live in the XPToolkit path these days. You can easily see that these pages are up-to-date. I can't get rid of the feeling that the one (NewLayout) is the plan and the other (XPToolkit) is the real work. The widget set in the XPToolkit path is smaller than the one in the NewLayout/Technical documentation path. Norbert From sandram at boi.hp.com Mon Nov 29 15:25:46 1999 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:05 2009 Subject: UPD> widget set In-Reply-To: <000801bf368a$3855d840$c31343ce@gca-2.xionics.com> Message-ID: I believe the XPToolkit is real work too. I feel it's important to just some list going into our UPDF and then see what we have to add. We may have to periodically follow mozilla and add new widgets when needed. I have a proto started which uses just the basic widgets so far - tab, check box, frame, radio buttons, cmdButtons. I will show it at the next meeting. Things I haven't added to the prototype yet but should be considered are: a UI constraint model, localization strings. Sandra Matts -----Original Message----- From: owner-upd@pwg.org [mailto:owner-upd@pwg.org]On Behalf Of Norbert Schade Sent: Wednesday, November 24, 1999 7:43 AM To: UPD group Subject: UPD> widget set All, starting from mozilla.org jump to projects. In the list you see XPToolkit and NewLayout directly followed by each other. I haven't been able to exactly determine the essense and differences between them, but I mainly live in the XPToolkit path these days. You can easily see that these pages are up-to-date. I can't get rid of the feeling that the one (NewLayout) is the plan and the other (XPToolkit) is the real work. The widget set in the XPToolkit path is smaller than the one in the NewLayout/Technical documentation path. Norbert From nschade at xionics.com Tue Dec 7 17:10:04 1999 From: nschade at xionics.com (Norbert Schade) Date: Wed May 6 14:05:05 2009 Subject: UPD> UPDF constraints Message-ID: <001501bf40ff$d9b32e20$c31343ce@gca-2.xionics.com> All, I have done some research and thinking about constraints and I want to share it at this point. I would appreciate first comments this week to be able to work it over. I haven't concentrated to much on writing good XML so far. I may try that the next days in case we agree about the general direction. I will arrive in LA Wednesday night very late, will have a breakfast late Thursday morning and could talk about constraints further more in detail after that, if people are interested and available. If you have WinWord available you may want to read the attached doc file. I have copied it below. But the tabs are translated badly and the 'rectangles' stand for bullets. Start of WinWord document UI constraints in UPDF I thought about it a while and want to start the discussion to prepare a section in the spec. Up to now I limit myself to contraints in the UI, although we are facing similar problems when printing, too. But this often results in CallBack functions. That?s why I call it ?UI constraints?. Statement 1 (to be discussed): Constraints handle limitations and automatic switches To provide consistent functionality, we do not only handle limitations and exclusions like ?if DialogElement1 is set to Setting1, DialogElement2 cannot show Setting2?, but also automatic switches like ?if DialogElement1 is set to Setting1, DialogElement2 is to be set to Setting2?. I do not think this needs a lot of extra work either, but would ease the understanding of even complex UI behavior. Statement 2 (to be discussed): Installed options are to be identified InstalledOptions must be declared as such so they can be identified for specific functionality. Statement 3 (to be discussed): All interdependencies between driver elements are handled as constraints Only the model itself or InstalledOptions like an Input or Output option can own another driver element. So only the model and any InstalledOption can have lists of paper sources, sizes, media types, duplex modes, etc. This might be a kind of a revolution for some people, but it keeps the printer?s description and later the driver very straightforward. It means that the model owns e.g. paper sources and paper sizes in separate lists, but this part of the UPDF does not tell that certain sources do only support certain sizes. I know that this would require a significant change of the sample XML of M.Yeung. But paper sources and even other driver elements have so many different attributes between different manufacturers nowadays that it would extremely hard to find a generic way to describe these interdependencies within the listings of driver elements. Now while I seriously think about constraints it looks more reasonable to me to provide a separate constraint section and tell there as a constraint that the envelope tray does not feed Letter and many other sizes. Statement 4 (to be discussed): The list of conditional sets combined to a constraint is infinite We want to allow maximum flexibility. With combining two conditional sets to a constraint this is only possible in a limited way. So we could tell that duplex is only available with a certain amount of RAM and depending on certain paper sizes and only from certain paper sources. Simplifying that and ignoring perfect XML syntax at the moment this could result in two constraints like: Constraints Model Constraint Set Condition RAM <= 2MB /Condition /Set Set Condition (PaperWidth x PaperHeight) > 2MB /Condition /Set Set Condition Duplex != Off /Condition /Set /Constraint Constraint Set Condition PaperSource != Manual /Condition /Set Set Condition Duplex != Off /Condition /Set /Constraint /Model /Constraints I?d like to define some rules with this simplified sample: Rule 1: InstalledOptions will not be changed by constraints. So condition 1 of constraint 1 will not result in any change in the UI. This explaines Statement 2. Rule 2: The definition of the constraint defines the order in which it will be resolved. This can be ignored in case of exactly two conditional sets per constraint. In case of more conditional sets it may happen that a certain selection in the UI is activating condition 1 of constraint 1. May be that resolving condition 2 of constraint 1 is already resolving the complete constraint. So condition 3 of constraint 1 can be skipped. That means the order of conditions is Top-Bottom. The top condition is to be resolved first and so on. That allows control about priorities. Rule 3: The order of constraints define their priorities. Not very obvious that we need that rule. But resolving a certain constraint may activate another constraint. Hoping we will never get into an infinite loop, it?s now important, what to do first and next. Defining a global default element or message could help avoid crashing the driver. Rule 4: InstalledOptions have their own constraints. They do not change or extend constraints of the basic models. In case an InstalledOption is going to be merged into a basic UPDF file, the corresponding block of constraints should be added after all other blocks already listed. In the example above no InstalledOption is listed. So I only show the Model section. The string Model is a technical variable, not the UI string (I have seen cases, where models had different names in different locales). This procedure keeps it easier to handle InstalledOptions. Certain constraint blocks can be easily removed without being afraid to break anything. In case there are constraints between different InstalledOptions ? and this is known ? the constraint blocks for both InstalledOptions should list the corresponding constraints. To-do-list ? We have to decide whether we define the good or the bad elements. In my examples I defined the bad combinations in all the constraints. This is causing some problems when trying to define automatic switches. See further below in this document. ? Some syntax issues must be discussed. Up to here that?s the basic part. You may have wondered why I braced the conditions with ?Set?. ? I can well imagine that we realize an OR by simply listing several conditions: Set Condition PaperSource = Tray1 /Condition Condition PaperSource = Tray2 /Condition Condition PaperSource = EnvelopeTray /Condition /Set Set Condition Duplex != Off /Condition /Set ? I can well imagine we want to handle other settings within a set. Samples could be ?Action? and ?Message?. The Action tag ? The action to resolve could be to mark the bad element. This could result in a red cross next to the bad element, e.g. in a combo box. Action Mark = RedCross.JPG ? The action to resolve could be to gray the bad element. This would show the bad element gray, but the others normal black. Action Gray = 75% ? The action to resolve could be to hide the bad element, apparantly the default, in case neither Mark, Gray nor Hide is listed under the Action tag. Action Hide = TRUE ? The action to resolve could be to show an info button to allow the user to activate a detailed message. Action Info = INFO.JPG ? The action to resolve could be to select a certain driver element active. In case Select is not listed under the Action tag, the first element of the driver element list of this UI element will be activated. I can well imagine several Select lines per constraint Set. This would result in a kind of a fallback selection in case the first listed Select line cannot be used because of a certain driver configuration. Action Select = Manual I can well imagine that several lines are combined to define a complex action: Set Condition UIElement1 != DriverElementX /Condition Action Mark = MARK.JPG Action Gray = 75% Action Info = INFO.JPG /Set Set Condition UIElement2 != DriverElementY /Condition Action Info = INFO.JPG Action Select = DriverElementZ1 Action Select = DriverElementZ2 /Set In case the driver provides all required functionality this would be resolved in case UIElement1 is to be changed: DriverElementX would be grayed and marked. An Info button would be visible next to the UI element, even when the combo box is not open. In case UIElement2 is to be changed: DriverElementY would be hidden. The selected driver element would not be the first in the list, but DriverElementZ1 ? if available. Otherwise DriverElementZ2. Info button as above. The Message tag This would only be used in case there is an Action Info line defined. ? We want to activate a certain text. Message Text = Constraint_PaperSource_Duplex ? We may want to activate different levels of message boxes. ? Exit: Just the message and and Exit button. Default. ? Exit_Show: The message, an Exit button and a Show button. Pressing the Show button would should another window with more detailed info. I think of the list of constraints that has been used for the UIElement, where the technical variables would be replaced by the locale specific strings. Although this would still be quite a technical information in a strict syntax it provides a lot of details with generic functionality. Just an idea. ? Exit_Show_Save: As Exit_Show, except that the detailed info can be saved to a file. Might be useful for the support or if somebody wants to manipulate his UPDF file. Message Window = Exit So the latest example could be extended to something like Set Condition UIElement1 != DriverElementX /Condition Action Mark = MARK.JPG Action Gray = 75% Action Info = INFO.JPG Message Text = Constraint_UIElement1_UIElement2 Message Window = Exit_Show /Set Set Condition UIElement2 != DriverElementY /Condition Action Info = INFO.JPG Action Select = DriverElementZ1 Action Select = DriverElementZ2 Message Text = Constraint_UIElement1_UIElement2 Message Window = Exit_Show /Set I think it is realistic to assume the same message text for both sets to save translation effort. Automatic switches This is not much more than an idea up to now. The general problem to realize something like ?if this is selected here, something else should happen there? is very similar to constraints in the basic sense. So I wonder whether we can use this or a very similar kind of syntax not only for the negative combinations (this and that cannot be combined), but also for activating certain selections depending on others. I will keep an eye on that. End of WinWord Document -------------- next part -------------- A non-text attachment was scrubbed... Name: UI constraints in UPDF.doc Type: application/msword Size: 35328 bytes Desc: not available Url : http://www.pwg.org/archives/upd/attachments/19991207/c21332d1/UIconstraintsinUPDF-0001.doc From nschade at xionics.com Tue Dec 28 10:57:58 1999 From: nschade at xionics.com (Norbert Schade) Date: Wed May 6 14:05:05 2009 Subject: UPD> constraints Message-ID: <000301bf514c$503b6f60$c31343ce@gca-2.xionics.com> the more I think about it the more I am sure about that statement: There is no OR in XML. Everything is interpreted as AND. So the only solution for something like "if paper size is Letter OR A4 then ..." is to build two separate constraints. Feedback please. Norbert