Here is the part that makes it bug :
(B
(B#define SHALLOC_FRAGMENT 32
(B/*
(B* If there are at least SHALLOC_FRAGMENT additional bytes of
(B* memory, divide the chunk into two chunks.
(B*/
(Bif ((u_int8_t *)rp =
(B(u_int8_t *)elp-links + SHALLOC_FRAGMENT) {
(Bsp = rp;
(B//---
also the keybindings need to work off configuration and generic
actions - like the button bindings do now. also to do bindings right
Who will define the key generic actions?
look at the old ecore code in ecore/src/e_x.c and ecore/src/e_ev_x.c
will see
we cant go putting random x code in e17 (well
Title: [E-devel] spanish translation
Hello (hola for
Spanish)
Maybe Spanish E-community
should join our efforts and coordinate our translations and actions in order to
avoid duplication of work.
Another (good) idea would be
creating a web-page for Spanish users of Enlightenment, with
hello.
this is my polish translation, attached as pl.po
any polish users are free to comment or send me feedback
--
Grzegorz Gaczyski [EMAIL PROTECTED]
Linux user# 172707 Icq# 11422711 Gg# 1765546
./configure --enable-freedom --disable-softwarepatents=all
pl.po
Description: Binary data
Carsten Haitzler said:
definitely. basically the way i am doing things right now is:
the first translation for a language (es, pt etc.) becomes the
default until someone provides more specific translations (eg
pt_BR vs pt_PT). so that's why :) we are happy to accept
multiple translations.
Carsten Haitzler [EMAIL PROTECTED] [2005-04-20 11:56]:
I suggest to handle this the same way we do it in Esmart:
ecore-config --libs only includes -lecore, if you need the
subsystems, you'll have to add the other linker switches yourself.
hmm - i see not big problem with this - as long as
Ribas, Joan wrote:
Hello (hola for Spanish)
Maybe Spanish E-community should join our efforts and coordinate our
translations and actions in order to avoid duplication of work.
Another (good) idea would be creating a web-page for Spanish users of
Enlightenment, with translated documents,
About the es_AR or just es issue. I think it should be just es, and all
(Bcountry variations should default to es, unless somebody from one of
(Bthose countries wants a special translation. I would like to stress out
(Bhere that spanish from spain is es_ES and not es (which is just spanish
Hello all,
If anyone has tried to write some IPC code they know that it can be
tedious to pack and unpack data. Well, a while back I merged some code
from raster's evoak library/test app into ecore_ipc for handling data
packing/unpacking.
Now I guess some of you guys might not be so clear on
Hello,
I made the formatting a little more consistent int the Ecore_Ipc.h.
Also,
for the STRUCT_ENC function, if the structure to encode is NULL we
should set the size to 0 and return NULL, So I made a change to
accommodate this.
Stafford
Index: Ecore_Ipc.h
Title: RE: [E-devel] spanish translation
Cuenten conmigo para el proyecto!.
Les cuento que estoy trabajando en un Editor de texto (eNotes) basado en EFL avanzado, con posibilidad de coloreo de sintaxis y otros chiches que quiero ponerle.
Pueden contactarse conmigo por privado.
Get another
On Wednesday, 20 April 2005, at 08:09:08 (-0700),
E CVS List wrote:
use an install hook to setuid freqset thus avoiding mkinstalldir issues with
diff versions of automake
===
RCS file:
es:
Bueno yo no utilizo los locales en español, pero puedo ayudar si es necesario.
en:
Even though I don't use spanish locales, I'm willing to help out any way I can.
Also, I'm working in a text editor(eNotes) based on EFL, with syntax
highlight and some others gadgets that i wanna put in.
Hi, I quite don't agree on es_LA, LA is actually the country code for
(B"LAO PEOPLE'S DEMOCRATIC REPUBLIC". I would just leave it as es. Here
(Bare some definitions about this codes:
(Bhttp://www.openi18n.org/spec/ldml/1.0/ldml-spec.htm
(Bhttp://www.loc.gov/standards/iso639-2/englangn.html#st
Michael Jennings wrote:
On Wednesday, 20 April 2005, at 08:09:08 (-0700),
E CVS List wrote:
use an install hook to setuid freqset thus avoiding mkinstalldir issues with
diff versions of automake
===
RCS file:
On Wednesday 20 April 2005 03:14 pm, ilLogict wrote:
Another way to get that corrected is to modify MKINSTALLDIRS from
$(top_builddir)/./mkinstalldirs to $(mkinstalldirs), which contains
$(install_sh) -d, in makefiles.
It works atleast for me ;)
yes, but the new code is more 'standard' in
users were having issues turning off eterm borders on amd64:
http://bugs.gentoo.org/show_bug.cgi?id=76324
so a user proposed a patch which worked for him:
http://bugs.gentoo.org/attachment.cgi?id=56738
what do you think mej ?
-mike
---
This
Carsten Haitzler (The Rasterman) a écrit :
On Tue, 19 Apr 2005 22:23:29 -0400 Jay Summet [EMAIL PROTECTED] babbled:
imlib2 appears to store image data internally in ARGB format, which you can
get
a pointer to with a call such as:
unsigned int *pImageData = imlib_image_get_data();
Michael Jennings wrote:
On Wednesday, 20 April 2005, at 15:45:28 (-0400),
Mike Frysinger wrote:
users were having issues turning off eterm borders on amd64:
http://bugs.gentoo.org/show_bug.cgi?id=76324
so a user proposed a patch which worked for him:
http://bugs.gentoo.org/attachment.cgi?id=56738
On Wednesday 20 April 2005 04:24 pm, Michael Jennings wrote:
On Wednesday, 20 April 2005, at 15:45:28 (-0400),
Mike Frysinger wrote:
users were having issues turning off eterm borders on amd64:
http://bugs.gentoo.org/show_bug.cgi?id=76324
so a user proposed a patch which worked for him:
Insert Nike motto here
Paulo Matos
Nathan Ingersoll said:
Any objection to setting up a translations mailing list? This
is going
to be a continuous maintenance task, and not completely related
to
code development.
---
This SF.Net email
Hello,
I put some initial work into perl + efl bindings at http://pefl.miracles.net
I'd appreciate it if anyone could point me to various examples of code
in c (like
http://www.everburning.com/docs/evas_textblock/evas_textblock_intro.html
but for handling mouse events, listboxes, buttons
Roland Bär submitted this patch:
http://bugs.gentoo.org/attachment.cgi?id=52947action=view
via this bug:
http://bugs.gentoo.org/show_bug.cgi?id=84520
in an attempt to get the code working for amd64 ... patch is not ok as is, but
if the x86-specific code is wrapped in #ifdef __i386__ and then
23 matches
Mail list logo
