Re: Hungarian o and u double accute doesn't display correctly

2010-09-10 Thread Yavor Doganov
Please report issues with the Debian GNUstep packages to the Debian
BTS.  Many bugs are Debian-specific; it is the responsibility of the
Debian maintainers to analyze them, and forward only those that are
real upstream bugs.

В Thu, 09 Sep 2010 20:34:01 +0200, Csanyi Pal написа:
 I was run the comand 'defaults write NSGlobalDomain NSFont DejaVuSans'

, /usr/share/doc/gnustep-back0.18/README.Debian
| NOTE: Font names for the default art backend do not match the cairo
| backend; usually, an extra space is added for cairo, e.g. DejaVu
| Sans vs DejaVuSans.
`

So you should do

   defaults write NSGlobalDomain NSFont 'DejaVu Sans'


Or better yet, just remove this setting -- that way, by default
ttf-dejavu will be used with the cairo backend, and ttf-freefont with
the art backend.


___
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnustep


getting gnustep to work

2010-09-10 Thread stolennomenclature

Over the years I have tried many times to install and get Gnustep to work.
Never had any luck so far. All its ever produced for me is a nice list of
error messages. Tried again recently on Windows, no luck. So I tried just
now on a clean install of Ubuntu. I installed Gnustep, followed the mini
tutorial to create a tiny program and its makefile (below). I then, as
instructed, typed make, and as usual, got some error messages (just
below).

First I would like to ask if anyone can help me solve this problem?
Second I would like to ask if anyone knows why the developers are able to
write such a complex piece of code (gnustep and all its sophisticated
libraries) and yet seem unable to write a simple and effective means of
installing it?

Thanks in advance for any help that can be offered.

ERRORS:
make
GNUmakefile:1: /common.make: No such file or directory
GNUmakefile:6: /tool.make: No such file or directory
make: *** No rule to make target `/tool.make'.  Stop.


PROGRAM (source.m):

#import Foundation/Foundation.h

int
main (void)
{ 
  NSLog (@Executing);
  return 0;
}

MAKEFILE (GNUmakefile):

#import Foundation/Foundation.h

int
main (void)
{ 
  NSLog (@Executing);
  return 0;
}

-- 
View this message in context: 
http://old.nabble.com/getting-gnustep-to-work-tp29673384p29673384.html
Sent from the GNUstep - General mailing list archive at Nabble.com.


___
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnustep


Re: getting gnustep to work

2010-09-10 Thread David Chisnall
On 10 Sep 2010, at 04:24, stolennomenclature wrote:

 First I would like to ask if anyone can help me solve this problem?

Yes, the problem is trivial.  As it says on every single GNUstep tutorial, 
before compiling code you need to source the GNUstep.sh file (installed by 
default in System/Library/Makefiles/GNUstep.sh), to correctly configure the 
environment variables that GNUstep Make needs.

 Second I would like to ask if anyone knows why the developers are able to
 write such a complex piece of code (gnustep and all its sophisticated
 libraries) and yet seem unable to write a simple and effective means of
 installing it?

gmake  sudo -E gmake install seems pretty simple and effective to me - that's 
all I've ever needed to install any of the GNUstep libraries on FreeBSD, 
OpenBSD, Fedora, or Solaris 10.

David

-- Send from my Jacquard Loom


___
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnustep


Re: getting gnustep to work

2010-09-10 Thread Richard Frith-Macdonald

On 10 Sep 2010, at 04:24, stolennomenclature wrote:

 
 Over the years I have tried many times to install and get Gnustep to work.
 Never had any luck so far. All its ever produced for me is a nice list of
 error messages. Tried again recently on Windows, no luck. So I tried just
 now on a clean install of Ubuntu. I installed Gnustep, followed the mini
 tutorial to create a tiny program and its makefile (below). I then, as
 instructed, typed make, and as usual, got some error messages (just
 below).
 
 First I would like to ask if anyone can help me solve this problem?
 Second I would like to ask if anyone knows why the developers are able to
 write such a complex piece of code (gnustep and all its sophisticated
 libraries) and yet seem unable to write a simple and effective means of
 installing it?

What do you mean by 'installed Gnustep' here?
Do you mean that you used Ubuntu packages ... if so then any problem is with 
the Ubuntu packages rather than anything to do with GNUstep development, and 
you need to contact the person who is responsible for Ubuntu packages.  Of 
course the packages may have set everything up for you and perhaps all you need 
to do is log out and log in again ... but if so then perhaps you could ask the 
package maintainer to have the installation process end with a message to tell 
you that.

On the other hand, it you installed GNUstep stuff by building from source, then 
you probably forgot to read the installation instructions, README, INSTALL, or 
any of the installation tutorials available on the net...
When you configure gnustep-make there are two main options for the way you 
install:
1. Install in locations like OpenStep/Apple (unfortunately this is the default 
for historical reasons)
2. Install in some other location (eg the Linux Filesystem Hierarchy Standard 
'configure --with-layout-fhs')

If you are installing in the OpenStep/Apple locations then you need environment 
variables set up to say where to find things ... and all the documentation 
tells you about this.  Basically you need to source GNUstep.sh after installing 
gnustep-make and every time you log in.

If you are installing in a 'native' layout (fhs is probably ok for most linux 
systems) then things will be where the system expects to find them anyway, and 
you should not nod to source GNUstep.sh

