Isn't printrun just a version/edition id?
But couldn't you still put this in the edition field?
E.g.:
1st edition, 20th printing.
This would mean the ordinals (-st, -th) would need to be entered
manually in the Zotero field, but that's not too bad. Can you provide
example citations that show what the citations look like? Preferably
in English, but I can make sense of the citation in Persian if need
be.
- Avram
But couldn't you still put this in the edition field?
E.g.:
1st edition, 20th printing.
This would mean the ordinals (-st, -th) would need to be entered
manually in the Zotero field, but that's not too bad. Can you provide
example citations that show what the citations look like? Preferably
in English, but I can make sense of the citation in Persian if need
be.
- Avram
For some reason, I thought that the is-numeric test would help here,
but now I see that it will return true for both "3" and "volume 3,
print 17", so we can't use that to determine whether to append
"edition", or "volume", or "printing".
Can the CSL gurus offer any advice on this?
By the way, does the citation processor handle the Arabic (۱۲۳...)
numerals correctly?
Avram
By the way, does the citation processor handle the Arabic (۱۲۳...)
numerals correctly?
Avram
I think this might be part of the functionality added for the
NSF-specific version of Zotero that was created. Don't know anything
about the details, and I can't help there.
I very much hope that Dan can offer some guidance-- it would be good
to know that there is a real, successful attempt to run the Zotero
client and server in another, quite different, environment. And maybe
you could produce some more documentation on how you've managed to set
things up, for future implementers' reference.
Abbas also wrote:
>> By the way, does the citation processor handle the Arabic (۱۲۳...)
>> numerals correctly?
> No it doesn't. And it is not necessary until numbers are stored as European
> numerals. BTW I've implemented a converter in NLAI translator to convert
> Arabic numeral to European when necessary to ensure that numbers are always
> stored correctly (https://gist.github.com/1015122)
Interesting. How do you handle converting back to Arabic numbers in
styles? I suppose you could define them as the long form of the number
terms, but that's still a bad solution. This might still need
attention in a future version of CSL.
Avram
The CSL specification is pretty clear on this, with an example even.
Can someone explain the decision to go with this behavior?
Avram
Yes, and those tables aren't meant to be used for anything else for the
time being.
>>>Does anybody ever used "custom fields" in Zotero or knows how to implement
>>> them?
>>
>> I think this might be part of the functionality added for the
>> NSF-specific version of Zotero that was created.
>>
> Yes, and those tables aren't meant to be used for anything else for the time being.
I conclude that no custom fields can be added to any item type. Maybe
I can modify the original schema in "userdata.sql" and "schema.js" by
inserting some "alter table" statements. I will give it a try. Using
edition field may cause problems with localization.
>>> By the way, does the citation processor handle the Arabic (۱۲۳...)
>>> numerals correctly?
>> No it doesn't. And it is not necessary until numbers are stored as European
>> numerals. BTW I've implemented a converter in NLAI translator to convert
>> Arabic numeral to European when necessary to ensure that numbers are always
>> stored correctly (https://gist.github.com/1015122)
>Interesting. How do you handle converting back to Arabic numbers in
>styles? I suppose you could define them as the long form of the number
>terms, but that's still a bad solution.
I've modified the source code and in "integration.js" just before
inserting citations and bibliography into the Word document I test
language field of items(using item_ids) and if it is "fa" I convert
commas, semicolons, ... to Persian and make its direction right to
left. I could convert numerals too but MS Word handles it itself.
Could not use long form of numbers yet.
Using custom fields will break syncing and potentially break Zotero
upgrades. That's what I mean when I say they're not meant to be used
right now.
Abbas, I gather, is apparently part of a workgroup in Iran that is
implementing a local version of Zotero's client and server. Thus they
may well be modifying the server as well to maintain syncing. It will
of course break syncing with zotero.org, and upgrades as well, but
they'd presumably be committing to maintaining a customized fork of
the project.
I personally think that this is a very interesting and positive
development-- more in-depth experimentation like may well drive the
development useful and unexpected new features.
Avram
Do you mean that there IS some way to add a custom field (using
customFields table) to 'book' item type?
> On Wed, Jun 22, 2011 at 9:58 PM, Avram Lyon <ajl...@gmail.com> wrote:
> Abbas, I gather, is apparently part of a workgroup in Iran that is
> implementing a local version of Zotero's client and server.
Actually there are two workgroups and I am with the one that is
working on client side. We will contact people who are working on
server. But for now our priority is to release a version of zotero
with RTL and Persian support including Persian user interface,
documentation, national library translator and a website to
communicate with users. Since there is no free reference manager
software with complete RTL and Persian support I guess Zotero will
become so popular in Iranian universities.
Why should this be a separate release (which, by the way, cannot be
called "Zotero", which is a registered trademark of George Mason
University�see http://www.zotero.org/support/terms/trademark for more
information�and won't be able to benefit from Zotero support) rather
than patches to the core release?
Dear Dan, I appreciate your suggestion.
Practically we've sent some parts of our work to you and eventually we
will submit every part of code that we've changed. We should convince
you to apply the changes and this is not possible unless our code is
mature enough. So any separate release will be temporary and of course
we will bound ourselves to the license.