Re: Email versus e-mail

Subject: Re: Email versus e-mail
From: "Burnett S M \(ISeLS\)" <sburnett -at- glam -dot- ac -dot- uk>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Wed, 19 Jul 2006 13:25:40 +0100


Because we publish mostly online we insist on including the hyphen for all e-words, and this is reflected in our Style Guide.

We have to meet accessibility standards (DDA/SENDA) and including the hyphen enables screen-readers to pronounce such words with greater clarity, thus avoiding confusion for our sight-impaired users.

Sue


Sue Burnett
Team Leader, Facilitation & Publishing
e-Support Team
University of Glamorgan
Pontypridd CF37 1DL
Tel: 01443 483640 (direct line)

http://blendedlearning.glam.ac.uk





-----Original Message-----
From: techwr-l-bounces+sburnett=glam -dot- ac -dot- uk -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+sburnett=glam -dot- ac -dot- uk -at- lists -dot- techwr-l -dot- com] On Behalf Of techwr-l-request -at- lists -dot- techwr-l -dot- com
Sent: 19 July 2006 07:00
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: TECHWR-L Digest, Vol 9, Issue 17

Send TECHWR-L mailing list submissions to
techwr-l -at- lists -dot- techwr-l -dot- com

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.techwr-l.com/mailman/listinfo/techwr-l
or, via email, send a message with subject or body 'help' to
techwr-l-request -at- lists -dot- techwr-l -dot- com

You can reach the person managing the list at
techwr-l-owner -at- lists -dot- techwr-l -dot- com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of TECHWR-L digest..."


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Try WebWorks ePublisher Pro for Word today! Smooth migration of legacy
RoboHelp content into your new Help systems. EContent Magazine Decision-
maker review (October 2005) is here: http://www.webworks.com/techwr-l

Doc-To-Help includes a one-click RoboHelp project converter. It's that easy. Watch the demo at http://www.DocToHelp.com/TechwrlList

---


Today's Topics:

1. RE: FW: Email versus e-mail (peter -at- galley -dot- ie)
2. RE: FW: Email versus e-mail (Sankara R)
3. RE: Wikipedia (Jones, Donna)
4. Re: Email versus e-mail (Sandy Nicholson)
5. Re: Wikipedia (Bryan Sherman)
6. Re: RoboHelp, RoboDemo, and Procedural Movies - Please Help
(Surag R)
7. RE: RoboHelp, RoboDemo, and Procedural Movies - Please Help
(Diana Ost)
8. translation (obair81 -at- comcast -dot- net)
9. Re: translation (Cassandra Greer)
10. RE: translation (Jones, Donna)
11. Re: translation (obair81 -at- comcast -dot- net)
12. RE: translation (Wroblewski, Victoria)
13. Fwd: translation (Norm Dancy)
14. RE: RoboHelp, RoboDemo, and Procedural Movies - Please Help
(Sam Stuhlman)
15. Re: translation (Gene Kim-Eng)
16. Translation? (Geoff Hart)
17. RE: translation (obair81 -at- comcast -dot- net)
18. Re: Email versus e-mail (Janice Gelb)


----------------------------------------------------------------------

Message: 1
Date: Tue, 18 Jul 2006 08:25:04 +0100
From: peter -at- galley -dot- ie
Subject: RE: FW: Email versus e-mail
To: david -dot- shenton -at- smithsdetection -dot- com, techwr-l -at- lists -dot- techwr-l -dot- com
Message-ID: <a87a72712db343c0b5675cbed261093d -at- galley -dot- ie>
Content-Type: text/plain; charset=utf-8

I still pronounce it that way - I thought it was illegal, like muffin the mule :-)

Seriously, one of the functions of the hyphen is to prevent mispronumciation, so for me e-mail, co-operative, co-worker ill
stay.

Peter



============================================
Original Message


A few years ago when I first saw the word Coworker my first thought was to pronounce it Cow orker, till I read
further...still amuses me when I see it.





------------------------------