Anyway, once gnustep-make is properly installed, the installation process for 
any other part of GNUstep is simply 'make install'



___
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnustep


Re: Hungarian o and u double accute doesn't display correctly

2010-09-10 Thread Stef Bidi
On Thu, Sep 9, 2010 at 1:34 PM, Csanyi Pal csanyi...@gmail.com wrote:

 However, when I run my application from xterm window, then I can see
 warnings:
 2010-09-09 20:17:42.091 LPT_Interface[7583] The font specified for
 NSLabelFont, Helvetica, can't be found.

 Helvetica is the default art backend font.  It's usually installed with the
art backend as a nfont.  If I remember correctly, nfonts aren't used in the
cairo backend.  My guess, is that if no font is specified, GNUstep will
default to Helvetica, a font not installed with the cairo backend.  If I'm
not mistaken cairo uses fontconfig, so all your system fonts are available.


 But, on Debian GNU/Linux Squeeze system, the command 'aptitude search
 helvetica' gives no results.

 I was run the comand 'defaults write NSGlobalDomain NSFont DejaVuSans'
 but I can see that that this command does not affect the NSLabelFont
 variable.

 Moreover, I was run these commands once again:
 defaults write NSGlobalDomain NSFont DejaVuSans
 defaults write NSGlobalDomain NSLabelFont DejaVuSans

 but still get warnings, like:
 2010-09-09 20:24:35.769 LPT_Interface[7681] The font specified for
 NSMenuFont, Helvetica, can't be found.

 2010-09-09 20:24:35.771 LPT_Interface[7681] The font specified for
 NSBoldFont, Helvetica-Bold, can't be found.

 2010-09-09 20:24:35.774 LPT_Interface[7681] The font specified for
 NSFont, DejaVuSans, can't be found.

 2010-09-09 20:24:35.803 LPT_Interface[7681] The font specified for
 NSLabelFont, DejaVuSans, can't be found.

A much, much easier way of specifying fonts is using the SystemPreferences
application.  I'd suggest grabbing it.  There's a module for fonts and it's
really easy to use.
___
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnustep


Problem with some characters

2010-09-10 Thread Germán Arias
On Ink and others GNUstep's apps, I can't write characters like:

ÁÉÍÓÚ

I don't know if this is a problem on my configuration or currently
GNUstep can't support this characters. Any suggestion? I'm using cairo
backend.


___
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnustep


Re: Problem with some characters

2010-09-10 Thread Csanyi Pal
Germán Arias ger...@xelalug.org writes:

 On Ink and others GNUstep's apps, I can't write characters like:

 ÁÉÍÓÚ

 I don't know if this is a problem on my configuration or currently 
 GNUstep can't support this characters. Any suggestion? I'm using cairo 
 backend.

I'm using art backend, and I can write these characters.
(Debian GNU/Linux Squeeze, gnustep installed using aptitude and debian
gnustep packages.)

-- 
Regards, Paul Chany
http://www.debian.org
http://wiki.debian.org/DebianEdu
http://csanyi-pal.info


___
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnustep


Re: Hungarian o and u double accute doesn't display correctly

2010-09-10 Thread Csanyi Pal
Stef Bidi stefanb...@gmail.com writes:

 A much, much easier way of specifying fonts is using the
 SystemPreferences application.  I'd suggest grabbing it.

 There's a module for fonts and it's really easy to use.

Finally, I get these charaters running my application!
What did I?

I used SystemPreferences for setup fonts.

I switch to the art backend.

-- 
Regards, Paul Chany
http://www.debian.org
http://wiki.debian.org/DebianEdu
http://csanyi-pal.info


___
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnustep


Re: Problem with some characters

2010-09-10 Thread Fred Kiefer
Am 10.09.2010 20:22, schrieb Germán Arias:
 On Ink and others GNUstep's apps, I can't write characters like:
 
 ÁÉÍÓÚ
 
 I don't know if this is a problem on my configuration or currently
 GNUstep can't support this characters. Any suggestion? I'm using cairo
 backend.

The current way how we test whether a cairo (or rather fontconfig) font
supports a character is horribly broken. As is the whole way we deal
with characters and glyphs in that backend. The result is that
characters get reported back as being supported by a font although they
aren't. That way the font replacement code that is already in gui wont
kick in here.
The simplest way to work around this is to use fonts that actually
supply all the characters you might use. An even better way to fix this
is to rewrite the glyph handling of the GNUstep cairo backend to move
away from the cairo toy font implementation.

Fred

___
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnustep


Re: Problem with some characters

2010-09-10 Thread Germán Arias
On vie, 2010-09-10 at 21:32 +0200, Fred Kiefer wrote:
 The current way how we test whether a cairo (or rather fontconfig) font
 supports a character is horribly broken. As is the whole way we deal
 with characters and glyphs in that backend. The result is that
 characters get reported back as being supported by a font although they
 aren't. That way the font replacement code that is already in gui wont
 kick in here.
 The simplest way to work around this is to use fonts that actually
 supply all the characters you might use. An even better way to fix this
 is to rewrite the glyph handling of the GNUstep cairo backend to move
 away from the cairo toy font implementation.
 
 Fred

Well, the fonts I'm using have those characters. I can write without
problem on OpenOffice with these. But I noticed that if I copy and paste
these characters from OpenOffice to Ink, I can see these perfectly. Then
the problem is on the input from keyboard to get those characters. Or I
think so.


___
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnustep