fair enough - I think mostly we're on the same page - and as soon as it becomes clear to me that a user is referring to an issue that doesn't exist or can't be replicated in Zotero I'll tell her to go to talk to Mendeley support - I certainly don't investigate Mendeley bugs.
But in the case of Vincent he was trying to understand how to modify csl styles, which I think is something that makes sense to support and encourage (not least because I've still not completely given up hope that we'll at least end up with some styles or fixes supplied from the commercial people - in the case of Papers that actually seems to be the case judging by the recent exchange over on xbiblio).
I don't know who's who here, but let me tell you something Dan Stillman. I'm a Master degree student and I am not decided yet which reference software I will adopt, thus I am in the decision process to choose which one I'll finally consider. I have been led to think Mendeley might be interesting, but while experiencing difficulties with referencing and further discovering limits in comunity support, I am now thinking that it's a real down point for Mendeley...
If I ended up on Zotero's forum, it's because while trying to frenchify APA 6th Edition referencing style, I tried to contact Richard Karnesky, contributor on APA 6th Ed. style, and he personally suggested I would come on Zotero's forum for some help. So here I am. At first I didn't think it was a Mendeley-related problem, I tought I had a CSL problem. Helpfully, mronkko, Gracile and adamsmith came to support and try to solve this issue. It is while discussing that we ended up confirming it was a mendeley-issue.
To conclude this final post, let me just say that as a higher education student exploring tools for referencing, after this experience, I'm quite more likely to promote high quality community support from Zotero rather than Mendeley's. So thank you mronkko, Gracile and adamsmith for providing evidence that Zotero comunity is a major advantage over Mendeley.
I hope I made clear I'm very thankful here, and please do not consider me as a "Mendeleyer", because I'm not, I'm just exploring limits...and discovering the power of a comunity which you can count on!
Vincent: That's great to hear, and to clarify, I wasn't trying to make you feel unwelcome. We've just had a number of threads here where it wasn't revealed until many posts in that the person was using Mendeley and was asking about problems that didn't occur in Zotero. (I'm sure this happens in part because people aren't aware that CSL issues can be program-specific, and we should probably do a better job of communicating that.) In any case, feel free to post other questions here as long as you've tested first in Zotero—as I said above, we're happy to help.
Thank you Dan Stillman for these words, and Happy New Year!
I would have a last and final question which I'm sure could help any other Zotero user who are working with CSL files to better understand CSL files achitecture.
My question: What line should I add if I want line 48 to be translated within my script? What I mean is that I want to apply something like an IF command for "month" that would apply a modification for a french term. Something similar to the "Term" section that could change reference within the whole script
So, is there an IF or whatever command line function to add that would apply a french version for months? Even if I must add 12 command lines, one for each month, that would be OK.
So where and how do I apply such a command line inside my CSL script??
I don't understand the question - could you provide an example of what you want to do?
If you just want to change the formatting for one month (e.g. abbreviate septiembre as spt. instead of sep. or so) you can also do that in the terms section of the style - see. e.g. the MLA style which re-defines all month abbreviations.
even if default-locale is set to "fr-FR", for reason which I won't explain here, it doesn't translate to french. SO this is why I want to manually apply a command line that would translate months inside my script itself. To do so, there must be a line to add somewhere in the CSL script to do so. I will probably have to add 12 lines, one for each month. Is it possible?
But in the case of Vincent he was trying to understand how to modify csl styles, which I think is something that makes sense to support and encourage (not least because I've still not completely given up hope that we'll at least end up with some styles or fixes supplied from the commercial people - in the case of Papers that actually seems to be the case judging by the recent exchange over on xbiblio).
If I ended up on Zotero's forum, it's because while trying to frenchify APA 6th Edition referencing style, I tried to contact Richard Karnesky, contributor on APA 6th Ed. style, and he personally suggested I would come on Zotero's forum for some help. So here I am. At first I didn't think it was a Mendeley-related problem, I tought I had a CSL problem. Helpfully, mronkko, Gracile and adamsmith came to support and try to solve this issue. It is while discussing that we ended up confirming it was a mendeley-issue.
To conclude this final post, let me just say that as a higher education student exploring tools for referencing, after this experience, I'm quite more likely to promote high quality community support from Zotero rather than Mendeley's. So thank you mronkko, Gracile and adamsmith for providing evidence that Zotero comunity is a major advantage over Mendeley.
I hope I made clear I'm very thankful here, and please do not consider me as a "Mendeleyer", because I'm not, I'm just exploring limits...and discovering the power of a comunity which you can count on!
Vincent
I would have a last and final question which I'm sure could help any other Zotero user who are working with CSL files to better understand CSL files achitecture.
Here is my PasteBin link: http://pastebin.com/QHEBmVcg
Here are lines 43 to 56
<if type="webpage">
<group delimiter=" ">
<text term="retrieved" text-case="capitalize-first" suffix=" "/>
<group>
<date variable="accessed" suffix=" ">
<date-part name="day" suffix=" "/>
<date-part name="month" text-case="lowercase" suffix=" "/>
<date-part name="year"/>
</date>
<text variable="year-suffix"/>
</group>
<text term="from"/>
<text variable="URL"/>
</group>
</if>
My question: What line should I add if I want line 48 to be translated within my script? What I mean is that I want to apply something like an IF command for "month" that would apply a modification for a french term. Something similar to the "Term" section that could change reference within the whole script
</term>
<term name="retrieved">repéré le</term>
<term name="from">à</term>
<term name="in">dans</term>
<term name="presented at">présenté à</term>
<term name="no date">sans date</term>
<term name="edition">édition</term>
</terms>
So, is there an IF or whatever command line function to add that would apply a french version for months? Even if I must add 12 command lines, one for each month, that would be OK.
So where and how do I apply such a command line inside my CSL script??
Thank you all Zotero CSL experts,
Vincent
If you just want to change the formatting for one month (e.g. abbreviate septiembre as spt. instead of sep. or so) you can also do that in the terms section of the style - see. e.g. the MLA style which re-defines all month abbreviations.
even if default-locale is set to "fr-FR", for reason which I won't explain here, it doesn't translate to french. SO this is why I want to manually apply a command line that would translate months inside my script itself. To do so, there must be a line to add somewhere in the CSL script to do so. I will probably have to add 12 lines, one for each month. Is it possible?
As adamsmith said, you can redefine month terms just like any other term:
<locale xml:lang="en">
<terms>
<term name="month-01">janvier</term>
...
</terms>
</locale>
What was missing was the correct formulation: <term name="month-01">janvier</term>
With your help, I succeded in translating months in french..
Thank you all, and once again, I confirm Zotero is the best.
Vincent