Initial commit

.gitattributes

@@ -0,0 +1,2 @@
+# Auto detect text files and perform LF normalization
+* text=auto

App/AppInfo/Launcher/ZoteroPortable.ini

@@ -0,0 +1,164 @@
+;This is an example launcher INI that is part of the PortableApps.com Template
+;It uses a standard Windows INI format, so any line starting with a semi-colon is treated as a comment
+;It is recommended that you use a coding text editor to edit this, preferably one with context highlighting
+;If editing with Notepad++, be sure you have turned off the option to add a BOM as it will break the INI
+;Full details: http://portableapps.com/manuals/PortableApps.comLauncher/
+
+[Launch]
+;This section details how an app is started and where it works
+;ProgramExecutable is the EXE to run to start the app relative to the AppNamePortable\App directory
+ProgramExecutable=Zotero\zotero.exe
+;ProgramExecutable64 is an optional EXE to run if running on Windows 64-bit
+;ProgramExecutable64=AppName\AppName64.exe
+;CommandLineArguments is an optional setting that will cause the above EXE to be launched with this string passed
+CommandLineArguments='-datadir "%PAL:DataDir%\profile"'
+;DirectoryMoveOK indicates whether a directory can be moved to a different path rather than just supporting drive letter changes
+DirectoryMoveOK=yes
+;SupportsUNC indicates whether an app can run from a Windows UNC path, often referred to as a network path
+SupportsUNC=yes
+;RunAsAdmin indicates whether an app requires admin rights to run. This should generally be avoided when possible
+;Details: http://portableapps.com/manuals/PortableApps.comLauncher/ref/launcher.ini/launch.html#runasadmin
+;RunAsAdmin=try
+
+[Activate]
+;This section lets the launcher know what functionality needs to be included.
+;IMPORTANT: Any changes to this section will require the launcher to be recompiled.
+;Registry indicates whether we will be reading or writing to the registry. If not, setting to false will make the launcher slightly smaller and cause it to start slightly faster.
+Registry=false
+;Java indicates whether the app needs Java to run
+;Java=find
+;XML indicates whether the launcher will need to read or write to XML paths within settings files of the app. If not, setting to false will make the launcher slightly smaller and cause it to start slightly faster.
+XML=false
+
+[Environment]
+;This section lets the launcher know what environment variables need to be set. If not needed, this can be removed.
+;AppNameExamplePath=%PAL:AppDir%\App\AppName
+
+
+[RegistryKeys]
+;This section allows you to backup and restore a given key and the keys below it within the registry.  Any existing data in the same location will be backed up before the app is run and restored on exit.  The portable app's data will be stored in a .reg key with the name at the beginning of each line within the Data directory.  It's best to take as little of the registry as possible.  In our example, taking the whole ExamplePublisher section isn't necessary because all our app's data is stored within AppName.  If we took ExamplePublisher, we might run into problems with other apps from the same publisher.
+;AppName=HKCU\Software\ExamplePublisher\AppName
+;If there is some data in the registry that the app creates but does not need to be saved between sessions of the portable app, it can be handled using a - instead of a name for a .reg file as follows:
+;-=HKCU\Software\ExamplePublisher\GarbageData
+
+[RegistryCleanupIfEmpty]
+;This section allows you to remove sections of the registry if they are empty when the app exits. In this example, we're removing the app publisher's section if no local apps from the same publisher exit after our portable app exits so we don't leave behind an empty bit of registry.
+;1=HKCU\Software\ExamplePublisher
+
+;ENVIRONMENT VARIABLES FOR USE WITH DIRECTORIES AND FILES
+;These next sections deal with directory and file handling.  For these, environment variable substitutions will apply
+;Environment variables: http://portableapps.com/manuals/PortableApps.comLauncher/ref/envsub.html#ref-envsub
+
+[DirectoriesMove]
+;This section allows you to configure directories that need to be moved from the Data directory to either the app's directory or to the local machine.  Many standard environment variables are supported here including things like APPDATA.
+
+;This first entry will move the contents of AppNamePortable\Data\AppNameConfig to C:\Users\[user]\AppData\Roaming\ExamplePublisher\AppName while the app is running and back when complete.  Any existing data will be backed up and restored.
+
+
+;This second entry will move the contents of AppNamePortable\Data\AppNamePortableConfig to AppNamePortable\App\AppName while the app is running and back when complete.
+;AppNamePortableConfig=%PAL:AppDir%\AppName\Config
+
+;This entry indicates that the contents of C:\Users\[user]\AppData\Roaming\ExamplePublisher\GarbageData should be disposed of when the app is done running.  Any existing data will be backed up and restored when complete.
+-=%LOCALAPPDATA%\Zotero
+
+[FilesMove]
+;This section allows you to configure directories that need to be moved from the Data directory to either the app's directory or to the local machine.  Many standard environment variables are supported here including things like APPDATA.
+
+;This first entry will move the file AppNamePortable\Data\appnameexample.config to C:\Users\[user]\AppData\Roaming\ExamplePublisher while the app is running and back when complete.  Any existing data will be backed up and restored.
+;appnameexample.config=%APPDATA%\ExamplePublisher
+
+;This second entry will move the file of AppNamePortable\Data\appnameportableexample.config to AppNamePortable\App\AppName while the app is running and back when complete.
+;appnameportableexample.config=%PAL:AppDir%\AppName
+
+[DirectoriesCleanupIfEmpty]
+;This section allows you to remove directories if they are empty when the app exits. In this example, we are removing the ExamplePublisher directory if it is empty so we don't leave a blank directory behind from the app.
+;1=%APPDATA%\ExamplePublisher
+
+[FileWrite1]
+;FILEWRITE
+;These entries allow you to update the paths within configuration and registry files
+;The entries use the standard environment variables along with some additional modifiers
+;Environment variables: http://portableapps.com/manuals/PortableApps.comLauncher/ref/envsub.html#ref-envsub
+
+;For these examples, we'll update the relative paths in both a standard config file and a .reg file
+
+;FileWrite1 to 3 will update the drive letter, relative path, and full path in a config file
+;Note the order from most specific path to least, ensuring we don't change a drive letter alone before a full path
+
+;Type=Replace
+;File=%PAL:DataDir%\settings\appnameportableexample.config
+;Find=%PAL:LastDrive%%PAL:LastPackagePartialDir%\
+;Replace=%PAL:Drive%%PAL:PackagePartialDir%\
+
+[FileWrite2]
+;Type=Replace
+;File=%PAL:DataDir%\settings\appnameportableexample.config
+;Find=%PAL:LastDrive%%PAL:LastPortableAppsBaseDir%\
+;Replace=%PAL:Drive%%PAL:PortableAppsBaseDir%\
+
+[FileWrite3]
+;Type=Replace
+;File=%PAL:DataDir%\settings\appnameportableexample.config
+;Find=%PAL:LastDrive%\
+;Replace=%PAL:Drive%\
+
+;FileWrite4 to 6 will update the drive letter, relative path, and full path in a registry file
+;Note that we use double backslashes for the paths instead of singles because that is the way a .reg file stores them
+
+[FileWrite4]
+;Type=Replace
+;File=%PAL:DataDir%\settings\AppName.reg
+;Find=%PAL:LastDrive%%PAL:LastPackagePartialDir:DoubleBackslash%\\
+;Replace=%PAL:Drive%%PAL:PackagePartialDir:DoubleBackslash%\\
+
+[FileWrite5]
+;Type=Replace
+;File=%PAL:DataDir%\settings\AppName.reg
+;Find=%PAL:LastDrive%%PAL:LastPortableAppsBaseDir:DoubleBackslash%\\
+;Replace=%PAL:Drive%%PAL:PortableAppsBaseDir:DoubleBackslash%\\
+
+[FileWrite6]
+;Type=Replace
+;File=%PAL:DataDir%\settings\AppName.reg
+;Find=%PAL:LastDrive%\\
+;Replace=%PAL:Drive%\\
+
+;FileWrite 7 is an example of writing a value directly to a file, to specify a path to plugins for example
+
+;[FileWrite7]
+;Type=INI
+;File=%PAL:DataDir%\settings\appnameportableexample.config
+;Section=Paths
+;Key=PluginsPath
+;Value=%PAL:AppDir%\AppName\plugins
+
+
+
+
+
+
+;Language switching is a bit beyond an example package such as this.  The PortableApps.com Launcher does support automatic language switching with the platform but it is not required for portable apps.
+;Details: http://portableapps.com/manuals/PortableApps.comLauncher/ref/launcher.ini/language.html
+
+;[Language]
+;Base=%PortableApps.comLanguageCode%
+;CheckIfExists=%PAL:AppDir%\Languages\%PAL:LanguageCustom%.locale
+;DefaultIfNotExists=en
+
+;[LanguageStrings]
+;ar-sa=ar
+
+;[LanguageFile]
+;Type=INI
+;File=%PAL:DataDir%\settings\appnameportableexample.config
+;Section=Language
+;Key=Language
+
+;Lastly, we'd need to save our changes to the language setting back to the configuration file
+
+;[FileWrite8]
+;Type=INI
+;File=%PAL:DataDir%\settings\appnameportableexample.config
+;Section=Language
+;Key=Language
+;Value=%PAL:LanguageCustom%

