DOCPROPERTY field switches and non-breaking hyphens and spaces

[chapteryx]

I have created some custom properties for data that will be use
repeatedly in my document. Because this document can function as
template, this is very useful when creating a similar document as th
first.
I just change the docproperty values, refresh the document, and it'
good to go.

But I've run into a problem with non-breaking characters.
If the value that I enter into the custom property field value
(Prepare, Properties, Document Properties, Advanced Properties, Custom
Value) contains a non-breaking hyphen, then that non-breaking hyphen i
transformed into another character that LOOKS like a hyphen, but is NO
a non-breaking hyphen.
As an example, the company documentation standards require a format suc
as ABC-123 for the product names. I need to use a non-breaking hyphen i
the product name, but I can not find a way to "preserve" the characte
set or font or something in order to faithfully reproduce th
non-breaking hyphen in the actual document text.

"If a paragraph talking about the ABC-123 product needs to wrap,
then I do not want to see any of the wrapped lines cause the ABC-
123 custom property value get split over seperate lines, like it just
did there. That just looks all wrong, and is one of the reasons why a
non-breaking hyphen exists in the first place."

I've searched through MS WORD forums and technical help, and I did fin
a large collection of "optional switches" that can be applied t
DOCPROPERTY fields, including MERGEFORMAT and CHARFORMAT among others.

But there's nothing available, it would seem, to allow me to retai
those non-breaking hyphens in the custom property value once it's bee
inserted into the document text.

Any advice would be most welcome - I suspect that I've hit a
unresolvable bug.

If there is a switch or a way to faithfully reproduce a non-breakin
hyphen in the text from a custom property, then I would hope to find
way to specify that quickly too. If I need to CTRL-F9 and manually edi
each field, then that's okay, I guess. But switching on a "retai
formatting" switch somewhere in the Windows Registry just once and fo
all would be a godsend.

Thanks in advance for any help (or even commiserations )!

 

[Peter T. Daniels]

I can't help you _at all_, but I have a different problem with non-breaking
hyphens. In linguistics, we often have to put a hyphen at the beginning of
an ending (such as -ing) when it's being talked about all by itself, and
it causes the word before it to move to the next line -- it doesn't recognize
that "non-breaking" doesn't mean 'don't break after a space'! (That's what
non-breaking space would be for, if I wanted to accomplish that.)

But I've run into a problem with non-breaking characters.

[a very annoying problem]

 

[chapteryx]

I can't help you _at all_, but I have a different problem wit
non-breaking
hyphens.

Well, I don't mean to be rude, and your problem is equally legitimate
but why did you reply to my message, and not open a new thread?

Could you possibly remove your reply, please, given as it doesn't relat
_at all_ to the topic of the thread

 

[Peter T. Daniels]

Peter T. Daniels;494885 Wrote:

Well, I don't mean to be rude, and your problem is equally legitimate,
but why did you reply to my message, and not open a new thread?

Could you possibly remove your reply, please, given as it doesn't relate
_at all_ to the topic of the thread ?

It sounds like you have no idea how newsgroups work. Messages cannot be
"removed," and there is no reason related queries shouldn't be piggybacked.

I can't help observing that you didn't even bother to mention the version
of MSWord you're using.

 

[chapteryx]

Ah, well, allow me to retort, and then I shan't bother you anymore.
I'm sure you think you're well-intentioned and I don't blame you fo
your response.
I know quite well how a newgroup works, thanks, which is precisely why
wrote what I did.
I manage the odd newsgroup myself, and I can remove messages when s
requested. That's what the filthy big "REPORT INAPPROPRIATE CONTENT
button is all about. And an administrator can remove what he/sh
wishes.
And an administrator can even sometimes partially delegate such access.
Secondly, some newsgroup software does allow you to remove your ow
posts, sometimes whenever you like, and sometimes only if there's bee
no response to your message yet.
Thirdly, it is a common feature in newsgroup software to allow reader
to list all questions that have not yet had a response. Such message
allow contributors to quickly assist when there has been no response t
date.
Because you posted a largely useless response, albeit interesting i
itself, there might well be many who consider that even reading m
request (already answered in some fashion) is not top priority.
What's more, you're unlikely to get a response to your own problem b
piggybacking on an as-yet unproductive thread.
I just don't really understand why you didn't open a new thread, sinc
it's really quite a different issue, and nothing to do with Custo
Properties.

But you know, I don't really mind, and I'm not really upset about it a
all.
But you have a high posting count so maybe you can reflect on th
unintended and perhaps unexpected consequences of your activities o
others.

Last of all, dear Sir, you fail to mention the version of WORD that yo
have a problem with too, so calling my kettle black is a little inflate
of you in the circumstance.
I wish you good luck to solve your non-breaking space problem.

PS: The problem I describe occurs in the three most recent versions o
WORD, and though you are quite correct to note my omission, it's no
really of any consequence

 

[Peter T. Daniels]

Maybe some of what you say is correct for some moderated newsgroups. This
isn't one.

Clearly you posted blindly here, without reading the newsgroup for a few
days or weeks as is normal practice. You seem to be harboring the fantasy
that hundreds of people are posting questions and answers around the
clock.

I could indeed "cancel" my post so that other Google Groups users would
not see it. That does not remove it from newsgroups in general.

Evidently you also understand little about the structure of MSWord
itself, if you don't realize that the version can be _very_ important
for an intricate and specialized question like yours.