I downloaded a profile to use as a base for a new profile (the disc ID matched and pulled up the profile, but mine is a box set content so no upc and the profile that downloaded was by UPC, but thats not the point)

So after changing the profile to disc id, i started verifying some info, and there were a few mistakes in the overview (spelling errors not present on the cover) i figured I'd fix these in the UPC profile as well since I can read the overview from the cover scans. There are two by UPC profiles for this, both with the exact same overview on the back. some words are split because they go onto a second line so in the overview (on the cover) they are entered as extrava-ganza (etc). The one profile removed the dashes from these words, the other has them. What is the proper way. I would think it would be with the dashes because thats 'exactly as appears on the cover' but since the - just shows it continues on the next line, and when transcribing it, it doesn't cross two lines should it be dropped or not?

-Agrare

agreed

Required or not, if the '-' is on the case, it has to be entered into profiler.

We are talking about end-of-line hyphens right?

If an end-of-line hyphen is to be required (and i disagree) then the corresponding carriage return (and possibly line feed, depending on the OS the jacket was created under ) must also be included.  If the jacket has an end-of-line hyphen and i'm required to include that i'd expect No votes if it didn't follow it with a carriage return.  One without the other would not match the jacket exactly and would be wrong by definition.

The full rule (minus exceptions) is "Overviews should match the back of the DVD case exactly, including capitalization of words exactly as it is shown on the back of the case. If words are highlighted in italic or bold on the case, then identify them with ‘single quotation’ marks." which states which typographic characteristics are deemed important by the powers-that-be.

If we must included end-of-line hyphens we must also include all the weird spacing and formatting used to get around photos and other stuff on the jacket.  The program doesn't allow this level of detail/craziness at present.

------------------------------
If we are talking about random, nonsensical hyphens in the middle of words in the middle of sentences, then yes, include them.  Those are funny.

Quoting tweeter:

[...]

Quote:
If we must included end-of-line hyphens we must also include all the weird spacing and formatting used to get around photos and other stuff on the jacket.  The program doesn't allow this level of detail/craziness at present.

That's my take as well: it is formatting/typographic stuff, therefore do not include it.

Quote:

If we are talking about random, nonsensical hyphens in the middle of words in the middle of sentences, then yes, include them.  Those are funny.

Agree.  That would be part of the text.

Quoting Unicus69:

Quote:
"...match the back of the case exactly" means that it should match the back of the case EXACTLY.  Not, unless you believe the hyphen doesn't belong there.  We do not match each carraige return...that which ends each line in the overview...but we do copy each and every character exactly as it is in the overview.

As Max points out, this is done for a reason.  You think it is 'nonsensical', so you want to leave it out.  Other people think copying typos is 'nonsensical', should they be allowed to correct them?  If the answer to that question is 'no', then you can't leave out the hyphen either.  Sorry, but you can't have it both ways. 

Please note i used the word 'nonsensical' for those hyphens i'd keep (the funny ones).

Those that split words were not 'nonsensical' but typographic.  We don't need them.  The Coles have not required justification of the text we enter in Overviews, words wrap to the next line automagically, so no hyphenation is necessary. Typographic elements they require (Bold, Italics, Capitalization) i gladly provide.

(Note: carriage returns and line feeds are characters.  They have the same electronic heft as alphabetic, numeric and typographic characters.  When my profile submission notes are pushing the 1,000 character limit i'm looking for carriage returns i can remove to save space.)

I don't want it both ways.  But if end-of-line hyphens are demanded then the carriage returns are also required, along with the formatting/spacing at the beginning of lines.

This is exactly the insanity that is going on right now with en, em and other dashes.  We are attempting to match the back cover EXACTLY using a tool set that is incapable of doing that.

I think it is time to reevaluate the rules about how the overview text is entered.  What is the purpose of capturing the overview in text?  We have it exactly as it appears on the back cover on the image of the back cover.  So, what else can be gained by having it as text?

The only reasons I can think of having it as text is so that it can be read when the scan is either low-res or is difficult or impossible to scan in a readable manner, or to allow searching.  By including a lot of extra or special characters in it, searching becomes difficult or impossible.  And adding these extra characters makes it quite difficult to read.  So, these efforts to make it match exactly are defeating the very benefits of having the text.

Quoting Unicus69:

Quote:


Text, on the other hand, is not changed based on the size of the field it is being entered into. 

But text is in fact being altered based on the size of the field it is being entered into, in this case.  If the field on the back of the case had been slightly wider, this word would not have been hyphenated.

Hyphenating a word in DVDP in the middle of a line which is not a normally hyphenated word is just stupid.

You have to allow people to use their intelligence to interpret the fact that the hyphen on the case is only there because the word is split between two separate lines on the case.  It is not part of the word if it appears on a single line.

This has nothing to do with correcting spelling errors or typos.