Siniy
The following tiddler seems to be where the new field creation logic is. If
manipulated you may be able to create other fields but it is not clear what
implications this would have. Test on an empty.html and save and reload,
list and search then ask the dev team if they can tell you what
It is not my problem. It is problem of TW5.
понедельник, 28 декабря 2020 г. в 08:34:32 UTC+3, positiv...@gmail.com:
> You said, "I don't know that attributes can be with Russian letters". I
> cannot see what you tried and what error you saw.
>
> When I open a Wiki file and create a new
positivesigner is my username at gmail.com.
On Sunday, December 27, 2020 at 9:36:16 PM UTC-8 Thomas Stone wrote:
> I was unable to get my screenshots to submit with the post. Email me at
> positiv...@gmail.com if you want to send some screenshots back and forth.
>
> On Sunday, December 27, 2020
I was unable to get my screenshots to submit with the post. Email me at
positivesig...@gmail.com if you want to send some screenshots back and
forth.
On Sunday, December 27, 2020 at 9:34:32 PM UTC-8 Thomas Stone wrote:
> You said, "I don't know that attributes can be with Russian letters". I
Positiv, thank you for experiment. I don't know that attributes can be
with Russian letters
I test it with space "цвет мой" unfortunately it don't work
суббота, 26 декабря 2020 г. в 02:21:59 UTC+3, positiv...@gmail.com:
> FYI: I was able to verify the button provided by Xavier on the
FYI: I was able to verify the button provided by Xavier on the sample TW
that Siniy-Kit provided. His link opens a specific Tiddler. I edited that
tiddler and pasted in the below code. I was also able to verify Eric
Shulman's comment that the field names are converted to lower case upon
Hi Jeremy. Thank you for answer. Many people don't know about html
attributes and so on. And it looks strange for them, when they get this
alert,
* Illegal characters in field name "цвет". Fields can only contain
lowercase letters, digits and the characters underscore (_), hyphen (-) and
@Jeremy:
Your reply to Siniy-Kit cited: "... a-z, 0-9, dash and underscore..." I
have been under the impression that "dot" (".") is also supported and I
use it quite a bit. Did your reply simply omit it, or has there been a
change that has not bitten me yet, or are you contemplating
Hi Eric,
Oh I see, thank you for the enlightenment!
I realise that up to now I used extended field names only with wikis
running on NodeJS, not ones saved in an HTML file.
Cheers,
Xavier
Le mer. 23 déc. 2020 à 18:36, Eric Shulman a écrit :
> On Wednesday, December 23, 2020 at 9:09:20 AM
On Wednesday, December 23, 2020 at 9:09:20 AM UTC-8 Xavier wrote:
> From my experience, naming fields with any Unicode (utf-8) names hasn't
> brought any issues,
>
While $action-setfield allows you to create a field name using almost any
characters, the issue is whether the field name remains
Hi Siniy-Kit, Jeremy,
>From my experience, naming fields with any Unicode (utf-8) names hasn't
brought any issues,
as far as I don't use the EditTemplate (which explicitly refuses non-ascii
characters for naming fields)
but rather an action widget like *action-setfield*. For instance,
<$button>
Hi Siniy-Kit
As you’ve discovered, field names currently only work reliably and consistently
if are composed of the a-z, 0-9, dash and underscore. It is not trivial to fix
because of the way that the code expects to be able to roundtrip fieldnames
into attribute names. I think it would require
Many years ago I try to make new field "цвет" with value "красный" but it
was impossible, because all tiddlers are saved in this format
The `tm-remove-field` message is handled by the FieldManglerWidget. It
removes the specified field..
So our *fields are html attributes*, so they
13 matches
Mail list logo
