Hi Fabio,
Thanks for your detailed reports.
> Internationalization
> When using internationalization with an APPLICATION_SOURCE_PATH containing
> spaces (which are correctly escaped, like "/cygdrive/d/my\ dir" - without
> quotes!), xgettext failes with the following error, thus only producing empty
> .po-files, no messages.pot and no .js files:
>
> PREPARING APPLICATION TRANSLATION
> ----------------------------------------------------------------------------
> * Processing source code...
> xgettext: error while opening "/cygdrive/d/my" for reading: No such file or
> directory
> * Processing translations...
> - Translation: C
> - Merging translation file...
> - Generating catalog...
> - Translation: en
> - Merging translation file...
> - Generating catalog...
> - Translation: de
> - Merging translation file...
> - Generating catalog...
>
> I am now using 8.3 filenames, like "/cygdrive/d/MYDIR~1".
>
>
I could reproduce this bug and will file a bug to that end in the
qooxdoo bugzilla.
> Application namespace
> Though the documentation of APPLICATION_NAMESPACE declares "Even complexer
> stuff
> is possible like: net.sf.custom", it does not work. Loading an Application
> using
> such a complex namespace causes the following exception:
>
> Malformed settings key "net.sf.custom.resourceUri". Must be following the
> schema
> "namespace.key". in Setting.js (line 153)
>
This one I couldn't repro. I had no problem changing the skeleton to
this namespace. Particularly, I didn't get this error message, and also
the resulting script file was correctly named "net.sf.custom.js" (as you
mentioned in your other mail). Mind though that I had not only to change
the Application.js, but also the directory structure under source/class
to contain net/sf/custom. Please try to reproduce the problem with a
vanilla skeleton, and if you are successful zip it up and post it on the
list.
> Additional resources
> Using the APPLICATION_FILES option, all files and directories supplied are
> correctly copied into the "build" directory. However, cygwin sets "chmod 0"
> for
> every single resource so that files cannot be read, and directories not be
> traversed.
> My workaround is to perform the following commands to build:
> make build && chmod -R 755 build/ && find build/ -type f -exec chmod 644 '{}'
>
Same here, it worked alright for me. An additional file was copied into
the build directory with correct access rights. Are you sure there is
nothing in your shell environment (umask, ...) that might influence the
copy behaviour?
=Thomas
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
