XML Catalog files for XHTML
Reference: package: w3c-dtd-xhtml; version: 1.1-5ubuntu Hi, Anyone know who is maintaining the XML Catalog files for XHTML? The current w3c-dtd-xhtml distribution is both incorrect and incomplete, and it's not clear why the catalog and catalog.xml files supplied with the package don't refer to the entities supplied with the package. This may be simply an oversight, but it's not too difficult to fix this, and anyone actually using XML Catalogs would be better served with a functional set of catalogs for the entities supplied. The incorrect files include: /usr/share/xml/xhtml/schema/dtd/catalog /usr/share/xml/xhtml/schema/dtd/catalog.xml These use incorrect public identifiers and could also point into the other XHTML catalogs found in the subdirectories, but don't. The catalogs in the 1.0 directory: /usr/share/xml/xhtml/schema/dtd/1.0/catalog /usr/share/xml/xhtml/schema/dtd/1.0/catalog.xml don't include the DTDs themselves. The following are essentially correct but include an unnecessary module reference (since the module is not used by the flattened DTD): /usr/share/xml/xhtml/schema/dtd/1.1/catalog /usr/share/xml/xhtml/schema/dtd/1.1/catalog.xml For the catalogs used for XHTML Basic 1.0: /usr/share/xml/xhtml/schema/dtd/basic/catalog /usr/share/xml/xhtml/schema/dtd/basic/catalog.xml these, like XHTML 1.1, should refer to the flattened DTD unless the modular one is intended. If that latter is the case the rest of the modules would need to be included. As with XHTML 1.1 it's easier to simply refer to the flattened DTD: /usr/share/xml/xhtml/schema/dtd/basic/xhtml-basic10-f.dtd. The xhtml11-model-1.mod and xhtml-basic10-model-1.mod framework modules are only used if the modular DTD drivers (xhtml11.dtd and xhtml-basic10.dtd, resp.) are used; if this were the case the rest of the XHTML modules would be needed. These modules are not included in the Ubuntu distribution for XHTML 1.1. On the other hand, I note that the XHTML Basic 1.0 distribution includes most of the XHTML DTD modules. These aren't needed really if the flattened XHTML Basic 1.0 DTD is used (and it is available in the distribution -- there's no reason to the modular version unless one plans to modify the DTD). If the XHTML modules are to be included in the distribution it might be better to move them out of the 'basic' directory since they're not properly part of Basic but part of XHTML itself. This would also permit XHTML 1.1 to be built from the modules if someone wanted to create subsets or extensions (which is probably beyond the scope of discussions here). Finally, I probably should mention what xml1n.dcl is used for, as it's inconsistently used in the /usr/share/xml tree: whereas xml1.dcl is the correct SGML Declaration to be used with XML, xml1n.dcl is necessary when parsing with James Clark's SP toolkit (e.g., nsgmls). This is not documented anywhere in the package and is certainly one of the more arcane aspects of the XHTML distribution from W3C from whence this comes. I.e., you wouldn't want to use xml1n.dcl with most other software, though only no XML software would ever need to read an SGML declaration. By definition all XML software implicitly uses the xml1.dcl declaration. No variance is permitted and therefore its features are hardcoded into XML itself. I know of no XML software that actually reads an SGML declaration, but it is included for completeness, for XML as an SGML profile. My apologies if any of this has been discussed recently -- I looked through about six months of archives but didn't see any mention of the package. I'm happy to supply corrected XML Catalog files if desired. Cheers, Murray See: http://en.wikipedia.org/wiki/XML_Catalog http://xml.apache.org/commons/components/resolver/ http://xml.apache.org/commons/components/resolver/resolver-article.html ... Murray Altheim murray11 at altheim dot com = = === http://www.altheim.com/murray/ === === SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk = = === Boundless wind and moon - the eye within eyes, Inexhaustible heaven and earth - the light beyond light, The willow dark, the flower bright - ten thousand houses, Knock at any door - there's one who will respond. -- The Blue Cliff Record -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
HDMI and automatically hardware recognition
Hi everybody ! I just found one point that can really be improved in future releases of Ubuntu. In a first time I will explain how I found it, in a second time what I think about and the third point (the most important), a proposition to get rid of this lack... I got Ubuntu because I was worried about Windows (it's slow, it has a lot of glitches,...). With Ubuntu I can work without complications, until today... I bought a TV and wanted to connect it through HDMI cable. I configured my nvidia-settings and chose digital audio ouptut. It works fine, but... Every time I reconnect my TV, I must : - Manually detect connected screens - Set the correct screen settings - Change audio output to digital Every time I disconnect my TV, I must : - Set the correct screen settings (before disconnecting) - Change audio output to analog (otherwise laptop speakers don't work). In Windows, it works automatically in the most cases (sometimes not, it's just another Windows glitch...). I think that it's a pain for end-users (in this case I am) to have to always (re)set these damn settings to watch a movie, to connect a projector, to connect the external display. I know that's possible to script that, but as an end-user, I just don't want to : I want to use my computer and not to configure it all the time. When I connect my usb flash drive, it's automatically mounted and ready-to-use. Why it isn't the same with external displays ? A way to fix this problem, is to create something such as an hardware profile that contains settings and when a new display and/or audio output are detected (I think it's possible to detect a hardware change), a window / widget asks the user if he want's to apply saved settings or if he want's to set new settings. What do you think about that ? Yann -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: HDMI and automatically hardware recognition
I'll comment on the audio side, as thats what I am involved in, and am watching upstream. Video wise, I think it depends on what drivers you are using, but I'll let someone else more qualified comment on that side of things. On Tue, Feb 08, 2011 at 11:36:31PM EST, Yann Santschi wrote: A way to fix this problem, is to create something such as an hardware profile that contains settings and when a new display and/or audio output are detected (I think it's possible to detect a hardware change), a window / widget asks the user if he want's to apply saved settings or if he want's to set new settings. Audio wise, there is work going on upstream to retrieve the information from any connected HDMI device, and use that information to correctly configure audio setup for use by the user. The lower level parts of the stack, i.e ALSA don't even have this implemented properly if at all yet, and once thats done, the pieces higher up the stack, i.e PulseAudio still need to be extended to work with ALSA to get the information needed, and set things appropriately. In short, this is a known issue upstream, and it is being worked on, but I cannot give an estimate as to when it may be ready for use. Luke -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: HDMI and automatically hardware recognition
I see Luke has taken the audio half of this, as for the video part… On Tue, 2011-02-08 at 13:36 +0100, Yann Santschi wrote: Hi everybody ! I just found one point that can really be improved in future releases of Ubuntu. In a first time I will explain how I found it, in a second time what I think about and the third point (the most important), a proposition to get rid of this lack... I got Ubuntu because I was worried about Windows (it's slow, it has a lot of glitches,...). With Ubuntu I can work without complications, until today... I bought a TV and wanted to connect it through HDMI cable. I configured my nvidia-settings and chose digital audio ouptut. It works fine, but... Every time I reconnect my TV, I must : - Manually detect connected screens - Set the correct screen settings - Change audio output to digital Every time I disconnect my TV, I must : - Set the correct screen settings (before disconnecting) - Change audio output to analog (otherwise laptop speakers don't work). In Windows, it works automatically in the most cases (sometimes not, it's just another Windows glitch...). This is a combination of the nvidia-settings tool not being integrated into GNOME, the binary nvidia drivers not supporting the standard XRandR interface for monitor configuration, and no-one investing the time to make the standard GNOME display tools talk the proprietary NV-CONTROL protocol. If we had the code, we could fix the nvidia drivers - indeed, this *should* Just Work™ with the open-source nouveau drivers, and does for me. If convenience is more important than raw 3D performance you may find the nouveau drivers to be better for you. Of course, there's also the chance that hotplug detection won't work for your system with the nouveau drivers, but at least in that case we've got a chance of fixing it. I think that it's a pain for end-users (in this case I am) to have to always (re)set these damn settings to watch a movie, to connect a projector, to connect the external display. I know that's possible to script that, but as an end-user, I just don't want to : I want to use my computer and not to configure it all the time. When I connect my usb flash drive, it's automatically mounted and ready-to-use. Why it isn't the same with external displays ? A way to fix this problem, is to create something such as an hardware profile that contains settings and when a new display and/or audio output are detected (I think it's possible to detect a hardware change), a window / widget asks the user if he want's to apply saved settings or if he want's to set new settings. What do you think about that ? I think that what you actually want is for things to work automatically, like with USB, rather than have a pop up window. :) This is how it works for drivers which support XRandR and generate hotplug events right now - if you plug in a monitor, it will be set up the same way as it was last time, or if it hasn't been plugged in before it will have a sensible default set up. The big 3 - ati, intel, nouveau - all have the capabilities to do this. Similarly for audio (although I'm less familiar with the hardware capabilities here) - if we see an HDMI audio device is connected, and totem starts playing a movie, sending that stream over the HDMI connection is a good default. signature.asc Description: This is a digitally signed message part -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Cleaning up after console-setup mistake in Natty
On 2011-01-28 13:35, Colin Watson wrote: Lots of people have reported keyboard layouts being broken in Natty in one way or another. This was due to a merge I did from Debian on 2011-01-05 which worked fine in my tests, but turned out to fail in a number of common cases. I've identified two major problems: * I added some misguided migration code which broke in the case of debconf preconfiguration (which most people use because apt does it, but I was testing with 'dpkg -i'). The effect of this was to reset the various keyboard settings to the first choice in their respective lists: if you have XKBMODEL=a4techKB21 and XKBLAYOUT=us,af in /etc/default/keyboard, then this is what happened. This also tended to result in keyboard questions being asked on every upgrade. * Versions of the installer-side keyboard handling code prior to Natty didn't always set the 'seen' flag for keyboard questions in the installed system's debconf database. As a result, many people were asked the keyboard layout and variant questions again. I've uploaded console-setup 1.57ubuntu5 to fix this. When upgrading the keyboard-configuration package to the new version, if it detects a migration bug, it takes the old commented-out XKB* values from /etc/default/console-setup and restores them, which should restore the correct keyboard layouts for most people. It will print messages on standard error saying that it is doing so, but will not present any debconf messages. However, if you installed your system with an image from before 2011-01-05, upgraded it to current Natty, and then manually edited /etc/default/keyboard or used 'dpkg-reconfigure keyboard-configuration', the effect of this cleanup will be to *erase* those manual changes and restore the configuration from before you upgraded console-setup. I hope that this will cause few problems, as the overwhelming likelihood is that the previous configuration was more accurate. I considered presenting the debconf questions again, but given the significant confusion already caused I felt that this would not improve the situation. Note that all of this only affects people who have upgraded through Natty between Alpha 1 and Alpha 2. If there's still a problem after all this, please let me know. Sorry for any inconvenience caused! I still have a problem, but I'm not sure if it's console-setup's fault. After a boot into Natty/Unity, I press Ctrl-Alt-T to open a terminal, and notice that I in fact have an English/US keyboard layout, even though the keyboard applet/indicator shows Swe. To fix this, I can click the keyboard applet and select USA, then back to Swe - now, the keyboard indicator now shows USA, but I have the correct layout in the terminal. Swedish layout works correctly from boot in a VT (i e Ctrl-Alt-F1). /etc/default/keyboard shows XKBMODEL=pc105 and XKBLAYOUT=se. -- David Henningsson, Canonical Ltd. http://launchpad.net/~diwic -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