App/AppInfo/appinfo.ini

@@ -0,0 +1,86 @@
+;This is an example appinfo.ini that is part of the PortableApps.com Template
+;It uses a standard Windows INI format, so any line starting with a semi-colon is treated as a comment
+;It is recommended that you use a coding text editor to edit this
+;If editing with Notepad++, be sure you have turned off the option to add a BOM as it will break the INI
+;Full details on this file: http://portableapps.com/development/portableapps.com_format#appinfo
+
+[Format]
+;This section is used by the PortableApps.com Installer and does not normally need to be edited
+Type=PortableAppsFormat
+Version=3.5
+
+[Details]
+;The app details that will be shown to the user and used by the PortableApps.com Platform
+;Name is the name of the app. Generally the normal name of the app with " Portable" added to the end
+Name=Zotero Portable
+;AppId is a unique id used by the Platform's updater and app store as well as the Installer
+AppId=ZoteroPortable
+;Publisher includes the name of the original publisher and the organization packaging if different
+Publisher=Zotero Team & PortableApps.com
+;Homepage is the URL of the portable app's homepage which may differ from the app's main homepage
+Homepage=PortableApps.com/Development
+;Donate is the URL for donations to contribute money to help with development
+Donate=https://www.zotero.org/getinvolved/
+;Category is the type of app. It is used by the Platform for organization.  Valid entries are: Accessibility, Development, Education, Games, Graphics & Pictures, Internet, Music & Video, Office, Security or Utilities. Only these exact entries are accepted
+Category=Office
+;Description is a short description of the app. The app name should be omitted.  Examples include: "Web browser", "Email client", etc
+Description=A personal research assistant
+;Language indicates how the installer will be built.  If a single language, the installer will be built in that language.  If Multilingual, a standard installer with all languages will be built. Generally, only Multilingual or English apps are released by PortableApps.com.  A full list of languages is available
+Language=Multilingual
+
+[License]
+;This section includes licensing details on the bundled app.
+;Shareable indicates whether an app may be shared from one user to another. Generally true except for commercial apps
+Shareable=true
+;OpenSource indicates whether an app is open source under an OSI license
+OpenSource=true
+;Freeware indicates whether an app is freeware and may be used with no charge to the user
+Freeware=true
+;CommercialUse indicates whether this app may legally be used in a business setting. Some freeware prohibits this
+CommercialUse=true
+;EULAVersion is the version of the license that comes with the app that the user must agree to before use. This is included as a file EULA.txt within the AppInfo directory.  An EULA should *only* be used if the user is required to agree to it before installing.  Each time a major change is made to the EULA (not just a formatting change) the version should be increased. Note that open source licenses (GPL, MIT, etc) do not need to be agreed to by the user and should not be included as an EULA.txt.
+;EULAVersion=1
+
+[Dependencies]
+;This section indicates to the launcher and platform what this app needs to function
+;See details at: http://portableapps.com/development/portableapps.com_format#appinfo
+;UsesGhostscript=optional
+;UsesJava=no
+;UsesDotNetVersion=
+
+[Version]
+;PackageVersion is used by the installer and the updater.  It must be in dotted quad X.X.X.X format for use by Windows.  You must ensure that each successive version has a higher package version than the previous or it will not be treated as a newer version by the platform's updater. Generally, the PackageVersion is based on the DisplayVersion.  So an app with version 3.4 will have a package version of 3.4.0.0.
+PackageVersion=5.0.23.0
+;DisplayVersion is displayed to the user and used in naming the installer
+DisplayVersion=5.0
+;Some example Display and Package versions
+;3.4 would be 3.4.0.0
+;4.5a would be 4.5.1.0
+;1.2 Dev Test 1 would be 1.1.99.1  Why?  So we can have room to grow and still use 1.2.0.0 as the official stable release. Dev tests with 3 and 4 digit numbers can be indicated similarly. 4.5.1 Dev Test 1 would be 4.4.1.991 and 4.5.1.1 Dev Test 1 would be 4.5.0.991.
+
+[Control]
+;This indicates to the platform how many icons a given app should have and how the app should be started.  All official apps should generally have a single icon.  The only exception is for office suites that include multiple big apps.  See LibreOffice Portable for an example.
+Icons=1
+;Start is the EXE that should be run to start the app
+Start=ZoteroPortable.exe
+
+;[Associations]
+;This section indicates to the platform which extensions the app can handle and how to start the app
+;See details at: http://portableapps.com/development/portableapps.com_format#appinfo
+;FileTypes=html,htm,xhtml,xhtm,xht,shtml
+;FileTypeCommandLine=/Open=%1
+;FileTypeCommandLine-extension=/OpenExtension=%1
+;Protocols=http,https,gtp,gopher
+;ProtocolCommandLine=--protocolhandler=%1
+;ProtocolCommandLine-protocol=--http:%1
+;SendTo=true
+;SendToCommandLine=-multiplefiles "%1"
+;Shell=true
+;ShellCommand=/idlist,%I,%L
+
+;[FileTypeIcons]
+;This section indicates which icons to associate with the file types listed in Associations
+;See details at: http://portableapps.com/development/portableapps.com_format#appinfo
+;swf=video
+;ttp=custom
+;qwe=app

