Skip to content

Fix typos (found by codespell) #34

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
stweil wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Fix typos (found by codespell) #34

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4c56d5e
Fix typos (found by codespell)
stweil Jun 30, 2018
4a002ed
Fix typos in meeting minutes
stweil Feb 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions Board_Documents_2014/2014-09-25 ALTO Board Meeting Minutes.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,17 +87,17 @@
Board meeting minutes and agendas are not yet on Github.
</li>
<li>
Miscellanous folder contains internal documents such as description of change request process, membership criteria. All these items are not yet on GitHub, but should be moved to “Board” repository in Github.
Miscellaneous folder contains internal documents such as description of change request process, membership criteria. All these items are not yet on GitHub, but should be moved to “Board” repository in Github.
</li>
<li>
Member proposals do/can contain private information that we do wish to make publically available. Either (1) delete member proposals, or (2) get a private Github respoitory so that information can be hidden.
Member proposals do/can contain private information that we do wish to make publicly available. Either (1) delete member proposals, or (2) get a private Github respoitory so that information can be hidden.
Suggestion was to delete member proposals.
</li>
<li>
Old comments and minutes need to be moved. Comments to be deleted (notes are not clear about this).
</li>
<li>
Use the 'board' repository as a miscellanous container; it is currently unused.
Use the 'board' repository as a miscellaneous container; it is currently unused.
</li>
<li>
Discussion about Action Items and Meetings: Jukka proposed to document Action Items more formally.
Expand Down
2 changes: 1 addition & 1 deletion Board_Documents_2015/2015-02-05 ALTO Board Meeting Minutes.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@
</p>

<p>
Jukka remarks that the date on action items is not necesary. Frederick responds that the date corresponds to the meeting from which the action item arose.
Jukka remarks that the date on action items is not necessary. Frederick responds that the date corresponds to the meeting from which the action item arose.
</p>

<p>
Expand Down
2 changes: 1 addition & 1 deletion Board_Documents_2015/2015-03-05 ALTO Board Meeting Minutes.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@

<p>
Frederick asks if it is possible to add capabilities similar to <a href=http://www.idpf.org/epub/301/spec/epub-overview.html>ePub</a>
and <a href=http://www.w3.org/TR/css3-writing-modes/>CSS Writing Modes</a> to ALTO and maintain backward compability.
and <a href=http://www.w3.org/TR/css3-writing-modes/>CSS Writing Modes</a> to ALTO and maintain backward compatibility.
For example, Jean Philippe says that it is quite common to include Western words in the text of Japanese newspapers. Further research needed.
</p>

