Skip to content
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.

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

Format of STEP 5 is confusing for persons with *English as a second language* #137

Closed
jessemonroy650 opened this issue Dec 6, 2015 · 3 comments
Labels
Milestone

Comments

@jessemonroy650
Copy link

@jessemonroy650 jessemonroy650 commented Dec 6, 2015

The thread that is linked to is typical of the types of conversion that volunteers endure on a DAILY basis. From my initial reading of the post, it appeared the person had good English skills, but in fact that person was below average. This lead to the conflict and acromony.

From my point of view, there appears to be no issue the the text. However, given the consistent DAILY mis-reading of the text, it appears the text is being read as two (2) steps and NOT two (2) choices. That is, people are mis-reading the text of Step 5: Going Further. It reads:

There are two choices available for building and packaging your applications:

  1. Build and package locally using the PhoneGap CLI
  2. Use PhoneGap Build cloud service for simplifying the build and app packaging process

Which you choose will depend on how comfortable you are working with a command line environment and more closely with the native SDK's and tools versus leaving it to a cloud service and providing the required details.

The previous text seems to be mis-reading as such:

There are two steps for building and packaging your applications:

  1. Build and package locally using the PhoneGap CLI
  2. Use PhoneGap Build cloud service for simplifying the _[linguistic blindspot]_ process

To the casual person, with English as a primary language, this is obviously a mis-reading.

However to the average person with English as a second language, it is a 90+% hit rate. That is to say, thay can recognize 90+% of the words, therefore deduce the intent - with their interpetation.

To be clear,

  • choices available for gets misread as steps.

And

  • build and app gets mis-read as app.

On the first, in some languages choices and steps amount to the same thing. This is one possible interpretation, and the possible reading.

On the second, there may be some confusion (in the mind of the reader), but they see Build and package and deduce that somehow the "PhoneGap Build cloud service" build and app packaging are related. That is to say, they do not read this as a equivalence, but read this as a relationship. The fact that one word is in error - draws no significance to the reader.

On the second, the fact that words in bold become a _blindspot_ is normal given the repetive nature of technical articles.

One other note, I have seen blogs that suggest that the CLI should be used to create templates (or boilerplates) for Phonegap Build. In the future, I will make note of such blogs and get them to correct, if possible or necessary.

In any case, this is the best I can make of this.

SUGGESTION: Take the 2x4 approach. Make a clear divison. Delineate there are two choices. Delineate that the two choices are separate paths and cannot be interchanged. This may require a pictorial explanation, as well. If suggestion are requested, I can write something.

NOTE: The user suggests make an alternate choice. That choice should be to point to templates as starting points. Perhaps this could be an explanation point.

@jessemonroy650
Copy link
Author

@jessemonroy650 jessemonroy650 commented Feb 27, 2016

These are issues on Nitobi

MORE Confusion

@mwbrooks mwbrooks added this to the User Support milestone May 20, 2016
purplecabbage added a commit that referenced this issue Nov 11, 2018
This fixes #137
@jessemonroy650
Copy link
Author

@jessemonroy650 jessemonroy650 commented Nov 15, 2018

Thanks guys for finally getting this done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

2 participants
You can’t perform that action at this time.