Message: 2
Date: Tue, 18 Jul 2006 02:54:11 -0700 (PDT)
From: Sankara R <ss_rajanala -at- yahoo -dot- com>
Subject: RE: FW: Email versus e-mail
To: "Shenton, David \(DTRN\)" <david -dot- shenton -at- smithsdetection -dot- com>,
David Loveless <daveloveless -at- gmail -dot- com>, techwr-l -at- lists -dot- techwr-l -dot- com
Message-ID: <20060718095411 -dot- 60569 -dot- qmail -at- web61212 -dot- mail -dot- yahoo -dot- com>
Content-Type: text/plain; charset=iso-8859-1


I think television started off with a hyphen, as
did many others? There was a day when to-morrow
was broken in two halves...

Blame the heathens (as did Geoff) but in good
time all hyphens give way to

Talking of confusing compounds, when I came
across "miniseries", being a non-native learner,
I looked up 'minisery' (to no avail).

--- "Shenton, David (DTRN)"
<david -dot- shenton -at- smithsdetection -dot- com> wrote:

>
> A few years ago when I first saw the word
> Coworker my first thought was to pronounce it
> Cow orker, till I read further...still amuses
> me when I see it.
>
> -----Original Message-----
> From:
>
techwr-l-bounces+david -dot- shenton=smithsdetection -dot- com -at- lists -dot- techwr-l -dot- com
>
[mailto:techwr-l-bounces+david -dot- shenton=smithsdetection -dot- com -at- lists -dot- techwr-l -dot- com]
> On Behalf Of David Loveless
> Sent: July 17, 2006 3:19 PM
> To: techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: Re: FW: Email versus e-mail
>
> Bryan mentioned...
>
> "My personal rule is to hyphenate all e-words
> unless they are a company or product name. My
> rationale is that I can't think of any
> hyphenated word that has morphed to no hyphen.
> For example, O-Ring, X-Ray...."
>
> Actually, the linguistic trend is eventually to
> *always* remove the hyphen from a word.
> Hyphenation, like acronyms, tend to simplify
> over the years. The example that comes
> immediately to mind is the word coworker. It
> was originally hyphenated and some style guides
> (AP I
> believe) still insist that it be hyphenated,
> but virtually every major dictionary says no.
> We are seeing the same thing happening right
> now with e-mail and other commonly hyphenated
> words.
>
> As for me, I choose to hyphenate any time that
> there is any doubt at all no matter what the
> style guides or dictionaries say. I think it
> removes the possible confusion over
> pronunciation. I also tend to hyphenate all
> "e-" words for that same reason. Same with our
> "i-"
> words. It's funny now, but my first
> introduction to itunes came about with
> disastrous social consequences. But that's just
> me and my linguistic side overriding the more
> responsible and anal-retentive editing side.
>
> And as a side note, Chicago 15 does mandate the
> hyphen for all "e-"
> terms (7.90 Compounds Formed with Specific
> Terms).
>
> Long Live Descriptivism!!!
>
> Dave
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> WebWorks ePublisher Pro for Word features
> support for every major Help format plus PDF,
> HTML and more. Flexible, precise, and efficient
> content delivery. Try it today!.
> http://www.webworks.com/techwr-l
>
> Doc-To-Help includes a one-click RoboHelp
> project converter. It's that easy. Watch the
> demo at http://www.DocToHelp.com/TechwrlList
>
> ---
> You are currently subscribed to TECHWR-L as
> david -dot- shenton -at- smithsdetection -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit
>
http://lists.techwr-l.com/mailman/options/techwr-l/david.shenton%40smithsdetection.com
>
>
> To subscribe, send a blank email to
> techwr-l-join -at- lists -dot- techwr-l -dot- com
>
> Send administrative questions to
> lisa -at- techwr-l -dot- com -dot- Visit
> http://www.techwr-l.com/techwhirl/ for more
> resources and info.
>
>
>
______________________________________________________________________
> This email has been scanned by the MessageLabs
> Email Security System.
> For more information please visit
> http://www.messagelabs.com/email
>
______________________________________________________________________
>
> </table> </Pre>
> <HTML>
> <br>
> <br>
>
************************************************<br>
> The information contained in, or attached to,
> this e-mail, may contain confidential
> information and is intended solely for the use
> of the individual or entity to whom they are
> addressed and may be subject to legal
> privilege. If you have received this e-mail in
> error you should notify the sender immediately
> by reply e-mail, delete the message from your
> system and notify your system manager. Please
> do not copy it for any purpose, or disclose its
> contents to any other person. The views or
> opinions presented in this e-mail are solely
> those of the author and do not necessarily
> represent those of the company. The recipient
> should check this e-mail and any attachments
> for the presence of viruses. The company
> accepts no liability for any damage caused,
> directly or indirectly, by any virus
> transmitted in this email.<br>
>
************************************************<br>
> </HTML>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> WebWorks ePublisher Pro for Word features
> support for every major Help
> format plus PDF, HTML and more. Flexible,
> precise, and efficient content
> delivery. Try it today!.
> http://www.webworks.com/techwr-l
>
> Doc-To-Help includes a one-click RoboHelp
> project converter. It's that easy. Watch the
> demo at http://www.DocToHelp.com/TechwrlList
>
> ---
> You are currently subscribed to TECHWR-L as
> ss_rajanala -at- yahoo -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit
>
http://lists.techwr-l.com/mailman/options/techwr-l/ss_rajanala%40yahoo.com
>
>
> To subscribe, send a blank email to
> techwr-l-join -at- lists -dot- techwr-l -dot- com
>
> Send administrative questions to
> lisa -at- techwr-l -dot- com -dot- Visit
> http://www.techwr-l.com/techwhirl/ for more
> resources and info.
>
>



