All the news that fits, we print.
This week, 132 posts consumed 386 K. There were 44 different contributors. 24 (54%) posted more than once. 25 (56%) posted last week too. The top 5 posters of the week were:
|
News: CrossOver Office, WineX 2.0 | 03/25/2002 | Archive |
---|---|---|
The biggest news of the week is CodeWeavers
announcement
of their newest
product. Dubbed "CrossOver Office" it allows:
you to install your favorite Windows productivity applications in Linux, without needing a Microsoft Operating System license. CrossOver includes an easy to use, single click interface, which makes installing a Windows application simple and fast.
Once installed, your application will integrate directly with your Gnome or KDE environment. Just click and run your application, exactly as you would in Windows, but with the full freedom of Linux.
CrossOver Office is capable of running a range of Windows software, but CodeWeavers will support the following applications:
|
WineConf 2002 (con't) | 04/01/2002 | Archive |
---|---|---|
To follow up on <kcref> last week's coverage</kcref> of WineConf, Andreas Mohr mentioned, I just added a link to my final wineconf 2002 summary page at http://home.arcor.de/andi.mohr/wine/wineconf2002/ to the WineHQ News. If anyone else has anything to contribute, then feel free to tell me NOW :) |
Making Fonts Suck Less | 03/25/2002 | Archive |
---|---|---|
Russell Howe asked,
I'm afraid this is a little off-topic, but every time Wine starts, as it
builds the font metrics, xfs-xtt (the font server) dies. I'm assuming
there's a font (or few) in the system which it doesn't like, or which
are corrupt.
It makes wine rather annoying to use (and means that if I kill wine and
restart the font server, it thinks the metrics are already done and
ignores most of my fonts!)
Does anyone know an easy way to find out which fonts they are?
Huw Davies stepped up and replied:
Try deleting ~/.wine/cachedmetrics* , re-run wine with --debugmsg
+font
, the last font that gets listed before the crash should be the
problem one.
A much better way to do font rendering in Wine is to use the new
client side rendering code. For this you need an XServer capable of
supporting the RENDER extension (xdpyinfo will tell you whether you
have such a beast) and a copy of the FreeType library version at least
2.0.5 (but the later the better). Add a [FontDirs] section to your
~/.wine/config file, with entries pointing at any directories that
contain TT fonts
eg
[FontDirs]
|
Implementing BiDi Fonts | 03/25/2002 | Archive |
---|---|---|
Shachar Shemesh opened discussion on adding BiDi support to Wine:
Like I mentioned ealier last week, I intend to add BiDi support to WINE.
There is a library called fribidi (
http://fribidi.sourceforge.net/
)
that does a pretty good job, and seems exactly apropriate for this task. I
have two questions:
|
Implementing a DIB Engine | 03/30/2002 | Archive |
---|---|---|
This is the first of two threads Francois Gouget started
concerning features to be added to Wine. He asked for opinions
of other developers on how to approach them. The first thread
was about implementing a DIB engine:
The DIB engine was discussed quite a lot at WineConf. I am now trying
to summarize these discussions to update bug 421 - Implement a DIB
engine.
http://bugs.winehq.org/show_bug.cgi?id=421
Is the following accurate, complete, etc? Comments? Other ideas?
Any volunteers?
This was discussed quite a bit at WineConf. Ideas that were floated
around are:
|
Unicode and I18N Support | 03/30/2002 | Archive |
---|---|---|
The second thread Francois started was about Unicode support. Right
now there's a bug referencing it, but it's quite vague. Francois
requested comments about creating specific goals to make the task
seem more manageable. He wondered what controls still needed Unicode
support and what common dialogs need work.
Dmitry Timoshkov felt some things needed work, but added,
One more thing that should be addressed IMO as the part of the unicode
support in Wine: file APIs. For instance in the current state all russian
file names created by windows programs are completely unreadable in Linux
because they are created in code page 1251 but native russian encoding
in Linux is KOI8-R (code page 20866). Therefore all file APIs should
work with unicode natively, and convert file names to code page specified
somewhere in the config file (like [x11drv]/TextCP) on create, and vice versa
on reading file names from disk.
Dimitrie Paun thought that Linux's support of UTF8 would be enough.
But Dmitry didn't think that was sufficient,
I'm afraid that will help to Linux only based installations of Wine, and
in any case all functions in Wine implementing file APIs should internally
use unicode.
Dmitry proposed creating filenames on disk in encoding used
in Linux because it's necessary to support
general mount options, used by *all* russian
users in the world to be able correctly see cyrillic filenames under Linux
from a vfat partition:
mount -t vfat -o codepage=866,iocharset=koi8-r.
Shachar Shemesh wasn't sure Windows would be able to read them.
But Dmitry explained Windows would be able to
thanks to magic mounting options I mentioned earlier. Native Linux
localized applications know nothing about anything other than KOI8-R, and
filenames created by them on a vfat partition are readable under Windows
just fine.
|
Improving Regression Testing | 03/29/2002 | Archive |
---|---|---|
Geoffrey Hausheer had some ideas for making the testing
framework easier to use:
As I've been writing tests (only for the last
week or so), I realized that as we get a lot more tests,
it will be very difficult to keep track of what is being
tested, and what is not. I'd like to propose a list of
which functions for each DLL are being tested, which file
tests it, as well as any comments on the current tests.
In general, while Francois' presentation is a
good place to get started, I think it'd be a lot easier
if there was a document off of winehq with
recommendations on how to build, test, and document
tests. Lowering the difficulty threshold, is more likely
to draw more people to do so.
Francois Gouget replied:
I agree. Documenting and finishing the test framework is on the list
for Wine 0.9.0. I added the corresponding tasks yesterday:
http://bugs.winehq.org/show_bug.cgi?id=526 530 [NEW] - Package the regression tests for Windows http://bugs.winehq.org/show_bug.cgi?id=530 527 [NEW] - Running C regression tests on Windows with MSVC http://bugs.winehq.org/show_bug.cgi?id=527 528 [NEW] - Running C regression tests on Windows with Cygwin/MinGW http://bugs.winehq.org/show_bug.cgi?id=528 529 [NEW] - Running Perl regression tests on Windows http://bugs.winehq.org/show_bug.cgi?id=529
argv[2] = [c"] argv[3] = [d] |
All Kernel Cousin issues and summaries are copyright their original authors, and distributed
under the terms of the
GNU General Public License,
version 2.0.