crewID/libnfc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Various typos

Browse source
This commit is contained in:
Philippe Teuwen 2013-01-31 21:58:29 +01:00
parent 93e26b1475
commit 06bfed11b9
8 changed files with 21 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
ChangeLog
View file

@ -16,7 +16,7 @@ Changes:
- nfc_emulate_target() now takes timeout parameter - nfc_emulate_target() now takes timeout parameter
Special thanks to: Special thanks to:
- Alex Lian (Windows support refesh) - Alex Lian (Windows support refresh)
Jan 20, 2013 - 1.7.0-rc2 (release candidate) Jan 20, 2013 - 1.7.0-rc2 (release candidate)
-------------------------------------------- --------------------------------------------

18
README
View file

@ -10,7 +10,7 @@ General Information
libnfc is a library which allows userspace application access to NFC devices. libnfc is a library which allows userspace application access to NFC devices.
The official web site is: The official web site is:
http://www.libnfc.org/ http://www.nfc-tools.org/
The official forum site is: The official forum site is:
http://www.libnfc.org/community/ http://www.libnfc.org/community/
@ -23,7 +23,7 @@ Important note: this file covers POSIX systems, for Windows please read README-W
Requirements Requirements
============ ============
Some NFC drivers depends on third party software: Some NFC drivers depend on third party software:
* pn53x_usb & acr122_usb: * pn53x_usb & acr122_usb:
@ -33,7 +33,7 @@ Some NFC drivers depends on third party software:
- pcsc-lite http://pcsclite.alioth.debian.org/ - pcsc-lite http://pcsclite.alioth.debian.org/
The regression test suite depend on the cutter framework: The regression test suite depends on the cutter framework:
http://cutter.sf.net http://cutter.sf.net
Installation Installation
@ -69,7 +69,14 @@ Please make sure to include:
And anything else you think is relevant. And anything else you think is relevant.
* How to reproduce the bug. * A trace with debug activated.
Reproduce the bug with debug, e.g. if it was:
$ nfc-list -v
run it as:
$ LIBNFC_LOG_LEVEL=3 nfc-list -v
* How to reproduce the bug.
Please include a short test program that exhibits the behavior. Please include a short test program that exhibits the behavior.
As a last resort, you can also provide a pointer to a larger piece As a last resort, you can also provide a pointer to a larger piece
@ -85,7 +92,8 @@ Patches
======= =======
Patches can be posted to http://code.google.com/p/libnfc/issues/list or Patches can be posted to http://code.google.com/p/libnfc/issues/list or
can be sent directly to libnfc's developers: http://www.libnfc.org/contact can be sent directly to libnfc's developers:
http://nfc-tools.org/index.php?title=Contact
If the patch fixes a bug, it is usually a good idea to include If the patch fixes a bug, it is usually a good idea to include
all the information described in "How to Report Bugs". all the information described in "How to Report Bugs".

2
README-Windows.txt
View file

@ -1,6 +1,8 @@
*- *-
* Public platform independent Near Field Communication (NFC) library * Public platform independent Near Field Communication (NFC) library
* Windows-specific parts:
* Copyright (C) 2010, Glenn Ergeerts * Copyright (C) 2010, Glenn Ergeerts
* Copyright (C) 2013, Alex Lian
-* -*
Requirements Requirements

2
debian/control vendored
View file

@ -4,7 +4,7 @@ Priority: extra
Maintainer: Nobuhiro Iwamatsu <iwamatsu@debian.org> Maintainer: Nobuhiro Iwamatsu <iwamatsu@debian.org>
Build-Depends: debhelper (>= 8), dh-autoreconf, libtool, pkg-config, libusb-dev Build-Depends: debhelper (>= 8), dh-autoreconf, libtool, pkg-config, libusb-dev
Standards-Version: 3.9.4 Standards-Version: 3.9.4
Homepage: http://www.libnfc.org/ Homepage: http://www.nfc-tools.org/
Vcs-Git: https://code.googlecode.com/p/libnfc/ Vcs-Git: https://code.googlecode.com/p/libnfc/
Vcs-Browser: http://code.google.com/p/libnfc/source/browse/ Vcs-Browser: http://code.google.com/p/libnfc/source/browse/

2
debian/copyright vendored
View file

@ -1,6 +1,6 @@
Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: libnfc Upstream-Name: libnfc
Source: http://www.libnfc.org/ Source: http://libnfc.googlecode.com/
Files: * Files: *
Copyright: 2009, Roel Verdult <roel@libnfc.org>, Romuald Conty <romuald@libnfc.org> Copyright: 2009, Roel Verdult <roel@libnfc.org>, Romuald Conty <romuald@libnfc.org>

2
libnfc/additional-pages.dox
View file

@ -4,7 +4,7 @@
* @section intro_sec Introduction * @section intro_sec Introduction
* This is the developer manual for \b libnfc. * This is the developer manual for \b libnfc.
* libnfc is an open source library that allows you to communicate with NFC devices. For more info, see the * libnfc is an open source library that allows you to communicate with NFC devices. For more info, see the
* <a href="http://www.libnfc.org">libnfc homepage</a>. * <a href="http://www.nfc-tools.org">libnfc homepage</a>.
* *
* @section quick_start_sec Quick start * @section quick_start_sec Quick start
* If you are looking for libnfc's public API, you should start with the Modules page which links to the different categories of libnfc's functionality. * If you are looking for libnfc's public API, you should start with the Modules page which links to the different categories of libnfc's functionality.

2
utils/mifare.c
View file

@ -47,7 +47,7 @@
* @note There are three different types of information (Authenticate, Data and Value). * @note There are three different types of information (Authenticate, Data and Value).
* *
* First an authentication must take place using Key A or B. It requires a 48 bit Key (6 bytes) and the UID. * First an authentication must take place using Key A or B. It requires a 48 bit Key (6 bytes) and the UID.
* They are both used to initialize the internal cipher-state of the PN53X chip (http://libnfc.org/hardware/pn53x-chip). * They are both used to initialize the internal cipher-state of the PN53X chip.
* After a successful authentication it will be possible to execute other commands (e.g. Read/Write). * After a successful authentication it will be possible to execute other commands (e.g. Read/Write).
* The MIFARE Classic Specification (http://www.nxp.com/acrobat/other/identification/M001053_MF1ICS50_rev5_3.pdf) explains more about this process. * The MIFARE Classic Specification (http://www.nxp.com/acrobat/other/identification/M001053_MF1ICS50_rev5_3.pdf) explains more about this process.
*/ */

2
windows/mm/libnfc.mm
View file

@ -21,7 +21,7 @@
; #define? COMPANY_PRODUCT_ICON ..\win32\libnfc.ico ;; override from company.mmh ; #define? COMPANY_PRODUCT_ICON ..\win32\libnfc.ico ;; override from company.mmh
#define? UISAMPLE_DIALOG_FILE_dlgbmp nfcleft.bmp ;; override uisample.mmh #define? UISAMPLE_DIALOG_FILE_dlgbmp nfcleft.bmp ;; override uisample.mmh
#define? UISAMPLE_BLINE_TEXT www.libnfc.org #define? UISAMPLE_BLINE_TEXT www.nfc-tools.org
#define? COMPANY_WANT_TO_INSTALL_DOCUMENTATION N #define? COMPANY_WANT_TO_INSTALL_DOCUMENTATION N
;--- Include MAKEMSI support (with my customisations and MSI branding) ------ ;--- Include MAKEMSI support (with my customisations and MSI branding) ------