Writing on PF: Exploring the [B] Phenomenon

[epenguin]

Writing

On this site and no other, when I type B inside [] I get .

I copied that from a thread where I wrote the above sentence.

Now let me write that sentence, well just the

Yes I wrote B capital and got b. If you press the quote and it comes out like on my screen you will see I am not fantasizing.

But not in the title. And not outside the []. This does not happen with [A]. Let me write a few more [C][D][M][X][Y][Z]. OK, it does not happen for X, Y, Z, so we can survive. But - yes it is still happening.

This phenomenon is very uninteresting. However it could drive some of the people who come here crazy.* Unless it happens only to me.* Otherwise I think something needs to be done.

*I am not crazy.**

**However if you are seeing different on your screen than I on mine, I might sound crazy.
I type B and if it is in square brackets I get b.
And I can't get round it by typing b in brackets - I get - i.e. b inside [].

 

[Evo]

On this site and no other, when I type B inside [] I get .

I copied that from a thread where I wrote the above sentence.

Now let me write that sentence, well just the

Yes I wrote B capital and got b. If you press the quote and it comes out like on my screen you will see I am not fantasizing.

But not in the title. And not outside the []. This does not happen with [A]. Let me write a few more [C][D][M][X][Y][Z]. OK, it does not happen for X, Y, Z, so we can survive. But - yes it is still happening.

This phenomenon is very uninteresting. However it could drive some of the people who come here crazy.* Unless it happens only to me.* Otherwise I think something needs to be done.

*I am not crazy.**

**However if you are seeing different on your screen than I on mine, I might sound crazy.
I type B and if it is in square brackets I get b.
And I can't get round it by typing b in brackets - I get - i.e. b inside [].

Perhaps because is the first part of bolding?

 

[lisab]

In the following tests, the . in the brackets are there just as dummies:

[.b]bold[/b] = bold
[.B]bold[/B] = bold
[.B]bold[/b] = bold
[.bold]bold[/bold] = [bold]bold[/bold]

[.b] =
[.B] =

That this happens to me, too, says nothing about your sanity or lack thereof.

 

[alxm]

Wow, seems there's no way around this actually.

You'd think putting the "noparse" tags ([noparse][noparse][/noparse][/noparse]) around it should work, but even then, it still changes the thing to lowercase. That's a bug.

Example:
[noparse]The 'B's here were written in uppercase[/noparse]

 

[Danger]

I don't see a problem with this. If you want to differentiate a "B" from a "b", use a different container such as the "" that I used here. Otherwise, you are going to invoke the bold function. There are a lot of container symbols available that don't trigger an automatic function: <>, (), ··, ”’, etc..

edit: Mentors—how the hell did we end up with another penguin here? I thought that we were still trying to assassinate the first one.

 

[epenguin]

Aha, he said, if I write [] and put I into it, that should give me i.!

Voilà: .

Danger what you say is all very well but [A] is supposed to represent the molarity of A. That was a nuisance here https://www.physicsforums.com/showpost.php?p=2850378&postcount=5

 

[Gokul43201]

See: https://www.physicsforums.com/showthread.php?p=1080197#post1080197

 

[Gokul43201]

Some workarounds:

1. -> enclose in itex tags

2. [noparse][[/noparse]B] -> use noparse around some part of the 3-character string, not the entire thing

3. [B] -> other types of goofy tricks, this being a quick one - hit "quote" to see what I've done.

Note: Enclosing within code tags does not help.

 

[Danger]

Danger what you say is all very well but [A] is supposed to represent the molarity of A.

I wasn't aware of that. Sorry. Good solutions, Gokul.

 

[epenguin]

Some workarounds:

1. -> enclose in itex tags

2. [noparse][[/noparse]B] -> use noparse around some part of the 3-character string, not the entire thing

3. [B] -> other types of goofy tricks, this being a quick one - hit "quote" to see what I've done.

Note: Enclosing within code tags does not help.

Thank you. The first seems the one I am most likely to remember.