I've improved slightly the translation app at http://l10n.xwiki.org
It now supports sorting per the translation keys both for the output
(the file will be nicer looking) and when translating, which will make
it easier to translate keys that correspond to the same module together.
In terms of status the great news is that we have the following language
completed:
- English (obviously)
- French
- German
- Romanian
Translators might want to have a look at the "outdated" translations.
These are the already translated keys that have in the mean time changed
in the english language.
Outdated translations are available from the OutDated link of your language.
Review is also important. It gives a second chance to check
translations. Also an already translated key that has been changed and
not reviewed will not be taken into account until it is reviewed.
Review is accessible from the Review link of your language.
In any case I'm really happy with what we have achieve. We now have 4
complete languages and we can keep track of the changes.
We'll make sure this hard work is going to make it in 1.8 final release.
Thanks to all for the contribution and we welcome other volunteers to
tackle the other languages.
Ludovic
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Hi devs,
Someone on the list asked how create a link and an image pointing to a
relative reference (that he got using one of XWiki's API since they
all return relative URL). We currently don't have a good solution for
this and I'd like to propose a solution.
For links
=======
Make the usage of a prefix that specifies what comes next a generic
feature. We have the following needs:
* link to a URL
* link to a relative path
* link to a document
* link to a mailto
* link to an attachment
I propose the following syntax:
[[label>>prefix:value]]
where prefix = one of http:, path:, doc:, mailto:, attach:
In addition I propose that when there's no prefix or if the prefix is
an unknown prefix then to consider that the reference is a reference
to a document (equivalent to doc:).
Pros:
* Generic
* Ability to add more prefixes later on (for ex ftp:)
* Ability to have virtual wikis which have "reserved" names such as
"doc", "http", "ftp", "mailto", etc since you can write
[[doc:doc:Space.Page]]
* Ability to write shorthand for documents in the text, such as: "This
is a link doc:Space.Page"
* Ability to reference relative paths and write stuff such as
{{velocity}}[[label>>path:$xwiki.getURL(something)]]{{/velocity}}
For images
=========
* Similar to links add the ability to add prefixes in a generic way.
We have the following needs:
* image where the source is at a URL
* image where the source is at a relative path
* image where the source is in a document
I propose the following syntax:
image:prefix:value
where prefix = one of http:, path:, attach:
Note that we already support image:http://... so the proposal here is
simply to make it generic.
In addition I propose that when there's no prefix or if the prefix is
unknown then to consider that the image is to be found in a document
(equivalent to attach:).
Same pros as above.
Here's my +1
WDYT?
Thanks
-Vincent
Hi,
I'm an Computer Science Undergraduate who is currently undergoing training
and engaged n the field of Open Source SOA products n development. I've
recently done project work in the area of WS Security (WS [Web Services]
Policy derivation from SOAP messages n some OSGI component implementatons
around that..) and have fair knowlege on WS security implementations. Also
also have an good understanding in Apache Axis2 Engine and been working on
Apache Axis2 Engine developing Ruby Services deployment using JRuby frame
work..
I would pretty much like to participate in a XWiki GSoc project for 2009 as
i see this as a great opportunity to expand my understanding in this field
and as a great learning experience. I had a look at previous 2008 xWiki
Gsoc Ideas,Devs list issues and some jiras and i gained interest in doing
some work in xWiki Core. I was particularly interested in ideas such as SAML
Authentication (Reported @ xWiki JIRA by Sergiu
Dumitriu<http://jira.xwiki.org/jira/browse/XWIKI-402>) , Support for
AJAX Calls (Reported @ xWiki JIRA by Sergiu
Dumitriu <http://jira.xwiki.org/jira/browse/XWIKI-641> ) , Xwiki Web
Services integration , and would like to know whether aforementioned work
(/proposals) are still available. However i would also be open to any other
ideas that will be put forward by XWiki org and would like to hear about
that too.
BTW i still don't know whether this is too early or not to ask for project
ideas n stuff ,but am certainly hoping to work with you guys if all goes
well .I'm still new to XWiki engine and it's aspects but i am willing to,
learn and have a good run on xWiki. Your feedback regarding this is very
much appreciated..Thnx in advance
.
Regards,
Udayanga Shaminda Wickramasinghe
The XWiki development team is pleased to announce the release of XWiki
Enterprise 1.8 RC 2.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
This is the second Release Candidate for the 1.8 version.
Changes from 1.8RC1:
Main changes:
* new "useravatar" macro for 2.0 syntax
* Improvements on 1.0->2.0 syntaxes convertion
* Add ability to configure xwiki to use the XWiki Syntax 2.0 as
default when creating new pages
* Bugs fixed in XWiki 2.0 syntax rendering.
* Upgrade to groovy 1.6 final.
* Update french translations
* Update german translations
* Update spanish translation
Important bug fixes:
* XWIKI-3228 - Error while saving xwiki 2.0 documents containing anchor links
* XWIKI-3242 - Entering an empty link makes the rendering blow up
* XWIKI-3252 - Cannot view documents in other languages than the
default when in multilingual mode and when using XWiki Syntax 2.0
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise18RC2
Note that general goals for XWiki Enterprise 1.8 are:
* Office Importer
* New Blog
* REST API
* Finish new rendering/syntax
* Finish new WYSIWYG
* French XE
* MediaWiki import
Thanks
-The XWiki dev team
hi
i was wondering if is it possible to have the sources of xwiki
entreprise
as netbeans project or eclipse project (the links to the svn ae dead)
i can't get any of the links to the repositories
please could you help on this one i really need the sources of xwiki
thank you very much
--
View this message in context: http://n2.nabble.com/xwiki-enterprise-web-sources-tp2414508p2428141.html
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi guys,
Proposal: create a new bridge called WikiAccessBridge whose purpose is,
for now, to get the temporary directory's location.
Reason: in my ChartMacro I need a temporary folder for storing images,
and then sending them to the output.
I'm thinking of providing two methods:
File getTemporaryDirectory() - to get the directory as a File, thus
having the ability to write files within it
URL getAttachmentURL(String fileName) - to get a newly created file as a
web URL (e.g: http://localhost/my_newly_created_temporary_file.png)
I plan to put the specifications of the bridge within org.xwiki.bridge
and the implementation within com.xpn.xwiki
WDYT?
Tnx,
Dan
jvdrean (SVN) wrote:
> Author: jvdrean
> Date: 2009-03-03 23:40:14 +0100 (Tue, 03 Mar 2009)
> New Revision: 17211
>
> Added:
> platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/xwikiexplorer/
> platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/xwikiexplorer/xwikiexplorer.js
> Modified:
> platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/xwiki.js
> Log:
> XWIKI-3287 : Provide a tree widget allowing to browse a XWiki farm (wikis>spaces>pages>attachments)
>
> First version of XWikiExplorer widget.
> +constants: {
> + /**
> + * Current wiki.
> + */
> + currentWiki: "$context.getDatabase()",
>
> + /**
> + * Main wiki.
> + */
> + mainWiki: "$context.getMainWikiName()",
This could make the file hard to cache in multiwiki mode using paths as
identifiers, since the JS will have the same address for all wikis.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi devs,
I would like to release XE 1.8RC2, it's mainly a bufixing/improvement
release as will be the RC3 before 1.8 final.
Here is my +1.
--
Thomas Mortagne