[Liblas-devel] posix

[Howard Butler]

did you try to send it to  liblas-devel at mail.hobu.net or liblas-devel at epimetheus.hobu.net 
?

The epimetheus one is not deliverable.  It is also possible your mail  
handler did a lookup and found epimetheus and rewrote the address and  
used that..  Please try to send again, and if you still have a problem  
I will dig into it later tonight.

Forwarding so Mateusz can think about a response in the mean time ;)

Howard



On May 5, 2008, at 3:30 PM, Martin (OPENGeoMap) wrote:

> Hi:
> I am receiving this Undelivered Mail Returned to Sender from your   
> liblas server list:
>
> This is the Postfix program at host mail.hobu.net.
>
> I'm sorry to have to inform you that your message could not be
> be delivered to one or more recipients. It's attached below.
>
> For further assistance, please send mail to <postmaster>
>
> If you do so, please include this problem report. You can
> delete your own text from the attached returned message.
>
> 			The Postfix program
>
> <Liblas-devel at epimetheus.hobu.net>: mail for epimetheus.hobu.net  
> loops back to
>   myself
>
> ------------------------------------------------------------------------
>
> Reporting-MTA: dns; mail.hobu.net
> X-Postfix-Queue-ID: 58DE48256B5
> X-Postfix-Sender: rfc822; martin at opengeomap.org
> Arrival-Date: Mon,  5 May 2008 15:26:15 -0500 (CDT)
>
> Final-Recipient: rfc822; Liblas-devel at epimetheus.hobu.net
> Action: failed
> Status: 5.0.0
> Diagnostic-Code: X-Postfix; mail for epimetheus.hobu.net loops back  
> to myself
>
>
> ------------------------------------------------------------------------
>
> Asunto:
> posix
> De:
> "Martin (OPENGeoMap)" <martin at opengeomap.org>
> Fecha:
> Mon, 05 May 2008 22:22:03 +0200
>
> Para:
> Liblas-devel at mail.hobu.net
>
>
> Hi:
>
> I am studying liblas source code a little i have several doubs:
>
>
>
> - Why use ANSI C standard to manage chars and std::string in C+??
> - In MVSC this works because use UTF-16, but in POSIX systems use  
> UTF8.
> - Qt people have QString and gnu/gnome people glib and glibmm  
> (glib::ustring) to solve this problems and works in all operating  
> systems and architectures.
>
>
> In Mingw i can not have a file called "España_is_spain" because the  
> 'ñ' letter =-O =-O =-O =-O
> Why here:
> http://ubuntuforums.org/archive/index.php/t-624698.html
>
> GNU explanation:
>
> There is a group of functions which wrap the common POSIX functions  
> dealing with filenames (g_open(), g_rename(), g_mkdir(), g_stat(),  
> g_unlink(), g_remove(), g_fopen(), g_freopen()). The point of these  
> wrappers is to make it possible to handle file names with any  
> Unicode characters in them on Windows without having to use ifdefs  
> and the wide character API in the application code.
>
> The pathname argument should be in the GLib file name encoding. On  
> POSIX this is the actual on-disk encoding which might correspond to  
> the locale settings of the process (or the G_FILENAME_ENCODING  
> environment variable), or not.
>
> On Windows the GLib file name encoding is UTF-8. Note that the  
> Microsoft C library does not use UTF-8, but has separate APIs for  
> current system code page and wide characters (UTF-16). The GLib  
> wrappers call the wide character API if present (on modern Windows  
> systems), otherwise convert to/from the system code page.
>
> Another group of functions allows to open and read directories in  
> the GLib file name encoding. These are g_dir_open(),  
> g_dir_read_name(), g_dir_rewind(), g_dir_close().
>
>
> C API
> http://library.gnome.org/devel/glib/stable/glib-File-Utilities.html
> http://library.gnome.org/devel/glib/2.16/
> c++ bindings (see Glib::ustring vs. std::string )
> http://www.gtkmm.org/docs/glibmm-2.4/docs/reference/html/classGlib_1_1ustring.html
> Ruby bindings:
> http://ruby-gnome2.sourceforge.jp/hiki.cgi?Ruby%2FGLib
> http://ruby-gnome2.sourceforge.jp/hiki.cgi?GLib
> python, perl, mono, etc bindings the same.
>
>
> In my GTK app in c, c++, c# and ruby i use glib to manage strings.  
> are there other solution??. Perhaps compilation flags???
>
> Regards
>
>
>
> Regards.
>