App/AppInfo/pac_installer_log.ini

@@ -0,0 +1,11 @@
+[PortableApps.comInstaller]
+Info1=Do not delete or modify this file. It may be necessary for this app to function correctly.
+Info2=This file was generated by the PortableApps.com Installer wizard and modified by the official PortableApps.com Installer TM Rare Ideas, LLC as the app was installed.
+Info3=This file should be excluded from git repositories by using the appropriate gitignore.
+Run=true
+WizardVersion=3.5.5.0
+PackagingDate=2017-10-23
+PackagingTime=16:37:09
+InstallerVersion=3.5.5.0
+InstallDate=2017-10-27
+InstallTime=16:36:01

App/DefaultData/profile/locate/engines.json

@@ -0,0 +1,46 @@
+[
+	{
+		"name": "CrossRef Lookup",
+		"alias": "CrossRef",
+		"icon": "https://www.crossref.org/favicon.ico",
+		"_urlTemplate": "http://crossref.org/openurl?{z:openURL}&pid=zter:zter321",
+		"description": "CrossRef Search Engine",
+		"hidden": false,
+		"_urlParams": [],
+		"_urlNamespaces": {
+			"z": "http://www.zotero.org/namespaces/openSearch#",
+			"": "http://a9.com/-/spec/opensearch/1.1/"
+		},
+		"_iconSourceURI": "http://crossref.org/favicon.ico"
+	},
+	{
+		"name": "Google Scholar Search",
+		"alias": "Google Scholar",
+		"icon": "https://scholar.google.fr/favicon-png.ico",
+		"_urlTemplate": "http://scholar.google.com/scholar?as_q=&as_epq={z:title}&as_occt=title&as_sauthors={rft:aufirst?}+{rft:aulast?}&as_ylo={z:year?}&as_yhi={z:year?}&as_sdt=1.&as_sdtp=on&as_sdtf=&as_sdts=22&",
+		"description": "Google Scholar Search",
+		"hidden": false,
+		"_urlParams": [],
+		"_urlNamespaces": {
+			"rft": "info:ofi/fmt:kev:mtx:journal",
+			"z": "http://www.zotero.org/namespaces/openSearch#",
+			"": "http://a9.com/-/spec/opensearch/1.1/"
+		},
+		"_iconSourceURI": "http://scholar.google.com/favicon.ico"
+	},
+	{
+		"name": "oaDOI Lookup",
+		"alias": "oaDOI Lookup",
+		"icon": "https://oadoi.org/static/img/favicon.png",
+		"_urlTemplate": "http://oadoi.org/{z:DOI}",
+		"description": "oaDOI Resolver for Zotero",
+		"hidden": false,
+		"_urlParams": [],
+		"_method": "GET",
+		"_urlNamespaces": {
+			"z": "http://www.zotero.org/namespaces/openSearch#",
+			"xmlns": "http://a9.com/-/spec/opensearch/1.1/"
+		},
+		"_iconSourceURI": "https://oadoi.org/static/img/favicon.png"
+	}
+]