Family Historian User Group

I hadn't got around to checking is VS Code supported LUA, but will as I have it installed already, and see how that goes. Recommended extensions: Lua by Sumneko. I believe that now also does code formatting but I've got used to Stylua. I can share it as a text file if you wish -- will need renaming...

I use Visual Studio Code with some relevant extensions. It integrates with Github, so I keep my master outside the FH plugins folder, and only transfer files there for debugging. One particular strength of this is that, if you set up the VS Code 'workspace' appropriately, it can recognise functions ...

P.S. Works in FH7 doesn't mean 'does everything conceivable in FH7'.

Via the plugin store, but probably simpler just to fork it yourself.

tatewise wrote: ↑21 Mar 2024 15:22 My guess is if you adjust the PC system date format to dd/mm/yyyy then AS will work correctly.

Seems a bit drastic... perhaps Gary could simply move to the UK instead

I don't believe we should be specifying formatting, as CP will have their own 'design guide'. Perhaps something like

"When present in a template, the 'label' should be visually distinct from the fields which is associated with."

I’d not looked at the Store author list before. Around half the names were unfamiliar to me, and don’t have any plugins listed. Presumably, they were contractors employed by CP at various times that have not been deleted from the system? Check the Language Packs, Mark. On the subject of iuplua, I s...

I can see that some people with very complex templates might benefit from this.

Gary_G wrote: ↑20 Mar 2024 16:49 Helen;

Just so we are clear. I am not suggesting anything to with adding "qualifiers" to field-names.

I didn't think you were, but expected it to be suggested as a workaround.

I'd be opposed to adding qualifiers to field names(as a plugin author who wishes people would use the same names for the same fields!).

And yes, I understand why you're reluctant to post a specific example, but it does make it hard for people to see the utility of what you're proposing.

Helen; I think the you are missing the point of improving the visibility of groups of fields. "well-crafted prompt" cannot fulfill the same purpose unless each and every field-name contains the prefix that I would propose be able to be added as a label for the group of fields. Adding such...

This is definitely off-topic, I'm afraid. Only open topics that are about: * using FH or complementary products (including plugins) * exchanging data between FH and other products and services * understanding how FH can be used to achieve functionality you're familiar with in other products * using ...

I'm struggling to see what this adds to a well crafted prompt that could include that Label. Perhaps Gary_G can cite an example of a template that needs it?

tatewise wrote: ↑18 Mar 2024 10:59 My first comment is that adding headstone images to the Individual Media tab is unusual.

Not that unusual - I do it.

Is this a candidate for the 'Maintaining the KnowledgeBase' forum? It falls between two stools. After a mention of the Knowledge Base (which used correct V6 terminology "Shared Note" and has now been updated to reflect V7's move away from that) it then goes on to suggest interface changes...

Always happy for people to improve the KB. There's a link on the KB under Contribute to Request an Editor's account.

P.S. I've tinkered with the article on Notes -- see if you think it's better now.

Try creating a custom Source Template Query.

Use =LastUpdated() for the Updated column.

Helen’s point about unknown e-mail addresses may be a red herring, as messages are clearly shown as sent from FHUG in my experience. Perhaps it should also be made clear that if you send a PM, it exposes your actual registered e-mail address as the reply address. As you pointed out, any private mes...

Curious to see if any bookseller in the UK other than Amazon (which I boycott) will have the book for sale. EE's publisher has already told me if I want it in Canada I'll have to buy it from Jeff Bezos's monolith. I'm still not sure this new edition will convince me to return to ESM's citation styl...

Common courtesy, Mark? Plus common sense.

If I receive an unsolicited email from an address that I'm not familiar with, it's deleted unread.

Other people might report it as spam -- and the last thing Jane needs is for FHUG to be reported as a source of spam.

Mark, People may not have realised that receiving private messages is enabled by default; it's not uncommon for the admins to receive reports of private messages as unwanted, hence this post. Ideally, all contact would be via the forums, where it's available for other to learn from. If you're happy ...

tatewise wrote: ↑16 Mar 2024 12:56 In my defence m'lord, the OP said nothing about Strathclyde format or the Source generic Author field.

Sorry, Mike. I assumed the reference to an organisation made it clear.

Gary_G wrote: ↑16 Mar 2024 12:38 This is because (beyond the names of organizations) that field could contain one or more names. In the footnotes, this poses no issues. In the bibliography, only the first name is reversed. If it is the only author, it just ends in a period.

I feared that might be the case.

IMO Names should always be entered in Name fields using the FH/GEDCOM convention Given /Surname/ AFAIK, it's also factually incorrect. All I could find in GEDCOM 5.5.1 is The name value is formed in the manner the name is normally spoken, with the given name and family name (surname) separated by s...

I can't see any way other of handling this at present other than entering the Author as it should be displayed, not as it is... So Fred Bloggs would be entered as Bloggs, Fred. I can't remember (Gary_G will know) if there's a requirement for the names to be handled in different ways in e.g. a footn...