On Mar 18, 3:31 pm, "Richard Cornford" <Rich...@litote s.demon.co.uk>
wrote:
"VK" <schools_r...@y ahoo.comwrote:
On Mar 18, 1:46 pm, Richard Cornford wrote:
That post is not even "provisiona l". All it does is state that
its author is "proposing to add new FAQ entry", which may be
true but is very much internal to VK's mind. It does not state
that anything in the post is intended for wider consideration
as such an entry and it does not employ the formal mechanism
for indicating such (the post contains no <FA****RYmark-up).
I implore your pardon...
http://www.jibbering.com/faq/index.html#FAQ5_1
"If a poster feels that the question they are answering should be
covered in the FAQ, placing <FA****RYin your post lets the FAQ
robot collect the messages for easy review and inclusion."
Now:
http://groups.google.com/group/comp....470812c5e4d3b5
Post title:
"<FA****RY> I'm changing my page but nothing is changing on the
screen. Why?</FA****RY>"
That is a Subject header not a title.
Are we feeling especially freaky today?
There are at least three "Native English Speakers" around one baby
(FAQ text) with at least one - JRS - positioning himself nearly as God
and the last keeper of the True English (to my endless amusement btw).
Yet all together they produced the most obscure chunk of a technical
text one could imagine. Moreover and for even more fun they are now
insisting that there is some hidden clarity in this text - one just
need to read it "with a proper mindset".
Again quoting
http://www.jibbering.com/faq/#FAQ5_1
"If a poster feels that the question they are answering should be
covered in the FAQ, placing <FA****RYin your post lets the FAQ robot
collect the messages for easy review and inclusion."
This sentence
1) doesn't specify in what part of the post the marker should be
placed: in the subject line or in the body or reduplicated in both
parts.
2) doesn't specify if the marker should be used as explicitly spelled
thus as a single marker; or does it presume using it tag-like so with
opening <F...tag and closing </F...tag with the relevant content
inside these tags.
No one - just like me - ever knew what a hey did the unknown dislexer
mean while writing it, so anyone was going by her own preferred
reading. By going from the most recent requests back to past:
<FA****RYcorrec tion
http://groups.google.com/group/comp....60c5921b248934
(single <F...mark in the subject line)
http://groups.google.com/group/comp....c1a4c1de15426f
<FA****RYtext </FA****RY>
(tag-like <F...usage in the message body)
<FA****RYcorrec tions
http://groups.google.com/group/comp....3a0e91da811ce1
(single <F...mark in the subject line)
<FA****RY4.41 correction
http://groups.google.com/group/comp....dd93894394e6ec
(single <F...mark in the subject line)
$ <FA****RY>
http://groups.google.com/group/comp....aa990244bf1226
(single <F...mark in the subject line)
http://groups.google.com/group/comp....e27bd0d8696c6a
<FA****RYtext <FA****RY>
(tag-like <F...usage in the message body)
http://groups.google.com/group/comp....5105828ebfcc5e
<FA****RYtext
(single <F...mark in the message body)
http://groups.google.com/group/comp....a3863e3c218aca
<FA****RYtext
(single <F...mark in the message body)
<FA****RY>
http://groups.google.com/group/comp....223469afd5aadc
<FA****RYtext
(single <F...mark in the subject line and
single <F...mark in the message body)
I may keep going to the past months to get even more random usages. So
far no one of them was declined for "non-appropriate <FA****RY>
formatting". The first precedent over all these years was created only
now, for my particular FAQ proposal. As interesting as it is by
itself, I don't care to re-post with any reasonable formatting. But
first get my sh** on your bullsh**:
1) For all future potential posters it will be interesting to know if
and why among all possible interpretations of FAQ 5.1 only
<FA****RY>Subje ct</FA****RYis not acceptable (while
<FA****RY>Subje ct is fine). Moreover it is not acceptable by some
weather conditions I guess and not simply as such. See for instance
http://groups.google.com/group/comp....167d13ea90ce98
and the like
2) Even more useful would be to join all language capabilities of
involved people - however limited they are - and try to translate FAQ
5.1 from the current Pigeon English to something not to say perfect
but at least descent. That would eliminate the funny threads like this
one in the future.
Best regards.