Sankara S Rajanala
+91 98863 12366
----------------
Tina: I am an experienced technical writer.
You are an intern and a rodent, respectively.




__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com


------------------------------

Message: 3
Date: Tue, 18 Jul 2006 06:04:32 -0500
From: "Jones, Donna" <DJones -at- zebra -dot- com>
Subject: RE: Wikipedia
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Message-ID:
<56BB7301E340C54291D9728333B94F090752BF90 -at- 03s03exch02 -dot- zebra -dot- lan>
Content-Type: text/plain; charset="us-ascii"

The link below came in a newsletter that I received this morning. I was
amused because the topic was just discussed here.

http://www.mercola.com/2006/jul/18/dont_rely_on_the_wikipedia.htm

- CONFIDENTIAL-
This email and any files transmitted with it are confidential, and may also be legally privileged. If you are not the intended recipient, you may not review, use, copy, or distribute this message. If you receive this email in error, please notify the sender immediately by reply email and then delete this email.


------------------------------

Message: 4
Date: Tue, 18 Jul 2006 12:07:49 +0100
From: Sandy Nicholson <sandy -at- ambertext -dot- co -dot- uk>
Subject: Re: Email versus e-mail
To: techwr-l -at- lists -dot- techwr-l -dot- com
Message-ID: <CBF114F0-ACE8-480E-9846-B9445669DF49 -at- ambertext -dot- co -dot- uk>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed

Sankara Rajanala wrote:

> There was a day when to-morrow was broken in two halves...

And `to-day' and `to-night' as well - and it wasn't that long ago.

> Talking of confusing compounds, when I came across "miniseries",
> being a non-native learner, I looked up 'minisery' (to no avail).