Expand Down
2 changes: 1 addition & 1 deletion Board_Documents_2015/2015-05-06 ALTO Board Meeting Minutes.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@
Jukka will draft a proposal for discussion of board member terms and voting quorum at the next board meeting (cf. action item <a href=https://github.com/altoxml/board/issues/17>17</a>).
</p>
<p>
Recruiting new board members was the next topic of discussion. No attending member had objections to recruiting a board member from commerical companies.
Recruiting new board members was the next topic of discussion. No attending member had objections to recruiting a board member from commercial companies.
Brian suggested someone from Northern Micrographics or from iArchives / Ancestry. Brian will contact someone from Northern Micrographics about board membership;
Frederick will contact someone from iArchives / Ancestry about board membership.
</p>
Expand Down
4 changes: 2 additions & 2 deletions Board_Documents_2015/2015-09-14 ALTO Board Meeting Minutes.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,8 +46,8 @@
<p>
Reviewed the board action items. Closed <a href="https://github.com/altoxml/board/issues/12">action item #12</a>
and <a href="https://github.com/altoxml/board/issues/5">action item #5</a>
because the board decided in an earlier meeting that transfering documents from PBWorks (previous ALTO repository) would be too much work.
Remaing action items (issues) in the board repository remain open.
because the board decided in an earlier meeting that transferring documents from PBWorks (previous ALTO repository) would be too much work.
Remaining action items (issues) in the board repository remain open.
</p>
<p>
Frederick re-announced the time (Nov 6, 2015) and location of the ALTO board face-to-face meeting @ <a href="http://ipres2015.web.unc.edu/">iPRES 2015</a> in Chapel Hill NC ()
Expand Down
2 changes: 1 addition & 1 deletion Board_Documents_2015/2015-12-02 ALTO Board Meeting Agenda.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
<li>Review proposed changes to ALTO Board Membership. See items in <i>italics</i> and marked [<b>PROPOSED</b>] on the <a href=https://altoxml.github.io/ALTO%20Board%20Membership%20Criteria.html>ALTO Board Membership</a> page. [<b>Frederick</b> leads discussion]</li>
<li>Discuss new board member recruited by Jean Philippe. [<b>Jean Philippe</b> leads discussion]</li>
<li>Decide when the schema changes necessary for Shape change request <a href=https://github.com/altoxml/schema/issues/22>(issue 22)</a> will be published. Will we combine it with some other (simple) issue? [<b>Evelien</b> leads (brief) discussion.]</li>
<li>Summarize the face-to-face meeting discussion of the fragement identifier API for ALTO change request <a href=https://github.com/altoxml/schema/issues/33>(issue 33)</a>. [<b>Jean Philippe</b> leads discussion.]</li>
<li>Summarize the face-to-face meeting discussion of the fragment identifier API for ALTO change request <a href=https://github.com/altoxml/schema/issues/33>(issue 33)</a>. [<b>Jean Philippe</b> leads discussion.]</li>
<li>Summarize the face-to-face meeting discussion and continue to discuss OCR confidence value change request <a href=https://github.com/altoxml/schema/issues/23>(issue 23)</a>. [<b>Jukka</b> and <b>Nate</b> lead discussion.]</li>
<li>Continue discussion of Glyphs change request <a href=https://github.com/altoxml/schema/issues/26>(issue 26)</a>.
(See item 10 in <a href=https://altoxml.github.io/2014-09-25%20ALTO%20Board%20Meeting%20Minutes.html>minutes</a> from London face-to-face meeting) [<b>Joachim</b> leads discussion.]</li>
Expand Down
4 changes: 2 additions & 2 deletions Board_Documents_2015/2015-12-02 ALTO Board Meeting Minutes.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
<li>Review proposed changes to ALTO Board Membership. See items in <i>italics</i> and marked [<b>PROPOSED</b>] on the <a href=https://altoxml.github.io/ALTO%20Board%20Membership%20Criteria.html>ALTO Board Membership</a> page. [<b>Frederick</b> leads discussion]</li>
<li>Discuss new board member recruited by Jean Philippe. [<b>Jean Philippe</b> leads discussion]</li>
<li>Decide when the schema changes necessary for Shape change request <a href=https://github.com/altoxml/schema/issues/22>(issue 22)</a> will be published. Will we combine it with some other (simple) issue? [<b>Evelien</b> leads (brief) discussion.]</li>
<li>Summarize the face-to-face meeting discussion of the fragement identifier API for ALTO change request <a href=https://github.com/altoxml/schema/issues/33>(issue 33)</a>. [<b>Jean Philippe</b> leads discussion.]</li>
<li>Summarize the face-to-face meeting discussion of the fragment identifier API for ALTO change request <a href=https://github.com/altoxml/schema/issues/33>(issue 33)</a>. [<b>Jean Philippe</b> leads discussion.]</li>
<li>Summarize the face-to-face meeting discussion and continue to discuss OCR confidence value change request <a href=https://github.com/altoxml/schema/issues/23>(issue 23)</a>. [<b>Jukka</b> and <b>Nate</b> lead discussion.]</li>
<li>Continue discussion of Glyphs change request <a href=https://github.com/altoxml/schema/issues/26>(issue 26)</a>.
(See item 10 in <a href=https://altoxml.github.io/2014-09-25%20ALTO%20Board%20Meeting%20Minutes.html>minutes</a> from London face-to-face meeting) [<b>Joachim</b> leads discussion.]</li>
Expand Down Expand Up @@ -94,7 +94,7 @@
He suggests that it might be useful to contact IIIF and ask their opinion about the usefulness of such a AFIF.
Frederick remarked that a AFIF would amount to a guarantee by the ALTO board that the ALTO schema will not change so much that it would break the API.
Clemens said that the ALTO schema can be considered as the AFIF; he cited an example of work that he is doing in his own library.
Jean Philippe said that IIIF syntax is very simple and the AFIF would similarily be simple.
Jean Philippe said that IIIF syntax is very simple and the AFIF would similarly be simple.
Evelien said that AFIF would amount to a guarantee that identifiers in ALTO files are permanent.
Clemens remarked that IIIF permits a reference to an image or a part of an image which is not possible without IIIF.
He further said that this is possible already with ALTO because ALTO data already has internal "markers" or identifiers which can be referenced.
Expand Down
2 changes: 1 addition & 1 deletion Board_Documents_2016/2016-01-27 ALTO Board Meeting Agenda.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
<li>Review action items [<b>Frederick</b> leads discussion]</li>
<li>Discuss new board members recruited by Jean Philippe and Frederick. [<b>Jean Philippe</b> and <b>Frederick</b> lead discussion]</li>
<li>Review (briefly) the release of the schema changes necessary for Shape change request <a href=https://github.com/altoxml/schema/issues/22>(issue 22)</a>. Note that the schema change has been in public comment since our last teleconference and will be released as schema version 3.1 following our Jan 27 teleconference. [<b>Evelien</b> leads discussion.]</li>
<li>Review (briefly) the face-to-face meeting and December 2 teleconference discussion of the fragement identifier API for ALTO change request <a href=https://github.com/altoxml/schema/issues/33>(issue 33)</a> and subsequent actions. [<b>Jean Philippe</b> leads discussion.]</li>
<li>Review (briefly) the face-to-face meeting and December 2 teleconference discussion of the fragment identifier API for ALTO change request <a href=https://github.com/altoxml/schema/issues/33>(issue 33)</a> and subsequent actions. [<b>Jean Philippe</b> leads discussion.]</li>
<li>Review (briefly) the face-to-face meeting and December 2 teleconference discussion of OCR confidence value change request <a href=https://github.com/altoxml/schema/issues/23>(issue 23)</a>. [<b>Jukka</b> and <b>Nate</b> lead discussion.]</li>
<li>Continue discussion of Glyphs change request <a href=https://github.com/altoxml/schema/issues/26>(issue 26)</a>.
(See item 10 in <a href=https://altoxml.github.io/2014-09-25%20ALTO%20Board%20Meeting%20Minutes.html>minutes</a> from London face-to-face meeting) [<b>Joachim</b> leads discussion.]</li>
Expand Down
2 changes: 1 addition & 1 deletion Board_Documents_2016/2016-01-27 ALTO Board Meeting Minutes.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
<li>Review action items [<b>Frederick</b> leads discussion]</li>
<li>Discuss new board members recruited by Jean Philippe and Frederick. [<b>Jean Philippe</b> and <b>Frederick</b> lead discussion]</li>
<li>Review (briefly) the release of the schema changes necessary for Shape change request <a href=https://github.com/altoxml/schema/issues/22>(issue 22)</a>. Note that the schema change has been in public comment since our last teleconference and will be released as schema version 3.1 following our Jan 27 teleconference. [<b>Evelien</b> leads discussion.]</li>
<li>Review (briefly) the face-to-face meeting and December 2 teleconference discussion of the fragement identifier API for ALTO change request <a href=https://github.com/altoxml/schema/issues/33>(issue 33)</a> and subsequent actions. [<b>Jean Philippe</b> leads discussion.]</li>
<li>Review (briefly) the face-to-face meeting and December 2 teleconference discussion of the fragment identifier API for ALTO change request <a href=https://github.com/altoxml/schema/issues/33>(issue 33)</a> and subsequent actions. [<b>Jean Philippe</b> leads discussion.]</li>
<li>Review (briefly) the face-to-face meeting and December 2 teleconference discussion of OCR confidence value change request <a href=https://github.com/altoxml/schema/issues/23>(issue 23)</a>. [<b>Jukka</b> and <b>Nate</b> lead discussion.]</li>
<li>Continue discussion of Glyphs change request <a href=https://github.com/altoxml/schema/issues/26>(issue 26)</a>.
(See item 10 in <a href=https://altoxml.github.io/2014-09-25%20ALTO%20Board%20Meeting%20Minutes.html>minutes</a> from London face-to-face meeting) [<b>Joachim</b> leads discussion.]</li>
Expand Down
2 changes: 1 addition & 1 deletion Board_Documents_2016/2016-02-24 ALTO Board Meeting Agenda.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@
[<b>Frederick</b> leads discussion]</li>
<li>Review action items [<b>Frederick</b> leads discussion]</li>
<li>Review status of ALTO schema version 3.1 [<b>Evelien</b> and <b>Frederick</b> lead discussion]</li>
<li>Review (briefly) the face-to-face meeting and December 2 teleconference discussion of the fragement identifier API for ALTO change request <a href=https://github.com/altoxml/schema/issues/33>(issue 33)</a> and subsequent actions. [<b>Jean Philippe</b> leads discussion.]</li>
<li>Review (briefly) the face-to-face meeting and December 2 teleconference discussion of the fragment identifier API for ALTO change request <a href=https://github.com/altoxml/schema/issues/33>(issue 33)</a> and subsequent actions. [<b>Jean Philippe</b> leads discussion.]</li>
<li>Review (briefly) the face-to-face meeting and December 2 teleconference discussion of OCR confidence value change request <a href=https://github.com/altoxml/schema/issues/23>(issue 23)</a>. [<b>Jukka</b> and <b>Nate</b> lead discussion.]</li>
<li>Continue discussion of Glyphs change request <a href=https://github.com/altoxml/schema/issues/26>(issue 26)</a>.
(See item 10 in <a href=https://altoxml.github.io/2014-09-25%20ALTO%20Board%20Meeting%20Minutes.html>minutes</a> from London face-to-face meeting) [<b>Joachim</b> leads discussion.]</li>
Expand Down
2 changes: 1 addition & 1 deletion Board_Documents_2016/2016-02-24 ALTO Board Meeting Minutes.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@
[<b>Frederick</b> leads discussion]</li>
<li>Review action items [<b>Frederick</b> leads discussion]</li>
<li>Review status of ALTO schema version 3.1 [<b>Evelien</b> and <b>Frederick</b> lead discussion]</li>
<li>Review (briefly) the face-to-face meeting and December 2 teleconference discussion of the fragement identifier API for ALTO change request <a href=https://github.com/altoxml/schema/issues/33>(issue 33)</a> and subsequent actions. [<b>Jean Philippe</b> leads discussion.]</li>
<li>Review (briefly) the face-to-face meeting and December 2 teleconference discussion of the fragment identifier API for ALTO change request <a href=https://github.com/altoxml/schema/issues/33>(issue 33)</a> and subsequent actions. [<b>Jean Philippe</b> leads discussion.]</li>
<li>Review (briefly) the face-to-face meeting and December 2 teleconference discussion of OCR confidence value change request <a href=https://github.com/altoxml/schema/issues/23>(issue 23)</a>. [<b>Jukka</b> and <b>Nate</b> lead discussion.]</li>
<li>Continue discussion of Glyphs change request <a href=https://github.com/altoxml/schema/issues/26>(issue 26)</a>.
(See item 10 in <a href=https://altoxml.github.io/2014-09-25%20ALTO%20Board%20Meeting%20Minutes.html>minutes</a> from London face-to-face meeting) [<b>Joachim</b> leads discussion.]</li>
Expand Down
2 changes: 1 addition & 1 deletion Board_Documents_2016/2016-03-23 ALTO Board Meeting Agenda.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@
<li>Review Doodle poll results for a face-to-face meeting in 2016. [<b>Frederick</b> leads discussion]</li>
<li>Continue discussion of Glyphs change request <a href=https://github.com/altoxml/schema/issues/26>(issue 26)</a>.
(See item 10 in <a href=https://altoxml.github.io/2014-09-25%20ALTO%20Board%20Meeting%20Minutes.html>minutes</a> from London face-to-face meeting) [<b>Joachim</b> leads discussion.]</li>
<li>Continue discussion (if needed) of the fragement identifier API for ALTO change request <a href=https://github.com/altoxml/schema/issues/33>(issue 33)</a> and subsequent actions. [<b>Jean Philippe</b> leads discussion.]</li>
<li>Continue discussion (if needed) of the fragment identifier API for ALTO change request <a href=https://github.com/altoxml/schema/issues/33>(issue 33)</a> and subsequent actions. [<b>Jean Philippe</b> leads discussion.]</li>
<li>Continue discussion (if needed) of OCR confidence value change request <a href=https://github.com/altoxml/schema/issues/23>(issue 23)</a>. [<b>Jukka</b> and <b>Nate</b> lead discussion.]</li>
</ol>

Expand Down
2 changes: 1 addition & 1 deletion Board_Documents_2016/2016-03-23 ALTO Board Meeting Minutes.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@
<li>Review Doodle poll results for a face-to-face meeting in 2016. [<b>Frederick</b> leads discussion]</li>
<li>Continue discussion of Glyphs change request <a href=https://github.com/altoxml/schema/issues/26>(issue 26)</a>.
(See item 10 in <a href=https://altoxml.github.io/2014-09-25%20ALTO%20Board%20Meeting%20Minutes.html>minutes</a> from London face-to-face meeting) [<b>Joachim</b> leads discussion.]</li>
<li>Continue discussion (if needed) of the fragement identifier API for ALTO change request <a href=https://github.com/altoxml/schema/issues/33>(issue 33)</a> and subsequent actions. [<b>Jean Philippe</b> leads discussion.]</li>
<li>Continue discussion (if needed) of the fragment identifier API for ALTO change request <a href=https://github.com/altoxml/schema/issues/33>(issue 33)</a> and subsequent actions. [<b>Jean Philippe</b> leads discussion.]</li>
<li>Continue discussion (if needed) of OCR confidence value change request <a href=https://github.com/altoxml/schema/issues/23>(issue 23)</a>. [<b>Jukka</b> and <b>Nate</b> lead discussion.]</li>
</ol>

Expand Down
2 changes: 1 addition & 1 deletion Board_Documents_2016/2016-04-2x ALTO Board Meeting Agenda.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@

<ol>
<li>Review design principles for ALTO. [<b>Frederick</b> leads discussion]</li>
<li>Continue discussion (if needed) of the fragement identifier API for ALTO change request <a href=https://github.com/altoxml/schema/issues/33>(issue 33)</a> and subsequent actions. [<b>Jean Philippe</b> leads discussion.]</li>
<li>Continue discussion (if needed) of the fragment identifier API for ALTO change request <a href=https://github.com/altoxml/schema/issues/33>(issue 33)</a> and subsequent actions. [<b>Jean Philippe</b> leads discussion.]</li>
<li>Continue discussion (if needed) of OCR confidence value change request <a href=https://github.com/altoxml/schema/issues/23>(issue 23)</a>. [<b>Jukka</b> leads discussion.]</li>
</ol>

Expand Down
2 changes: 1 addition & 1 deletion misc/ALTO Board Membership Criteria.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ <h3>ALTO Board Membership</h3>
Exceptions to the length of board membership terms shall be made as necessary to accomodate this policy.</li>
<li>Current board members must approve new board members. New members shall be approved by a voice or email vote.</li>
<li>Board membership terms shall be renewable with the consent of the member whose term is expiring and with the agreement of the board members whose terms are not expiring.</li>
<li>Before December 31 of each year, a Board chair shall be choosen for the subsequent year from amongst current board members. The board shall strive to choose board chairs in fall of each year, and, if possible, at the annual face-to-face meeting.
<li>Before December 31 of each year, a Board chair shall be chosen for the subsequent year from amongst current board members. The board shall strive to choose board chairs in fall of each year, and, if possible, at the annual face-to-face meeting.
Candidates for board chair include board members whose terms will expire in the current year provided that they will renew their board membership.</li>
<li>Current Board member term expirations:
<ul><li>December 31, 2018: Brian and Jean Philippe</li>
Expand Down