request for permission to create wiki pages

Hi.
I would like to contribute Slovenian translations to existing wiki pages, but do not have the permission to create new pages.
Looking forward to your reply,
Miha.
  • You just need to make a wiki account (which is separate from the main Zotero accounts):
    https://www.zotero.org/support/dev/documentation

    Thanks for your help!
  • I have - I've registered as miha114 - but I do not see the 'create page' link for non-existing pages.
  • Here is a print screen from my browser: https://www.dropbox.com/s/y1ns488epcjdn5i/scrimg_2017-09-21_13-52-48.png?dl=0
    I'm using Firefox on Linux btw.
  • Indeed, it seems you've not the permission to create new pages. @fcheslack or @dstillman can change this.
    (I've created the page btw.)
  • (this is by design. There was too much spam on the wiki. Can usually handles/grants these requests quickly)
  • (Sorry for the bad information.)
  • @adamsmith Ok. I've guessed as much myself. The documentation does not mention whom to contact to get the permission nor that permission should be requested for that matter. I do admit to not searching the documentation very thoroughly though.
    My next question then is where/from whom do I request the necessary permissions? Should I make this request in the Google group (zotero-dev)?

    @Gracile: Thank you for your kind gesture. Unfortunately I am unable to edit the page you've made. When I click (un-logged) on the 'Edit this page' link, I get redirected to the login page. When I do that the page reloads without the 'Edit' link. I can view source and that is all.

    @bwiernik: No sweat. I've read the instructions you've pointed me to and I've understood them in exactly the same way.
  • posting here is/was exactly right.
  • :-) Thank you.
  • (It explains how to request permission here, but it's also supposed to explain that on the registration page and show an Edit This Page in all cases — that's just currently broken. Sorry for the confusion.)

    I've given you write access, but I'm actually not sure it's worth working on translations of the wiki pages. We're considering removing the localized wiki pages altogether, since it's basically impossible for them to stay up to date — right now we still need to update much of the English documentation for 5.0, so it wouldn't even make sense to try to translate a lot of the current documentation. Honestly, I think keeping the English documentation current and then letting people use machine translation (e.g., translation in Google Chrome) makes more sense.

    For communities that want to maintain updated documentation in other languages, I think hosting it on a separate platform (which we could link to) may be better, because that could be more limited in scope and maintained as a complete entity, without dealing with the slow drift away from reality on lots of individual pages that we'd get on the wiki.

    (It's also much more important to keep the translations in the actual software on Transifex up to date (though Slovenian is at 95%, which is great).)
  • I understand your point and you're right that it's almost impossible to have localized versions up to date. Still, there are useful in my opinion (because they're not entirely outdated).

    Would it be possible to automatically add a visible message to a localized page which would be older than its English equivalent to warn that the content could be out of date (the minor vs major edit checkbox could also help here)?

    At least, localized wiki pages which deal with important content (data, backup, frequently asked questions…) should be kept. Tutorial-like content could be removed (librarians are doing that very well).

    How can I remove some pages? I assume only an admin can do that butthis one, for example, should be deleted…

    [in any case, I'd like to save all the translated content before you remove it!]
  • edited September 26, 2017
    @dstillman : Thank you for the granted permission and the clarifications. I apologize for the delay in my response - job and family-related reasons.

    I've decided to go ahead and add a translation even if it is going to be there just for a short while.

    I would like to second Gracile's opinion about the usefulness of localized page versions. I am also a bit skeptical about the quality of machine translations at least from English into Slovenian. Some languages are easier to 'map' for machine translations than others. The English to Slovenian translations on Google Translate are way better than they have been even a couple years ago, but you still get a text that is a bit on the wonky side: some words are incorrectly translated, word order follows the original which is in some cases less than optimal for Slovenian ... A computer savvy user can get around that or to be more precise, they would simply click to the English version which, I guess, supports the position that localizations are not crucial. In my opinion, though, they add //something// to the project, a feeling that non-English languages matter (to the project; I'm not sure this comes across the right way, but at the moment I am not able to express it better) ...

    PS. I've also encountered weird bug: I was unable to post the changes to the page from my Firefox browser. After I've added even a single character in the textbox, the buttons under it (Save, Preview, Cancel) went dead, i.e. the cursor would not change on mouseover and clicking the buttons did nothing. Then I've tried Brave browser and the interface worked as expected in that one.
  • right now we still need to update much of the English documentation for 5.0
    @dstillman, the documentation wiki currently has the warning "We're in the process of updating the documentation for Zotero 5.0. Some documentation may be outdated in the meantime. Thanks for your understanding.". There isn't a way to mark individual pages as being updated for 5.0, is there?
  • edited November 13, 2017
    There isn't a way to mark individual pages as being updated for 5.0, is there?
    I've removed that warning from the header and added it to each individual page (minus some that I've cleared manually), so it's now possible to remove from pages individually.
  • I've gone through about half of the documentation to check it and bring it up to date.

    The list of still-to-be-done pages is here:
    https://www.zotero.org/support/documentation_update_z5
  • Okay, all of the English-language documentation should be up to date with the exception of (1) screencasts, (2) client coding/extension developer documentation, and (3) translator coding documentation.

    Most of the screencasts are very out of date. I'm not sure how confusing they are to new users to leave up until someone is able to record new ones.

    @adamsmith Could you review the remaining translator pages linked at https://www.zotero.org/support/documentation_update_z5 and determine if any more should be removed or updated?
  • Thanks for doing this. Quick run-through:


    https://www.zotero.org/support/dev/technologies -- I'd nominate for deletion. We should just point people to proper resources for CSS Selectors, Xpaths, and Regex.
    https://www.zotero.org/support/dev/translators/coding -- Pretty much up to date, I believe
    https://www.zotero.org/support/dev/translators/testing -- up to date with the exception of running tests. Not sure what a good way of doing that locally is now @adomasven thoughts on that?
    https://www.zotero.org/support/dev/translators/scaffold -- Needs updating (pretty urgently; this one is high on my agenda)
    https://www.zotero.org/support/dev/translators/connectors -- Nominate for deletion. There are no differences anymore
    https://www.zotero.org/support/dev/translators/priority -- Up to date; nothing has change her.
  • edited December 7, 2017
    Do you have good resources for CSS Selectors, Xpaths, and Regex to link to? and what are your thoughts regarding the screencasts?
  • edited December 7, 2017
    CSS: I always use the W3Schools one https://www.w3schools.com/cssref/css_selectors.asp although people hate W3Schools. The MDN one is here but i find it much less readable: https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Selectors

    Xpaths: Maybe https://www.liquid-technologies.com/xpath-tutorial (all very XML focussed, but that's obviously their main purpose)

    Regex: A ton of these, all good. This is all in one page which I like: https://github.com/zeeshanu/learn-regex/blob/master/README.md

    And no other thought on the Screencast than that I agree that in their current state they're doing more harm than good.
  • edited December 11, 2017
    @adamsmith Translator tester is available when building the connectors with the debug flag for Chrome, Firefox and Safari. There's a button to open it in Preferences -> Advanced.

    As for documentation, that probably warrants a page higher-level page of its own for connectors to link to, for instructions on building and developing. (I've spent some time ago to make the Readme.md on the repo fairly detailed, so that's a good starting point perhaps)
  • I think it would be a good idea to just link to the Readme.md for the connectors and Word processor plugins, as you've made them much more complete than the documentation, and I suspect they will stay more up to date.
  • edited 5 days ago
    @dstillman, could you either make https://www.zotero.org/support/word_processor_plugin_installation editable for regular users, or add a link to the system requirements page (https://www.zotero.org/support/system_requirements#word_processor_plugins)? It took me a while to find out which word processors Zotero supports.

    I would write (first sentence already exists):

    "If you're running Zotero 5.0 or Zotero Standalone 4.0, the word processor plugins are bundled with Zotero and should be installed automatically for each installed word processor when you first start Zotero. See our list of supported Word and LibreOffice versions."

    (System Requirements is maybe also not the most logical place to mention word processor compatibility)

    edit: thanks for adding the link!

Sign In or Register to comment.