Hi devs,
We need to define a strategy for better handling translations. I've
had a call with Guillaume and Jean-Vincent and here's the process we'd
like to propose:
* One person is in charge of http://l10n.xwiki.org/. This means
monitoring the work there, coordinating validation of key values and
ensuring validated translations are incorporated in the source tree.
Guillaume is willing to take that role for now.
* The XE release manager has the responsibility of taking the
validated keys on l10n.xwiki.org and committing them during the
Milestone 2 dev (before the RC1).
* The l10n manager should ping the release manager whenever there are
translated and validated keys ready to be incorporated or if there
have been important changes to be included in the release after M2 has
been released.
* The l10n manager should test XE and the applications after the keys
have been applied to ensure quality. Basically the l10n manager is
responsible for the quality of translations in general.
Here's my +1
Thanks
-Vincent
Hello,
I am working on creating blog entries using xwiki. I was wondering if it would be possible to create a template for the blog entries so that they will be more structured?
Thank you for your time and help!
Hande Aksac
Hi,
Since I'm rewriting the new Rendering component
(see http://dev.xwiki.org/xwiki/bin/view/Design/NewRenderingArchitecture)
, we need to finalize the new syntax we want to have.
Right now I'v planned to use the same wiki syntax as now
(http://platform.xwiki.org/xwiki/bin/view/Main/
XWikiSyntax#HTextStyles) with only one change: all macros now need to
be closed.
For example: {macro}...{/macro} and {macro:text|param=value|.../}
Is that ok with everyone or do we want to make changes?
Thanks
-Vincent
Hello XWiki developers,
can someone explain me what is the strategy to define the mime-type of
an attachment?
I see not configurable map nor any setter on the attachment types.
Is there any way I can enrich this or is it simply taking over the
mime-type provided the browser (which, too often, ends up being
application/octet-stream) ?
thanks in advance
paul
Hi devs,
I've implemented support for Google Gadgets for pages and for panels.
http://incubator.myxwiki.org/xwiki/bin/view/Gadgets/
It is possible to browse the Google Gadget Directory and select a
gadget, set it's parameters and either:
- insert a call to a gadget macro in a wiki page
- create a panel with this gadget
It's basically working, except for a few Gadget translations issues in
the gadget settings page (for some gadgets).
To integrate in XE this requires:
- a slight modification to the PanelClass and the displaypanel macro (to
support a gadgeturl and gadgetprefs field)
- a few pages including a Gadget Groovy page (which requires programming
rights)
I think we should transform the Gadget Groovy to a plugin to avoid the
need for programming rights.
We can also from there create a special page type to make a display of
gadgets or panels like iGoogle or NetVibes.
It would store gadgets or panel lists in a special class with some
position parameters. And with some JS we can reposition the panels or
gadgets and save the config in the wiki page.
This would be an easy way to make some portal like experience in the wiki.
Who wants to takeover this from the dev team ? Do you think we can have
this in 1.8 ?
Ludovic
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Hi devs,
we are working with XWiki for about three years now (I think we
started using it around version 0.8). In this time we developed
several plugins, which we always planed to make open source to give
something back to the community. However, until now we never found the
time to do it. Now we saw in your GSoC proposals the project for a new
photo album application. We thought this would be a good moment to
contribute our photo plugin (or parts of it).
Short list of features:
- unzip an attached file and attach the contained files to a document
(i.e. the photo album)
- resize images to a maximum width and height maintaining the aspect
ratio (if you like already while unzipping) - only jpg until now. When
we wrote it, the XWiki image plugin stretched the images when width
and height were defined.
- read meta data from images (using http://www.drewnoakes.com/code/exif/
- sadly it seems the library is not updated anymore)
The plugin would be the Java part only and not directly affect the
GSoC project, since it seems to focus mostly on a new front end, but
we think the plugin could add some features to it. (Maybe I could
create a small example page if you are interested)
I hope to hear from you wether you are interested and if so, what
parts you are interested in.
Also don't hesitate to ask if you have questions or need further
information.
Edo
Hello XWikiers,
do I have a possibility for a plugin to access the classes of another
webapp?
Can this other webapp maybe offer some services shareable to others?
(JNDI?)
thanks in advance
paul
Hi devs,
We've been tackling this proposal for some time, but we never took a
final decision on it. So, I propose that we do this switch as soon as
possible.
Changes:
- default encoding UTF-8 in the start_xwiki* scripts, xwiki.cfg and web.xml
- remove the LANG= environment variable from the start script, since
it's not needed
- add the encoding configuration for the mysql jdbc connection URL
(http://dev.mysql.com/doc/refman/5.0/en/connector-j-reference-charsets.html)
Implications:
- hsqldb instances will continue to work fine
- for mysql and other DB instances, either the DB will need to be
changed to work with the new encoding, or the wiki will have to be
changed back to 8859-1. If we append characterEncoding=UTF-8 to the
connection URL, then the storage will throw exceptions when trying to
store an incompatible character, thus admins will quickly notice the
problem and solve the issue, before users report loosing characters
after a while (since without this setting the characters are silently
transformed to '?' and this won't be noticed until the cache expires).
We need to highlight this change in the release notes and upgrade
instructions.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
