Hello,
We want to make an Excel Export in XWiki but we have lot of problem.
Actually we are trying to make :
· A renderer to user XWiki Rendering Tool => It's ok
· A printer to return Excel content => Have a doubt about this solution
· A template to take Excel Content (xpage=excel) et push into OutputStream with => Not run
Have you idea about this kind of need ?
To last step, i have try to use it :
$response.setContentType("application/ms-excel")
$response.setHeader("Content-Disposition", 'inline; filename="my_excel.xls"')
$xcontext.setFinished(true)
$response.getOutputStream().write($myexcelcontent)
------------------------------------------------
Lionel ZUBER | UMA - Equipe technique
Centre de Service Rhône-Alpes | France
T : +33 4 69 64 63 20 | M: +33 6 76 90 54 47
lionel.zuber(a)logica.com<mailto:lionel.zuber@logica.com> | www.logica.fr<http://www.logica.fr>
P afin de contribuer au respect de l'environnement,
merci de n'imprimer ce mail qu'en cas de nécessité
Think green - keep it on the screen.
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
Hi devs,
I'd like to introduce a Dashboard Application in a xwiki-platform/xwiki-platform-core/xwiki-platform-dashboard/ module.
It would contain the following pages:
1/ Main.Dashboard.xml (currently in XE's app)
2/ The pages making up the user dashboard (XWiki.UserDashboardPreferencesClass, XWiki.XWikiUserDashboardSheet) (currently in Admin app)
3/ A new page which will have the logic to choose to display the user dashboard or the main shared dashboard (currently this code is in Main.WebHome in XE's app)
Also I'd like to suggest introducing a Dashboard space and have all the above-mentioned pages in that space.
Dashboard.WebHome would contain 3/.
And Main.WebHome would simply do an include of Dashboard.WebHome.
Note that this would allow the following:
* Ability to cleanly document the Dashboard feature on extensions.xwiki.org and have it visible on enterprise.xwiki.org for example
* It goes in the direction of splitting our XE XAR in discrete application
* It groups together (functionally) a domain (dashboard) which means that if a user doesn't want the dashboard feature, we can simply not install it or remove it easily.
WDYT?
Thanks
-Vincent
Hi devs,
I've started investigating this. The documentation for Provider can be found here:
http://code.google.com/p/atinject/source/browse/trunk/src/javax/inject/Prov…
Here's we would define a provider:
@Component
public class MyProvider implements Provider<RoleToProvide>
{
@Inject <-- just to show that a provider is a component and be injected other components
private SomeRole role;
@Override
public RoleToProvide get()
{
… logic here to return a RoleToProvide instance…
}
}
And here's how you'd use it:
@Component
public class MyComponent implements MyRole
{
…
@Inject
private Provider<RoleToProvide> provider;
…
public void someMethod()
{
RoleToProvide instance = this.provider.get();
…
Rationale:
=========
* UC1: Useful to break cyclic dependencies in a cleaner way than having the ComponentManager injected, especially since the Provider can be reused since it's shared
* UC2: Useful to clean up code so that the logic to decide which implementation to return can be externalized in a Provider implementation. For example imagine you have a config property in xwiki.properties and based on it you wish to return a component with one hint or another. You could use a Provider for this.
* Allows us to be JSR330 compliant (not a very strong point but still an argument ;))
Default Provider
=============
When you ask to get injected a Provider if no Provider is defined for the Role you wish, you'll get injected a generic provider which simply does a lookup using the Component Manager. This allows to simply implement UC1.
WDYT?
Thanks
-Vincent
Hi guys,
I'm trying to write some groovy that uses an image thats in the current skin in a link. In this case its a delete page image, that links to a delete page URL:
[[image:${xwiki.getSkinFile('icons/silk/page_delete.gif')}>>${doc.getExternalURL('delete')}]]
The issue is that the getSkinFile call returns a relative URL, which ends up getting rendered in the final HTML as
<img alt="/xwiki/resources/icons/silk/page_delete.gif" class="wikimodel-freestanding" src="/xwiki/bin/download/Storyboard/fcg9aYKeaI6AVIjxpocO/%2Fxwiki%2Fresources%2Ficons%2Fsilk%2Fpage_delete.gif"></img>
Do you have any suggestions for how I can get access to one of the icons for use as an image for a URL?
Thanks,
Nigel
Hi guys,
In order to finish convert extensions.xwiki.org into a valid XWiki
Repository server (supported by Extension Manager) I need to put a
upgrade xwiki.org and add a jar file (mostly about REST interface).
Thing is I need to put the latest 3.3 snapshot version of this REST
module so I can see two solutions:
* upgrade to 3.2 and patch it with several new API needed by the module
* upgrade to latest 3.3 SNAPSHOT
pros 3.3
* more simple for me
* we can probably quickly come back to the current 3.1.1 if a blocking
issue is found until it's fixed
* I'm going to quickly update xwiki.org any time we find and fix a blocker issue
cons 3.3
* snapshot version on production
There is some things I'm not 100% sure:
* is there any modification of to the DB introduced in 3.3 not
compatible with 3.1.1 and not introduced in 3.2 ? I know id change has
not been committed yet
+1 for 3.3 SNAPSHOT (ok the pros/cons is a bit oriented ;)) if there
is not incompatible DB change
--
Thomas Mortagne
Hi there
I've got two different groovy classes in two different pages (lets say Widget and WidgetFactory), and in a third page I'm trying to call an instance of the WidgetFactory, getting it to create a Widget.
I've included the groovy code for both classes in the third page using the "wiki.parseGroovyFromPage(…" call, which works as I can successfully call methods on the widget factory.
However, calling the createWidget method on the factory produces an error, in that the WidgetFactory code doesn't know anything about Widgets (i.e. it doesn't know about the Widget class). Am I doing something wrong?
I would like to be able to modularise the code in some way. It doesn't matter if there are many different classes declared in the one page, or just one; as long as I can instantiate them, and they know about each other. This would be great as it will mean I can reuse these classes around a few different pages.
I've tried including the code using the include macro (outside the groovy block) , and using the xwiki.includeForm call (inside the groovy block), with no success.
Thanks,
Nigel
Hi devs,
Is there a documentation and a tool to clean XWiki XML files for commit.
I used to use the SVN Application to clean the XML and commit in the
sandbox for the contributed apps.
But the SVN app does not work with git (even with the SVN bridge as it
seems svnkit is not compatible), so I'm left to export to commit.
How do developers usually do that ?
Ludovic
--
Ludovic Dubost
Founder and CEO
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
We need a way for subservient stores such as FS attachments to get transactions from the main store so that it can know to rollback if there is an error in the main store.
In order to Cloud/DataNucleus store plug in seamlessly and function with FS attachments, FS attachments needs to be able to get transactions from the main store without knowing or caring what that main store is.
I propose this:
Add a new storage submodule: xwiki-platform-store-transactionprovider which provides this interface which extends javax.inject.Provider:
@ComponentRole
public interface XWikiTransactionProvider
extends Provider<StartableTransactionRunnable<? extends XWikiTransaction>>
{
// No additional functions, just the get() from Provider.
}
The default implementation for now will be a wrapper which picks out the real TransactionProvider based on what the main store is, as defined in xwiki.cfg.
This will allow code to get a transaction from the main store then get TransactionRunnables from the main store and use them with this transaction and be assured
that you won't be using a Hibernate TransactionRunnable with a Cassandra Transaction.
WDYT?
Caleb
Hi,
I had no luck on the users group, so I thought I would try my luck on the
devs group.
I would like to add the javascript below to my xwiki page.
Is this something that can easily be done?
If so please can you show me an example.
Thanks
Riaz
google.load('visualization', '1', {'packages':['table']});
function changeData(scorer) {
var whereClause = "";
if(scorer) {
whereClause = " WHERE 'Scoring Team' = '" + scorer + "'";
}
var queryText = encodeURIComponent("SELECT 'Scoring Team', 'Receiving
Team', 'Minute of goal' FROM 197026" + whereClause);
var query = new
google.visualization.Query('http://www.google.com/fusiontables/gvizdata?tq='
+ queryText);
query.send(getData);
}
function getData(response) {
var table = new
google.visualization.Table(document.getElementById('visualization'));
table.draw(response.getDataTable(), {showRowNumber: true});
See this for more info:
http://gmaps-samples.googlecode.com/svn/trunk/fusiontables/gviz_datatable.ht
ml
-----Original Message-----
From: users-bounces(a)xwiki.org [mailto:users-bounces@xwiki.org] On Behalf Of
Riaz
Sent: 28 October 2011 10:35
To: users(a)xwiki.org
Subject: [xwiki-users] JavaScript example
Hi,
I'm new to XWiki, and I would like some help on how to add JavaScript to my
pages.
I have looked at the example SkinExtensionsTutorial and can now do basic
JavaScript for example:
alert ("HelloWorld"); via the JavaScriptExtension.
I would like to add Google fusion tables to my Xwiki page an example of what
I am after is below with the JavaScript:
http://gmaps-samples.googlecode.com/svn/trunk/fusiontables/gviz_datatable.ht
ml
The JavaScript is shown below:
google.load('visualization', '1', {'packages':['table']});
function changeData(scorer) {
var whereClause = "";
if(scorer) {
whereClause = " WHERE 'Scoring Team' = '" + scorer + "'";
}
var queryText = encodeURIComponent("SELECT 'Scoring Team', 'Receiving
Team', 'Minute of goal' FROM 197026" + whereClause);
var query = new
google.visualization.Query('http://www.google.com/fusiontables/gvizdata?tq='
+ queryText);
query.send(getData);
}
function getData(response) {
var table = new
google.visualization.Table(document.getElementById('visualization'));
table.draw(response.getDataTable(), {showRowNumber: true});
How can I add this information to my Xwiki page.
Your help is much appreciated.
Best Regards,
Riaz
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
Hi devs,
I'd like to create the following modules in xwiki-platform to add a UI for the linkchecker feature:
xwiki-platform-linkchecker/
|_ xwiki-platform-linkchecker-ui/
|_ xwiki-platform-linkchecker-refresher/
where:
* xwiki-platform-linkchecker-ui/ will add a Tab in Main.AllDocs to list broken external links. It'll contain the livetable that you can see on http://www.xwiki.org/xwiki/bin/view/Admin/ExternalLinkStatus
* xwiki-platform-linkchecker-refresher/ will contain an EventListener listening to DocumentUpdatingEvent and remove all link states from the link state cache for the modified pages received as Events. This module will depend on the LinkChecker Transformation module located in xwiki-rendering.
Here's my +1
Thanks
-Vincent
Hello Devs,
As a XWiki admin, I installed the AdminTools extension
(http://extensions.xwiki.org/xwiki/bin/view/Extension/AdminTools). The
configuration check pages are very useful to verify a fresh install,
the export pages are priceless (especially the Admin.Export one)...
Of course, these pages are not very polished but they do the job.
Fortunately, this extension is maintained as a contribution in Github.
In the extension wiki, it would be fine to clearly mention that
"Import Export Application", "Monitoring Application", "XAR Diff
Application" are now included in the AdminTools (as it is for the
"Check Config And Indexes Application"). Maybe I miss one or two.
If you agree, I can do it.
By the way, I submitted a few days ago a pull request to add a new
ShrinkTrashBin page in AdminTools. Don't forget it.
Maxime
Hi devs,
I've started designing the new livetable macro as a XWiki Syntax 2.0 macro. I've brainstormed with Jerome this morning and here's what we came up with:
http://dev.xwiki.org/xwiki/bin/view/Design/LiveTable20Macro
Feedback most welcome. I can add more information if something isn't clear (as there's very little doc ATM).
Thanks
-Vincent
On 11/02/2011 06:51 AM, shouldbe q931 wrote:
> Has any testing been done with Oracle ?
Fixing the Oracle problems was one of my targets for this release, but
it's so hard to get a local working instance of Oracle 10g installed.
I'll spend more time on this after I finish my assigned workload for 3.3
> On Tue, Nov 1, 2011 at 4:12 AM, Sergiu Dumitriu<sergiu(a)xwiki.com> wrote:
>> The XWiki development team is proud to announce the availability of XWiki
>> Commons, XWiki Rendering, XWiki Platform, XWiki Enterprise and XWiki
>> Enterprise Manager 3.3 Milestone 1. Since we're getting closer to the end of
>> the 3.x cycle, there are fewer new features in this release, most of the
>> changes being internal. The highlights of this release are:
>>
>> * a preview version of the new class editor to be used in the Application
>> Within Minutes designer
>> * new Debian packages for XWiki
>> * a few extension manager improvements
>> * LDAP improvements
>> * improvements on uploading and downloading attachments, especially when
>> filesystem storage is enabled
>>
>> And on the developers' front:
>>
>> * script services for Application Manager and Wiki Manager
>> * cache improvements
>> * changes in the way XAR modules are packaged
>> * and the usual dependency upgrades and translation improvements
>>
>> See the full release notes at
>> http://www.xwiki.org/xwiki/bin/ReleaseNotes/ReleaseNotesXWikiEnterprise33M1
>> for more details.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Rights have different scopes in XWiki. Administration rights can only be
set on a space or wiki level, and any "admin" right set on a document
alone will be silently ignored. Programming rights are only considered
when set on the xwiki:XWiki.XWikiPreferences document, being ignored in
any other virtual wiki and at the space or document level.
Delete rights are a bit special as well. By default, the creator of a
document has delete rights on that document. Unlike the other rights
which default to true when no right is set, this one defaults to false.
So, by default, when no "delete" rights are set on the
document/space/wiki, only the creator of a document and administrators
are allowed to delete it.
Should we allow setting the delete right at the document level?
Personally, I'd say no, since it's a rare requirement for a non-creator
to be able to delete just one document. Space-level rights should be
enough, IMO.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi devs,
We need to decide on a technical name for the "Application Within
Minutes", i.e. the name of the platform module and the name of the
space that will hold the Application Within Minutes pages. For now I
committed my code in xwiki-platform-applicationWithinMinutes and I
used the "ApplicationWithinMinutes" space name but this is not
consistent with the way we named modules and spaces so far. Do you
have any suggestions?
We could use simply xwiki-platform-application, but it collides with
xwiki-platform-application-manager, and I don't think it's a good idea
to merge them. Is application manager still used? Is it going to be
replaced by the extension manager?
Thanks,
Marius
Hey community,
I spent some time trying to make PDF export work for CJK (Chinese,
Japanese, Korean) characters, and managed to get it working quite well.
Searching for some good open source fonts, I finally decided on the
following:
- CJK Unifonts (Linux re-packaging of the Arphic fonts)
- IPAGothic
- Baekmuk
The first one comes in two variants, serif (a.k.a. ming or song) and
script (regular script, kai), and has good support for Chinese, with
good, but not complete, support for Japanese, and no support for Korean.
It looks very good in both variants, but we should decide on one of
them. I uploaded samples on http://jira.xwiki.org/browse/XWIKI-7106 to
see how they would look.
***
Q1: Should Kai or Ming be used as the default export font for Chinese?
***
I'm far from being an expert here, but my opinion is that the Kai
variant, with it's handwritten look, is better suited for printed
material. Still, PDFs are also used on screen, be that a large computer
monitor or a handheld device, and on screen the legibility of the Ming
variant is better. One option that I like is to use Kai for normal text
and Ming for tt/code elements, as a kind of monospace.
The second font, IPAGothic, is centered on Japanese, so it has good
support for Japanese, some support for Chinese, and no support for
Korean. It is a sans-serif variant.
The third font, Baekmuk, brings support for Korean (laking from the
other two fonts), along with little support for some Chinese and
Japanese characters. This one comes in more variants, but only two are
complete enough to be considered, Batang as the serif equivalent, and
Gulim as the sans-serif equivalent.
***
Q2: Should Batang or Gulim be used for Korean?
***
My opinion is that the serif variant looks better on print, although
less readable. Still, I've seen Gulim much more often used in practice.
I attached two samples for this as well to the Jira issue.
***
Q3: Should the current FreeSerif font be used for non-CJK characters, or
the font face defined in the font specific to each language?
***
While I prefer FreeSerif for all English text, I've seen in practice
that the preferred solution is to use a bulkier font for numbers and
latin characters.
***
Q4: Does italics/oblique make sense for CJK characters?
***
The concept of Italics is defined only for latin-like characters, and no
font provides support for italics CJK. Still, Firefox does render
slanted characters for CJK text inside <em>. FOP, the rendering engine
used for generating PDFs, does not have support for automatically
slanting fonts that don't provide an italics variant, and will insist on
choosing a font that comes in an italics variant. So, this means that by
default any text that is emphasized in the wiki will not be displayed in
the PDF correctly (they would appear as # characters). There is a simple
solution, and that is to alter the font file so that is says that both
the regular and italic version of the font are in the file. Another
option is to actually provide an oblique version of the font, which
FontForge seems to be able to do quickly and with good results. Still,
this will double the size of the fonts, so I'd rather not provide italic
fonts if they don't actually make much sense for native CJK users.
Some other fonts that I looked at were:
* the Droid font used in Android devices, which is a sans-serif font IMO
not suited for print; its advantage would be that it provides a unitary
look for all CJK languages, less good looking, but more legible
* the Hanazono font, which has impressive support for all the characters
in CJK Unicode sets, but was created in a wiki way, so IMO it's not very
consistent throughout the whole spectrum, and not as esthetically
looking as the others
***
Q5: Should a less good looking, but smaller and more consistent font be
used? If yes, which one?
***
The Droid font is actually quite small compared to the others, and on
smaller font sizes it is more readable.
I would really appreciate some feedback on this topic.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
On 11/02/2011 01:45 AM, Yang Li wrote:
> ? 2011/11/2 12:00, Sergiu Dumitriu ??:
>>>> ***
>>>> Q1: Should Kai or Ming be used as the default export font for Chinese?
>>>> ***
>>>>
>>>> I'm far from being an expert here, but my opinion is that the Kai
>>>> variant, with it's handwritten look, is better suited for printed
>>>> material. Still, PDFs are also used on screen, be that a large
>>>> computer monitor or a handheld device, and on screen the legibility of
>>>> the Ming variant is better. One option that I like is to use Kai for
>>>> normal text and Ming for tt/code elements, as a kind of monospace.
>>>>
>>> As a Chinese, I strongly recommend *song* , the most poluar font, and we
>>> seldom use ming in official documents...
>>
>> Reading on Wikipedia I got the impression that there isn't a clear
>> distinction between Ming and Song, and some refer to the same thing
>> with both terms. Looking at the list of CJK fonts
>> http://en.wikipedia.org/wiki/List_of_CJK_fonts none of the fonts that
>> have Song in their name are under an open source friendly license, so
>> they can't be redistributed. Please take a look at the sample PDF and
>> see if it is acceptably similar to Song:
>> http://jira.xwiki.org/secure/attachment/23886/ming-over-freefont.pdf
> According to the wikipedia
> http://en.wikipedia.org/wiki/Ming_%28typefaces%29
> ------------------------------------------------------------------------
> The names Song (or Sung) and Ming correspond to the Song Dynasty
> <http://en.wikipedia.org/wiki/Song_Dynasty> when a distinctive printed
> style of regular script <http://en.wikipedia.org/wiki/Regular_script>
> was developed, and the Ming Dynasty
> <http://en.wikipedia.org/wiki/Ming_Dynasty> during which that style
> developed into the Ming typeface style.^[1]
> <http://en.wikipedia.org/wiki/Ming_%28typefaces%29#cite_note-kinkido-0>
> In Mainland China, the most common name is Song (the Mainland Chinese
> standardized Ming typeface in Microsoft Windows
> <http://en.wikipedia.org/wiki/Microsoft_Windows> being named SimSun). In
> Hong Kong <http://en.wikipedia.org/wiki/Hong_Kong>, Taiwan
> <http://en.wikipedia.org/wiki/Taiwan>, Japan
> <http://en.wikipedia.org/wiki/Japan> and Korea
> <http://en.wikipedia.org/wiki/Korea>, Ming is prevalent. In Hong Kong
> and Taiwan, "Song typeface" (??) has been used but "Ming typeface" (??)
> has increased currency since the advent of desktop publishing
> <http://en.wikipedia.org/wiki/Desktop_publishing>. Some type foundries
> <http://en.wikipedia.org/wiki/Type_foundry>^[2]
> <http://en.wikipedia.org/wiki/Ming_%28typefaces%29#cite_note-1> use
> "Song" to refer to this style of typeface that follows a standard such
> as the Standard Form of National Characters
> <http://en.wikipedia.org/wiki/Standard_Form_of_National_Characters>, and
> "Ming" to refer to typefaces that resemble forms found in the Kangxi
> dictionary <http://en.wikipedia.org/wiki/Kangxi_dictionary>.
> ------------------------------------------------------------------------
> Ming and Song (or Sung) is different indeed, and Song is popular in
> Mainland China while Ming is popular in HK, TW, or JP and so on. They
> are similar, however, Song has more sharp angles or corners than Ming,
> while Ming has smooth ones, illustrated in the following two
> pictures(Ming and Song):
>
> Actually, there seems to be both Ming and Song available according to
> http://en.wikipedia.org/wiki/Arphic_Public_License#Arphic_Public_License
> But I cannot find where to download the fonts...
Yeah, tell me about it, in the end I used the ones repackaged in
CJKUnifonts, which only provide UKai and UMing. After searching some
more I found their Song variant, but it's older and less complete than
the other two.
Anyway, thanks a lot for the feedback, you've been of great help.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
On 11/01/2011 11:07 PM, Yang Li wrote:
> ? 2011/11/2 10:46, Sergiu Dumitriu ??:
>> Hey community,
>>
>> I spent some time trying to make PDF export work for CJK (Chinese,
>> Japanese, Korean) characters, and managed to get it working quite well.
>>
>> Searching for some good open source fonts, I finally decided on the
>> following:
>>
>> - CJK Unifonts (Linux re-packaging of the Arphic fonts)
>> - IPAGothic
>> - Baekmuk
>>
>> The first one comes in two variants, serif (a.k.a. ming or song) and
>> script (regular script, kai), and has good support for Chinese, with
>> good, but not complete, support for Japanese, and no support for
>> Korean. It looks very good in both variants, but we should decide on
>> one of them. I uploaded samples on
>> http://jira.xwiki.org/browse/XWIKI-7106 to see how they would look.
>>
>> ***
>> Q1: Should Kai or Ming be used as the default export font for Chinese?
>> ***
>>
>> I'm far from being an expert here, but my opinion is that the Kai
>> variant, with it's handwritten look, is better suited for printed
>> material. Still, PDFs are also used on screen, be that a large
>> computer monitor or a handheld device, and on screen the legibility of
>> the Ming variant is better. One option that I like is to use Kai for
>> normal text and Ming for tt/code elements, as a kind of monospace.
>>
> As a Chinese, I strongly recommend *song* , the most poluar font, and we
> seldom use ming in official documents...
Reading on Wikipedia http://en.wikipedia.org/wiki/Ming_%28typefaces%29 I
got the impression that there isn't a clear distinction between Ming and
Song, and some refer to the same thing with both terms. Looking at the
list of CJK fonts http://en.wikipedia.org/wiki/List_of_CJK_fonts none of
the fonts that have Song in their name are under an open source friendly
license, so they can't be redistributed. Please take a look at the
sample PDF and see if it is acceptably similar to Song:
http://jira.xwiki.org/secure/attachment/23886/ming-over-freefont.pdf
>> The second font, IPAGothic, is centered on Japanese, so it has good
>> support for Japanese, some support for Chinese, and no support for
>> Korean. It is a sans-serif variant.
>>
>> The third font, Baekmuk, brings support for Korean (laking from the
>> other two fonts), along with little support for some Chinese and
>> Japanese characters. This one comes in more variants, but only two are
>> complete enough to be considered, Batang as the serif equivalent, and
>> Gulim as the sans-serif equivalent.
>>
>> ***
>> Q2: Should Batang or Gulim be used for Korean?
>> ***
>>
>> My opinion is that the serif variant looks better on print, although
>> less readable. Still, I've seen Gulim much more often used in
>> practice. I attached two samples for this as well to the Jira issue.
>>
>> ***
>> Q3: Should the current FreeSerif font be used for non-CJK characters,
>> or the font face defined in the font specific to each language?
>> ***
>>
>> While I prefer FreeSerif for all English text, I've seen in practice
>> that the preferred solution is to use a bulkier font for numbers and
>> latin characters.
> FreeSerif is good.
OK, noted.
>>
>> ***
>> Q4: Does italics/oblique make sense for CJK characters?
>> ***
>>
>> The concept of Italics is defined only for latin-like characters, and
>> no font provides support for italics CJK. Still, Firefox does render
>> slanted characters for CJK text inside <em>. FOP, the rendering engine
>> used for generating PDFs, does not have support for automatically
>> slanting fonts that don't provide an italics variant, and will insist
>> on choosing a font that comes in an italics variant. So, this means
>> that by default any text that is emphasized in the wiki will not be
>> displayed in the PDF correctly (they would appear as # characters).
>> There is a simple solution, and that is to alter the font file so that
>> is says that both the regular and italic version of the font are in
>> the file. Another option is to actually provide an oblique version of
>> the font, which FontForge seems to be able to do quickly and with good
>> results. Still, this will double the size of the fonts, so I'd rather
>> not provide italic fonts if they don't actually make much sense for
>> native CJK users.
>>
> In fact, Chinese people use bold font to emphasize (hei), not italics,
> and we seldom use italics.
OK, so this means that italics doesn't make sense, which is good.
The bad news is that FOP doesn't support making characters bold when
there's no predefined font, either, but it won't fall back to a font
that does provide bold. This means that bold text will appear the same
way as regular CJK.
I tried to generate a bold font from FontForge, but it fails with an
error message: "some fragments did not join". So, our hope is that FOP
will implement this feature soon.
>>
>> Some other fonts that I looked at were:
>> * the Droid font used in Android devices, which is a sans-serif font
>> IMO not suited for print; its advantage would be that it provides a
>> unitary look for all CJK languages, less good looking, but more legible
>> * the Hanazono font, which has impressive support for all the
>> characters in CJK Unicode sets, but was created in a wiki way, so IMO
>> it's not very consistent throughout the whole spectrum, and not as
>> esthetically looking as the others
>>
>> ***
>> Q5: Should a less good looking, but smaller and more consistent font
>> be used? If yes, which one?
>> ***
>>
>> The Droid font is actually quite small compared to the others, and on
>> smaller font sizes it is more readable.
>>
> I prefer normal fonts, because nowadays we usually use a browser and
> large display @@..
>>
>> I would really appreciate some feedback on this topic.
>
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hello everybody,
I have created a JIRA macro using groovy. This macro allows to query JIRA
(using issue keys or using JQL) in order to obtain desired information.
The information can be displayed in several ways (tables, list, enum)
depending on what the user wants.
Also, this macro supports other several options in order to suit users'
needs.
I would like to contribute it and I also request if the community can host
it on github. Everyone interested in it could contribute to it
My github ID is sorinello. https://github.com/sorinello
Thanks, and I hope you will use this macro on a daily basis :)
Regards,
Sorin B.
The XWiki development team is proud to announce the availability of
XWiki Commons, XWiki Rendering, XWiki Platform, XWiki Enterprise and
XWiki Enterprise Manager 3.3 Milestone 1. Since we're getting closer to
the end of the 3.x cycle, there are fewer new features in this release,
most of the changes being internal. The highlights of this release are:
* a preview version of the new class editor to be used in the
Application Within Minutes designer
* new Debian packages for XWiki
* a few extension manager improvements
* LDAP improvements
* improvements on uploading and downloading attachments, especially when
filesystem storage is enabled
And on the developers' front:
* script services for Application Manager and Wiki Manager
* cache improvements
* changes in the way XAR modules are packaged
* and the usual dependency upgrades and translation improvements
See the full release notes at
http://www.xwiki.org/xwiki/bin/ReleaseNotes/ReleaseNotesXWikiEnterprise33M1
for more details.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi,
A little week-end fun which can turn out quite useful. I've coded a Google
Apps Integration module.
It allows to:
- search for a document in your Google Docs instance and upload it to an
XWiki page.
- to click on an "edit link" (like webdav) to open an attachment in Google
Docs, then edit it (in another tab), and then in one click retrieve it to
resave it in XWiki.
- the latest feature supports overwriting a document with the same name in
your Google Docs instance or to create a new separate file.
The extension is here and the code in GitHub:
http://extensions.xwiki.org/xwiki/bin/view/Extension/GoogleAppsIntegration
It's only using a XAR + Groovy and does not need any templates modification
(the attachment zone is enhanced by a JSX).
Some stuff that could be added:
- automatically give more rights for others to edit
- send a Wiki content or a Wiki table to Google Docs and resave in the Wiki
page (I leave that to XWiki rendering specialists :))
- additional UI feature to possibly use a Lightbox to launch the editing
and the edit screen
Ludovic
--
Ludovic Dubost
Founder and CEO
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Hi devs,
I've created a new FAQ application.
It's currently available from http://www.xwiki.org/xwiki/bin/view/FAQ/WebHomeNew
(it's linked from the old one: http://www.xwiki.org/xwiki/bin/view/FAQ/WebHome)
The reason I rewrote it is because I think FAQs are important and that we're not using it enough
Here's how I think it could work out:
* If a user has a question he/she should verify if it's already in the FAQ. If not then he/she should post a message for the XWiki Mailing List/Forum.
* The strategy is then for people who know the answer to create a new FAQ entry about the question and reply in the mail with the link to the new FAQ Entry
In this manner we will quickly enrich this FAQ database.
Of course the FAQ answers should be as short as possible and point to existing docs (if those docs don't exist they should be updated/created).
Basically I see FAQ as entry points to our documentation, from the point of view of someone asking questions of the type "how do I….".
Thus there can be several FAQ entries all having the same link to the documentation.
WDYT?
Thanks
-Vincent
PS: As you can see I have only 4 entries right now since we need to migrate exisitng FAQ entries:
- use a good page name
- rewrite them in XWiki Syntax 2.0
- verify their accuracy
- update docs where needed
Maybe we should have a FAQ day to work on that?