Even as a native speaker, I was thrown by that one, with my eye at
first seeing at as a strange hybrid of `ministries' and `miseries'. I
then pronounced it with the stress on the first syllable and with the
next two syllables having an unstressed, indistinct vowel sound
(somewhat like `missionaries'). After a few seconds, I did get it -
without having to resort to a dictionary - but it would have been
clearer to me with a hyphen. (Perhaps the word's not in such common
use on this side of the Atlantic though.)

Having said that, I'm one of those uncouth people who likes to spell
`email' without a hyphen.* I do sympathise with those who then start
reading it with an unstressed `e' (as in `emit', `emancipate' or
`emasculate'), but I'm sure they will get used to it in the end. :o)
There are a couple of words that always trip me up in a similar way -
of course, I can't bring them to mind at the moment.

* I can at least count on Oxford University Press to support me in
this, though. In the New Oxford Dictionary for Writers and Editors,
they list `email' as their preferred spelling (but note that it can
also be spelt `e-mail').

Best wishes,
Sandy

Ambertext, 2/Gf Bruntsfield Crescent, Edinburgh EH10 4EZ, Scotland
+44 (0) 131 447 9257 http://www.ambertext.co.uk/ sandy -at- ambertext -dot- co -dot- uk
Sole proprietor: Alexander J Nicholson


------------------------------

Message: 5
Date: Tue, 18 Jul 2006 07:25:43 -0400
From: "Bryan Sherman" <bsherm -at- gmail -dot- com>
Subject: Re: Wikipedia
To: "Jones, Donna" <DJones -at- zebra -dot- com>
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Message-ID:
<1ee5927a0607180425r41a37c84xbaee74a17259e757 -at- mail -dot- gmail -dot- com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

That is very interesting, especially since he is not treated well on
Wikipedia (though kudos for him linking to his article in Wikipedia
straight from his editorial).

Personally I find Wikipedia a mixed bag, and certainly take any
entries on controversial figures and/or subjects with a HUGE grain of
salt.

On 7/18/06, Jones, Donna <DJones -at- zebra -dot- com> wrote:
> The link below came in a newsletter that I received this morning. I was
> amused because the topic was just discussed here.
>
> http://www.mercola.com/2006/jul/18/dont_rely_on_the_wikipedia.htm
>


------------------------------

Message: 6
Date: Tue, 18 Jul 2006 21:07:34 +0530
From: "Surag R" <suragtechwriter -at- gmail -dot- com>
Subject: Re: RoboHelp, RoboDemo, and Procedural Movies - Please Help
To: Anthony <italian_scribbles -at- yahoo -dot- com>
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Message-ID:
<2bae94b00607180837v23c9da91l7fe05187c263ab81 -at- mail -dot- gmail -dot- com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi Tony,

The new version of RoboDemo is called Captivate. It was a Macromedia product
and now since Adobe has taken over Macromedia, it is an Adobe product. It
does a pretty good job among the "screen casting tools". There is an option
for simulation too where the users can actually do what they have seen.
There are advanced features like "quizzes" too.

There are competitors for Captivate like Camtasia, TurboDemo, Viewlet
Builder, and so on. However, they don't have some of the"rich features" of
Captivate.

If you don't want to have many such rich features, but just an ordinary
screen capture video, then you may go for freely available "Wink".

The best output format that could go embedded in online help files created
from RoboHelp will be the .swf flash format.

Thanks,
Surag


------------------------------

Message: 7
Date: Tue, 18 Jul 2006 11:39:43 -0400
From: "Diana Ost" <Diana -dot- Ost -at- msmcorp -dot- com>
Subject: RE: RoboHelp, RoboDemo, and Procedural Movies - Please Help
To: "Anthony" <italian_scribbles -at- yahoo -dot- com>
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Message-ID:
<E1F0717C85B5554CAF81E4CC609F3A7915659F7E -at- mercedes -dot- msmcorp -dot- com>
Content-Type: text/plain; charset="us-ascii"


Also, as replied to Tony off-list, RoboHelp Office 5.02 has a built-in
Software Video Camera (under the Tools tab) that works reasonably well.
It's not fancy, but it will show the screen clicks, menus, etc.

Diana Ost
Technical Writer/Reporting Analyst
Production Administration
Market Street Mortgage Corporation
diana -dot- ost -at- msmcorp -dot- com
Phone (727) 431-7209
Fax (727) 724-9096
2650 McCormick Drive, Suite 200
Clearwater, Florida 33759





This message and any attachments may contain confidential or privileged
information and are only for the intended recipient of this message. If
you are not the intended recipient, please notify the sender by return
email or phone, and delete or destroy this and all copies of this
message and all attachments. Any unauthorized disclosure, use,
distribution, or reproduction of this message or any attachments is
prohibited and may be unlawful.




------------------------------

Message: 8
Date: Tue, 18 Jul 2006 16:33:09 +0000
From: obair81 -at- comcast -dot- net
Subject: translation
To: techwr-l -at- lists -dot- techwr-l -dot- com (techwr-l -at- lists -dot- techwr-l -dot- c)
Message-ID:
<071820061633 -dot- 12168 -dot- 44BD0D45000387D700002F882216551406CEC89D070E0D01 -at- comcast -dot- net>


Is there any particular reason why a translated user manual for a communications product would not include the tech specs appendix and the glossary?

I ask because both, especially the tech specs, are full of terms that cannot be translated. So I am unsure of the value.

What have other folks done?

Thanks.

best,
Paul


------------------------------

Message: 9
Date: Tue, 18 Jul 2006 18:49:24 +0200
From: "Cassandra Greer" <cassandra -at- greer -dot- de>
Subject: Re: translation
To: obair81 -at- comcast -dot- net, techwr-l -at- lists -dot- techwr-l -dot- com
Message-ID: <20060718164924 -dot- 73440 -at- gmx -dot- net>
Content-Type: text/plain; charset="iso-8859-1"

Hi Paul

> Is there any particular reason why a translated user manual for a
> communications product would not include the tech specs appendix and the glossary?
>
> I ask because both, especially the tech specs, are full of terms that
> cannot be translated. So I am unsure of the value.
>
> What have other folks done?

I find it hard to imagine that there is nothing in the tech specs and the glossary that shouldn't be translated. Even if the terms aren't translatable, ie the target language uses the English terms, there are usually words around them esp in the glossary. The glossary may be especially important for those who don't have a perfect grasp of English and may have to be expanded for that reasonh. And in the specs, number formats and certain values may have to be localized - it very much depends on the target language/culture. I translate a lot of tech specs and they are full of untranslatable things but there are a lot of other things that need to be translated.

YMMV

Cass :)


--
Cassandra Greer
Technical Translation and Documentation
Spilhofstr. 16
81927 München
+49 (089) 94004794
cassandra (at) greer.de
cassandragreer (at) mac.com


------------------------------

Message: 10
Date: Tue, 18 Jul 2006 11:49:06 -0500
From: "Jones, Donna" <DJones -at- zebra -dot- com>
Subject: RE: translation
To: "techwr-l -at- lists -dot- techwr-l -dot- c" <techwr-l -at- lists -dot- techwr-l -dot- com>
Message-ID:
<56BB7301E340C54291D9728333B94F090752C1D5 -at- 03s03exch02 -dot- zebra -dot- lan>
Content-Type: text/plain; charset="us-ascii"

Paul,

In a glossary, maybe the terms can't be translated, but the definitions
can. Just don't define one term with other terms that don't translate or
you won't be helping your users.

To make the tech specs usable for people who don't speak English, make
sure that any term that can't be translated is in the glossary.

Donna

- CONFIDENTIAL-
This email and any files transmitted with it are confidential, and may also be legally privileged. If you are not the intended recipient, you may not review, use, copy, or distribute this message. If you receive this email in error, please notify the sender immediately by reply email and then delete this email.


------------------------------

Message: 11
Date: Tue, 18 Jul 2006 16:55:21 +0000
From: obair81 -at- comcast -dot- net
Subject: Re: translation
To: techwr-l -at- lists -dot- techwr-l -dot- com (techwr-l -at- lists -dot- techwr-l -dot- c)
Message-ID:
<071820061655 -dot- 28330 -dot- 44BD12790006950E00006EAA2216551406CEC89D070E0D01 -at- comcast -dot- net>


Terms like Ethernet, countless acronyms, and so on.

I am leaning to having these pieces translated, especially based on folks' comments so far.



-------------- Original message ----------------------
From: Norm Dancy <norm -at- navix -dot- jp>
> I am not a translator but edit completed translations. The languages
> are Japanese and English. I can't imagine that there are any terms or
> specifications that 'cannot be translated.' What types of information
> do you refer to?
> On Jul 19, 2006, at 1:33 AM, obair81 -at- comcast -dot- net wrote:
>
> > I ask because both, especially the tech specs, are full of terms that
> > cannot be translated. So I am unsure of the value.
> >
>
> Norm Dancy
>
> Cell phone: +81 (0)90-9960-4445
> Seattle: +1 360-519-5683
> Seattle: +1 425-906-3510
> Do Not Call: +1 303-607-7527
> SIP Phone Number: 1-747-668-2200
>




------------------------------

Message: 12
Date: Tue, 18 Jul 2006 12:08:40 -0500
From: "Wroblewski, Victoria" <victoria_wroblewski -at- usr -dot- com>
Subject: RE: translation
To: <obair81 -at- comcast -dot- net>, "techwr-l -at- lists -dot- techwr-l -dot- c"
<techwr-l -at- lists -dot- techwr-l -dot- com>
Message-ID: <28019CFDEDBAF3459A65C7833F3CA8983EBF7D -at- usrs121 -dot- usr -dot- com>
Content-Type: text/plain; charset="us-ascii"

-----Original Message-----
From: obair81 -at- comcast -dot- net
Sent: Tuesday, July 18, 2006 11:55 AM
Subject: Re: translation

> Terms like Ethernet, countless acronyms, and so on.
>
> I am leaning to having these pieces translated, especially based on
folks' > comments so far.

We translate all of our stuff in to up to 16 different languages... if
you have a translation company that knows what they are doing, there is
no reason they should not be able to translate things.

For instance, French does have customized acronyms. They use those for
French. If a language does not have a translation, we instruct the
translators to provide a translation for the acronyms in-line with the
rest of the text (Acronym, followed by English text, followed by
translation). In the specific case of "Ethernet", languages that do not
have a translated word, like Turkish, just use "Ethernet".

- Victoria


This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately.

Thank you. USRobotics


------------------------------

Message: 13
Date: Wed, 19 Jul 2006 02:14:20 +0900
From: Norm Dancy <norm -at- navix -dot- jp>
Subject: Fwd: translation
To: techwr-l -at- lists -dot- techwr-l -dot- c <techwr-l -at- lists -dot- techwr-l -dot- com>
Message-ID: <4fe3bbfa4e7ecbe6ddc4a95033cb1cc9 -at- navix -dot- jp>
Content-Type: text/plain; charset=US-ASCII; format=flowed

I'm sorry everyone. I sent the following response to obair81 without
sending it to the group too. My mistake. I didn't realize I had to also
include the address for the group. My note appears below.

Begin forwarded message:

> From: Norm Dancy <norm -at- navix -dot- jp>
> Date: July 19, 2006 2:11:17 AM JST
> To: obair81 -at- comcast -dot- net
> Subject: Re: translation
>
> I don't know about any other languages but 'Ethernet' does have a
> transliterated word in Japanese. It is pronounced somewhat close to
> the English but it is not written in English. '12 V ac' in Japanese
> would be properly rendered as '12VAC' in Japanese. So when it gets
> right down to specs., at least for Japanese, the way of presenting the
> information does indeed need to be translated even if that translation
> results only in a transliteration or alteration of the style of
> presentation. A knowledgeable translator would be able to render it
> into the target language without a problem. A less-than-capable
> translator would have problems.
>
> Even the presentation of a table of specifications is different in
> Japanese. In Japanese the label (Weight) appears on the left column,
> the colon (:) is in the center, aligned vertically, and the value is
> listed to the right (95g). They wouldn't think of placing a colon
> immediately following the word to which it is attached. Although not
> technically translation things are still done differently in the two
> languages and a qualified translator (and maybe typesetter) is still
> required.
>
>
> On Jul 19, 2006, at 1:55 AM, obair81 -at- comcast -dot- net wrote:
>
>> Terms like Ethernet, countless acronyms, and so on.
>
> Norm Dancy
>
> Cell phone: +81 (0)90-9960-4445
> Seattle: +1 360-519-5683
> Seattle: +1 425-906-3510
> Do Not Call: +1 303-607-7527
> SIP Phone Number: 1-747-668-2200
>
>

Norm Dancy

Cell phone: +81 (0)90-9960-4445
Seattle: +1 360-519-5683
Seattle: +1 425-906-3510
Do Not Call: +1 303-607-7527
SIP Phone Number: 1-747-668-2200



------------------------------

Message: 14
Date: Tue, 18 Jul 2006 13:24:36 -0400
From: "Sam Stuhlman" <Sam -dot- Stuhlman -at- w7optics -dot- com>
Subject: RE: RoboHelp, RoboDemo, and Procedural Movies - Please Help
To: "Anthony" <italian_scribbles -at- yahoo -dot- com>,
<techwr-l -at- lists -dot- techwr-l -dot- com>
Message-ID:
<F1FA1476AD059B4E968D9A1DD34C968C15F661 -at- w7server22 -dot- wave7optics -dot- com>
Content-Type: text/plain; charset="us-ascii"

I use Camtasia, which allows you to produce the movie in various
formats. You'll need to figure out somehow the format that is easiest
for most users. I did that by testing within my group. I gave them the
files with no instructions and waited to see who asked what. Then, I
sent 2 or 3 formats at a time and they decided what looked better. I
would package the movies separately and link them to the help. That way
if you need to change one, you just need to email a new file.

Also, you need to consider the users' computer platforms, monitor
resolution, etc. Is anyone using a Mac? Are they gamers with high-res or
testers with old cast off equipment?

Hope that helps.

-----Original Message-----
From: Anthony [mailto:italian_scribbles -at- yahoo -dot- com]
Sent: Monday, July 17, 2006 5:18 PM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: RoboHelp, RoboDemo, and Procedural Movies - Please Help

Hello Everyone,

I would like to add some "movies" of a variety of procedures in my
company's help system and am looking for some advice on the best method
and tools for the job. The help system itself was created on RoboHelp
HTML 5.0.1. We currently do not have RoboDemo.

Is it best to create the "movies" using RoboDemo software that is sold
separately or import the "movies" in .AVI, .MOV or .MPEG format directly
into their RoboDemo projects or (if possible) into the help system once
they have been generated by another software package?

If the latter, can it be done without RoboDemo and what is the best
video format to keep size to a minimum while delivering a high quality
image?

Further, if the latter, what aftermarket software would you suggest for
constructing the "videos" to be imported?

Thank you so much for the help.

- Tony

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com



------------------------------

Message: 15
Date: Tue, 18 Jul 2006 10:39:54 -0700
From: "Gene Kim-Eng" <techwr -at- genek -dot- com>
Subject: Re: translation
To: <obair81 -at- comcast -dot- net>, "techwr-l -at- lists -dot- techwr-l -dot- c"
<techwr-l -at- lists -dot- techwr-l -dot- com>
Message-ID: <001f01c6aa91$2e1c3c20$a320c90a -at- viragelogic -dot- com>
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
reply-type=original

If you mean that some of the technical terms have no equivalent in
the target language, then I would presume that those terms are not
being translated in the body of the manual either. So list the terms
in the glossary the same way they appear in the body of the manual
and then translate their definitions.

Gene Kim-Eng


----- Original Message -----
From: <obair81 -at- comcast -dot- net>
To: "techwr-l -at- lists -dot- techwr-l -dot- c" <techwr-l -at- lists -dot- techwr-l -dot- com>
Sent: Tuesday, July 18, 2006 9:33 AM
Subject: translation


> Is there any particular reason why a translated user manual for a
> communications product would not include the tech specs appendix and the
> glossary?
>
> I ask because both, especially the tech specs, are full of terms that
> cannot be translated. So I am unsure of the value.




------------------------------

Message: 16
Date: Tue, 18 Jul 2006 13:47:19 -0400
From: Geoff Hart <ghart -at- videotron -dot- ca>
Subject: Translation?
To: TECHWR-L <techwr-l -at- lists -dot- techwr-l -dot- com>, obair
<obair81 -at- comcast -dot- net>
Message-ID: <4fc31afaa3b67b03d121b72e24540e23 -at- videotron -dot- ca>
Content-Type: text/plain; charset=US-ASCII; format=flowed

Paul wondered: <<Is there any particular reason why a translated user
manual for a communications product would not include the tech specs
appendix and the glossary?>>

If both sections are useful to English readers, they'll be useful to
readers in all other languages. So in that context, there's no good
reason that I'm aware of to avoid translating this material. Possibly a
file just went MIA somewhere along the way?

<<I ask because both, especially the tech specs, are full of terms that
cannot be translated. So I am unsure of the value.>>

The value is twofold. First, for those things that cannot be
translated*, a definition is provided in the reader's own language.
That lets them understand the meaning of the untranslated term. Second,
for the things that can be translated, you have provided a translation.

* I assume you mean that the terms must be left in the original
language (e.g., because they're part of the interface)? If not, there
are darn few things that cannot be translated. There are many that
cannot be translated in a single word, but you can usually describe the
meaning in several words.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --
Geoff Hart ghart -at- videotron -dot- ca
(try geoffhart -at- mac -dot- com if you don't get a reply)
www.geoff-hart.com
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -



------------------------------

Message: 17
Date: Tue, 18 Jul 2006 18:21:57 +0000
From: obair81 -at- comcast -dot- net
Subject: RE: translation
To: "techwr-l -at- lists -dot- techwr-l -dot- c" <techwr-l -at- lists -dot- techwr-l -dot- com>
Message-ID:
<071820061821 -dot- 25609 -dot- 44BD26C5000B5EC4000064092216557996CEC89D070E0D01 -at- comcast -dot- net>


I really appreciate all the comments.

I will definitely have the glossary and tech specs translated.

best,
Paul

-------------- Original message ----------------------
From: "Jones, Donna" <DJones -at- zebra -dot- com>
> Paul,
>
> In a glossary, maybe the terms can't be translated, but the definitions
> can. Just don't define one term with other terms that don't translate or
> you won't be helping your users.
>
> To make the tech specs usable for people who don't speak English, make
> sure that any term that can't be translated is in the glossary.
>
> Donna
>
> - CONFIDENTIAL-
> This email and any files transmitted with it are confidential, and may also be
> legally privileged. If you are not the intended recipient, you may not review,
> use, copy, or distribute this message. If you receive this email in error,
> please notify the sender immediately by reply email and then delete this email.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> WebWorks ePublisher Pro for Word features support for every major Help
> format plus PDF, HTML and more. Flexible, precise, and efficient content
> delivery. Try it today!. http://www.webworks.com/techwr-l
>
> Doc-To-Help includes a one-click RoboHelp project converter. It's that easy.
> Watch the demo at http://www.DocToHelp.com/TechwrlList
>
> ---
> You are currently subscribed to TECHWR-L as obair81 -at- comcast -dot- net -dot-
>
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit
> http://lists.techwr-l.com/mailman/options/techwr-l/obair81%40comcast.net
>
>
> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
>
> Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit
> http://www.techwr-l.com/techwhirl/ for more resources and info.
>




------------------------------

Message: 18
Date: Wed, 19 Jul 2006 14:50:03 +1000
From: Janice Gelb <janice -dot- gelb -at- sun -dot- com>
Subject: Re: Email versus e-mail
To: TECHWR-L <techwr-l -at- lists -dot- techwr-l -dot- com>
Message-ID: <44BDB9FB -dot- 6060405 -at- sun -dot- com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Geoff Lane wrote:
> On Monday, July 17, 2006, Jones, Donna wrote;
>
>
>>I don't know why, but the abbreviation "email" instead of "e-mail" bugs
>>me, though I know that both are common.
>
> ---
>
> FWIW, I asked the same question when I saw a recent post. MS Manual of
> style 2nd Edition V3 requires the hypen, as does every style guide
> that I've used over the last five or six years. That said, I see an
> increasing incidence of "email" in informal correspondence and I
> suspect that it's only a matter of time before that becomes the
> preferred version <g>
>

At Sun, we gave up on the hyphen in email as of the 2003 edition
of our internal style guide. The Editorial Forum ultimately
decided that the hyphen after Internet terms with "i-" and
"e-" was unnecessary due to the words passing into common
usage. As other people have noted, the usual path is for
hyphenated neologisms to gradually lose the hyphen as
they migrate outside the purely technical environment.

***********************************************************
Janice Gelb | The only connection Sun has with
janice -dot- gelb -at- sun -dot- com | this message is the return address.

"These are my opinions. If they were the Biblical
truth, your bushes would be burning -- Randy Lander


------------------------------

_______________________________________________
You are currently subscribed to
TECHWR-L.
To unsubscribe send a blank email to
http://lists.techwr-l.com/mailman/listinfo/techwr-l
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.

End of TECHWR-L Digest, Vol 9, Issue 17
***************************************
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l

Doc-To-Help includes a one-click RoboHelp project converter. It's that easy. Watch the demo at http://www.DocToHelp.com/TechwrlList

---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40infoinfocus.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.


Follow-Ups:

Previous by Author: Re: Fwd: translation
Next by Author: Guidelines for Key Words
Previous by Thread: RE: FW: Email versus e-mail
Next by Thread: RE: Eddress (was Email versus e-mail)


What this post helpful? Share it with friends and colleagues:


Sponsored Ads