Re: Umlaut--Success!

2007-03-02 Thread Devin Asay

Signe,

On Mar 2, 2007, at 1:33 AM, [EMAIL PROTECTED] wrote:


Good morning Devin
I have still got no success (on Mac10.4.8 and Rev 2.6)
The fld "result" is set to "verdana,unicode", but only n appears.  
Could it be

that I need Rev 2.8?


Indeed it does not work with Rev v. < 2.7. There were some  
enhancements to unicode for 2.7 that seem to be necessary to make  
this work.


However, I have not tried your suggested settings with "Enable the  
Unicode Hex
Input method in the International system prefs under the input tab.  
This will
cause the Unicode Hex Input method to appear in the input menu (the  
one with the
little flags on the right side of the menubar.) First because my  
system is in
Norwegian and I did not find the input menu, and secondly because  
my potential
users cannot be bothered by doing this. (Or am I completely wrong?  
Is this

setting in Revolution somewhere?)


No, it's a Mac OS X setting. Open System Preferences, click on  
International, then Input Menu. As soon as you enable at least one of  
the items under Input Menu the input (flag menu, right next to the  
time on the right end of the menu bar) will become visible.


Do your users need to be able to type the n-with-umlaut into a field?  
If so, you could provide a button that inserted one, using the method  
I've described. If you decide to go that route I'd be happy to make a  
sample stack for you that does this.


Regards,

Devin


Quoting Devin Asay <[EMAIL PROTECTED]>:



On Mar 1, 2007, at 10:02 AM, Mark Schonewille wrote:


Hi Devin,

This doesn't work for me (Mac OS X 10.4.8, Rev 2.7.8).

The # is replaced by n instead of n-umlaut.


Right, after I sent this message, I discovered that the first # in
the field does not get replaced by the n-umlaut, only an n. It works
for every other # after the first one. (Go figure!) Here's a
workaround that worked for me:

on mouseUp
   get "#"&fld "poundfld"
   put numToChar(110) & numToChar(204) & numToChar(136) into tChars
   replace "#" with tChars in it
   set the unicodeText of fld "result" to uniencode(it,"UTF8")
   delete char 1 to 2 of fld "result"
end mouseUp

Does this work for you?

Thanks for keeping me honest!

Devin




Signe,

You can still do it without one of these methods. Let's take your
case as an example. Say you have a field "poundfield" that
contains your text with # for each n-umlaut. Now create another
field, say field "result", and set its textFont to a unicode font
as in #1 of my first post, below. Now create a button with the
following script:

on mouseUp
  get fld "poundfld"
  replace "#" with "nÃà" in it
  set the unicodeText of fld "result" to uniencode(it,"UTF8")
end mouseUp

Barring any automatic Mac to PC character substitutions (by Rev or
by your mail client,) this should result in the #'s in your
poundfield being replaced by the character you want. If it doesn't
work as posted here, the three characters in the 'with' part of
the replace statement are ASCII-110 ASCII-204 ASCII-136. So you
could generate them reliably by doing this:

on mouseUp
  get fld "poundfld"
  put numToChar(110) & numToChar(204) & numToChar(136) into tChars
  replace "#" with tChars in it
  set the unicodeText of fld "result" to uniencode(it,"UTF8")
end mouseUp



Devin Asay
Humanities Technology and Research Support Center
Brigham Young University

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Umlaut--Success!

2007-03-02 Thread Signe . Sanne
Good morning Devin
I have still got no success (on Mac10.4.8 and Rev 2.6)
The fld "result" is set to "verdana,unicode", but only n appears. Could it be
that I need Rev 2.8?

However, I have not tried your suggested settings with "Enable the Unicode Hex
Input method in the International system prefs under the input tab. This will
cause the Unicode Hex Input method to appear in the input menu (the one with the
little flags on the right side of the menubar.) First because my system is in
Norwegian and I did not find the input menu, and secondly because my potential
users cannot be bothered by doing this. (Or am I completely wrong? Is this
setting in Revolution somewhere?)

Signe Marie

Quoting Devin Asay <[EMAIL PROTECTED]>:

> 
> On Mar 1, 2007, at 10:02 AM, Mark Schonewille wrote:
> 
> > Hi Devin,
> >
> > This doesn't work for me (Mac OS X 10.4.8, Rev 2.7.8).
> >
> > The # is replaced by n instead of n-umlaut.
> 
> Right, after I sent this message, I discovered that the first # in  
> the field does not get replaced by the n-umlaut, only an n. It works  
> for every other # after the first one. (Go figure!) Here's a  
> workaround that worked for me:
> 
> on mouseUp
>get "#"&fld "poundfld"
>put numToChar(110) & numToChar(204) & numToChar(136) into tChars
>replace "#" with tChars in it
>set the unicodeText of fld "result" to uniencode(it,"UTF8")
>delete char 1 to 2 of fld "result"
> end mouseUp
> 
> Does this work for you?
> 
> Thanks for keeping me honest!
> 
> Devin
> 
> >
> >> Signe,
> >>
> >> You can still do it without one of these methods. Let's take your  
> >> case as an example. Say you have a field "poundfield" that  
> >> contains your text with # for each n-umlaut. Now create another  
> >> field, say field "result", and set its textFont to a unicode font  
> >> as in #1 of my first post, below. Now create a button with the  
> >> following script:
> >>
> >> on mouseUp
> >>   get fld "poundfld"
> >>   replace "#" with "nÃà" in it
> >>   set the unicodeText of fld "result" to uniencode(it,"UTF8")
> >> end mouseUp
> >>
> >> Barring any automatic Mac to PC character substitutions (by Rev or  
> >> by your mail client,) this should result in the #'s in your  
> >> poundfield being replaced by the character you want. If it doesn't  
> >> work as posted here, the three characters in the 'with' part of  
> >> the replace statement are ASCII-110 ASCII-204 ASCII-136. So you  
> >> could generate them reliably by doing this:
> >>
> >> on mouseUp
> >>   get fld "poundfld"
> >>   put numToChar(110) & numToChar(204) & numToChar(136) into tChars
> >>   replace "#" with tChars in it
> >>   set the unicodeText of fld "result" to uniencode(it,"UTF8")
> >> end mouseUp
> >>
> >> Hope this saves you from a kludge. ;-)
> >>
> >> Devin
> >>
> >> On Mar 1, 2007, at 1:38 AM, Signe Marie Sanne wrote:
> 
> Devin Asay
> Humanities Technology and Research Support Center
> Brigham Young University
> 
> ___
> use-revolution mailing list
> use-revolution@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
> 


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Umlaut--Success!

2007-03-01 Thread Devin Asay


On Mar 1, 2007, at 10:02 AM, Mark Schonewille wrote:


Hi Devin,

This doesn't work for me (Mac OS X 10.4.8, Rev 2.7.8).

The # is replaced by n instead of n-umlaut.


Right, after I sent this message, I discovered that the first # in  
the field does not get replaced by the n-umlaut, only an n. It works  
for every other # after the first one. (Go figure!) Here's a  
workaround that worked for me:


on mouseUp
  get "#"&fld "poundfld"
  put numToChar(110) & numToChar(204) & numToChar(136) into tChars
  replace "#" with tChars in it
  set the unicodeText of fld "result" to uniencode(it,"UTF8")
  delete char 1 to 2 of fld "result"
end mouseUp

Does this work for you?

Thanks for keeping me honest!

Devin




Signe,

You can still do it without one of these methods. Let's take your  
case as an example. Say you have a field "poundfield" that  
contains your text with # for each n-umlaut. Now create another  
field, say field "result", and set its textFont to a unicode font  
as in #1 of my first post, below. Now create a button with the  
following script:


on mouseUp
  get fld "poundfld"
  replace "#" with "nÃà" in it
  set the unicodeText of fld "result" to uniencode(it,"UTF8")
end mouseUp

Barring any automatic Mac to PC character substitutions (by Rev or  
by your mail client,) this should result in the #'s in your  
poundfield being replaced by the character you want. If it doesn't  
work as posted here, the three characters in the 'with' part of  
the replace statement are ASCII-110 ASCII-204 ASCII-136. So you  
could generate them reliably by doing this:


on mouseUp
  get fld "poundfld"
  put numToChar(110) & numToChar(204) & numToChar(136) into tChars
  replace "#" with tChars in it
  set the unicodeText of fld "result" to uniencode(it,"UTF8")
end mouseUp

Hope this saves you from a kludge. ;-)

Devin

On Mar 1, 2007, at 1:38 AM, Signe Marie Sanne wrote:


Devin Asay
Humanities Technology and Research Support Center
Brigham Young University

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Umlaut--Success!

2007-03-01 Thread Signe . Sanne

Hello Devin,
Nor did it work on Mac 10.4 and Revolution 2.6. I've spent half a day making
images with n+umlaut for textsize 14 and 16 in ordinary colour and in my
selection colour. Thanks all the same.
Signe Marie

> Signe,
> 
> You can still do it without one of these methods. Let's take your  
> case as an example. Say you have a field "poundfield" that contains  
> your text with # for each n-umlaut. Now create another field, say  
> field "result", and set its textFont to a unicode font as in #1 of my  
> first post, below. Now create a button with the following script:
> 
> on mouseUp
>get fld "poundfld"
>replace "#" with "nÃà" in it
>set the unicodeText of fld "result" to uniencode(it,"UTF8")
> end mouseUp
> 
> Barring any automatic Mac to PC character substitutions (by Rev or by  
> your mail client,) this should result in the #'s in your poundfield  
> being replaced by the character you want. If it doesn't work as  
> posted here, the three characters in the 'with' part of the replace  
> statement are ASCII-110 ASCII-204 ASCII-136. So you could generate  
> them reliably by doing this:
> 
> on mouseUp
>get fld "poundfld"
>put numToChar(110) & numToChar(204) & numToChar(136) into tChars
>replace "#" with tChars in it
>set the unicodeText of fld "result" to uniencode(it,"UTF8")
> end mouseUp
> 
> Hope this saves you from a kludge. ;-)
> 
> Devin
> 
> On Mar 1, 2007, at 1:38 AM, Signe Marie Sanne wrote:
> 
> > Hello Devin,
> >
> > I'm afraid none of the methods can be used. I have lots of texts in  
> > which I use "#" for the n with umlaut. These will be fed into  
> > fields on the fly appearing with the correct letter instead of the  
> > "#". So far I have used images for various text sizes which work  
> > reasonably well. My problem arose when I wanted to select a line in  
> > the text, then having to change the colour of the image as well. So  
> > I think I'll stick to the images, just double the sets of images  
> > with selection colours as well.  Thanks for all the help from you  
> > and Mark.
> >
> > Signe Marie Sanne
> >
> > Den 28. feb. 2007 kl. 18:57 skrev Devin Asay:
> >>  You *can* do this in Rev. Here's how I did it in OS X (I'm using  
> >> rev 2.8 in OSX 10.4.8):
> >>
> >> 1. Create a field and set its textfont to a unicode font:
> >>   set the textFont of fld "unistuff" to "Verdana,unicode"
> >>
> >> 2. Enable the Unicode Hex Input method in the International system  
> >> prefs under the input tab. This will cause the Unicode Hex Input  
> >> method to appear in the input menu (the one with the little flags  
> >> on the right side of the menubar.)
> >>
> >> 3. Position the insert cursor in the field, choose Unicode Hex  
> >> Input from the input menu, then type :
> >>   n (then, holding alt/option key down) 0308
> >>
> >>   the n with umlaut should appear.
> >>
> >> Sorry, don't know how to do this via direct input in Windows.  
> >> However, the following should work on either OS:
> >>
> >> 1. Create a UTF-8 encoded text file that includes the desired  
> >> character. I used BBedit, making sure I chose a font that  
> >> supported unicode (Tahoma or Lucida Grande should work) and that  
> >> the document encoding was set to UTF-8, then created the n-umlaut  
> >> character just as I described in #3 above.
> >>
> >> 2. Save the file to disk.
> >>
> >> 3. Read it in to your rev fld using the uniencode() function.
> >>
> >> I've created a stack that shows how to do this.
> >>
> >> go stack url "http://revolution.byu.edu/unicode/testUnicode.rev";
> >>
> >> You may also want to download the utf-8 file from http:// 
> >> revolution.byu.edu/unicode/textUni.ut8. This is the file that the  
> >> sample stack reads from.
> 
> 
> Devin Asay
> Humanities Technology and Research Support Center
> Brigham Young University
> 
> ___
> use-revolution mailing list
> use-revolution@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
> 


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Umlaut--Success!

2007-03-01 Thread Mark Schonewille

Hi Devin,

This doesn't work for me (Mac OS X 10.4.8, Rev 2.7.8).

The # is replaced by n instead of n-umlaut.

Best,

Mark

--

Economy-x-Talk
Consultancy and Software Engineering
http://economy-x-talk.com
http://www.salery.biz

Get your store on-line within minutes with Salery Web Store software.  
Download at http://www.salery.biz


Op 1-mrt-2007, om 16:38 heeft Devin Asay het volgende geschreven:


Signe,

You can still do it without one of these methods. Let's take your  
case as an example. Say you have a field "poundfield" that contains  
your text with # for each n-umlaut. Now create another field, say  
field "result", and set its textFont to a unicode font as in #1 of  
my first post, below. Now create a button with the following script:


on mouseUp
  get fld "poundfld"
  replace "#" with "nÃà" in it
  set the unicodeText of fld "result" to uniencode(it,"UTF8")
end mouseUp

Barring any automatic Mac to PC character substitutions (by Rev or  
by your mail client,) this should result in the #'s in your  
poundfield being replaced by the character you want. If it doesn't  
work as posted here, the three characters in the 'with' part of the  
replace statement are ASCII-110 ASCII-204 ASCII-136. So you could  
generate them reliably by doing this:


on mouseUp
  get fld "poundfld"
  put numToChar(110) & numToChar(204) & numToChar(136) into tChars
  replace "#" with tChars in it
  set the unicodeText of fld "result" to uniencode(it,"UTF8")
end mouseUp

Hope this saves you from a kludge. ;-)

Devin

On Mar 1, 2007, at 1:38 AM, Signe Marie Sanne wrote:


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Umlaut--Success!

2007-03-01 Thread Devin Asay

Signe,

You can still do it without one of these methods. Let's take your  
case as an example. Say you have a field "poundfield" that contains  
your text with # for each n-umlaut. Now create another field, say  
field "result", and set its textFont to a unicode font as in #1 of my  
first post, below. Now create a button with the following script:


on mouseUp
  get fld "poundfld"
  replace "#" with "nÃà" in it
  set the unicodeText of fld "result" to uniencode(it,"UTF8")
end mouseUp

Barring any automatic Mac to PC character substitutions (by Rev or by  
your mail client,) this should result in the #'s in your poundfield  
being replaced by the character you want. If it doesn't work as  
posted here, the three characters in the 'with' part of the replace  
statement are ASCII-110 ASCII-204 ASCII-136. So you could generate  
them reliably by doing this:


on mouseUp
  get fld "poundfld"
  put numToChar(110) & numToChar(204) & numToChar(136) into tChars
  replace "#" with tChars in it
  set the unicodeText of fld "result" to uniencode(it,"UTF8")
end mouseUp

Hope this saves you from a kludge. ;-)

Devin

On Mar 1, 2007, at 1:38 AM, Signe Marie Sanne wrote:


Hello Devin,

I'm afraid none of the methods can be used. I have lots of texts in  
which I use "#" for the n with umlaut. These will be fed into  
fields on the fly appearing with the correct letter instead of the  
"#". So far I have used images for various text sizes which work  
reasonably well. My problem arose when I wanted to select a line in  
the text, then having to change the colour of the image as well. So  
I think I'll stick to the images, just double the sets of images  
with selection colours as well.  Thanks for all the help from you  
and Mark.


Signe Marie Sanne

Den 28. feb. 2007 kl. 18:57 skrev Devin Asay:
 You *can* do this in Rev. Here's how I did it in OS X (I'm using  
rev 2.8 in OSX 10.4.8):


1. Create a field and set its textfont to a unicode font:
  set the textFont of fld "unistuff" to "Verdana,unicode"

2. Enable the Unicode Hex Input method in the International system  
prefs under the input tab. This will cause the Unicode Hex Input  
method to appear in the input menu (the one with the little flags  
on the right side of the menubar.)


3. Position the insert cursor in the field, choose Unicode Hex  
Input from the input menu, then type :

  n (then, holding alt/option key down) 0308

  the n with umlaut should appear.

Sorry, don't know how to do this via direct input in Windows.  
However, the following should work on either OS:


1. Create a UTF-8 encoded text file that includes the desired  
character. I used BBedit, making sure I chose a font that  
supported unicode (Tahoma or Lucida Grande should work) and that  
the document encoding was set to UTF-8, then created the n-umlaut  
character just as I described in #3 above.


2. Save the file to disk.

3. Read it in to your rev fld using the uniencode() function.

I've created a stack that shows how to do this.

go stack url "http://revolution.byu.edu/unicode/testUnicode.rev";

You may also want to download the utf-8 file from http:// 
revolution.byu.edu/unicode/textUni.ut8. This is the file that the  
sample stack reads from.



Devin Asay
Humanities Technology and Research Support Center
Brigham Young University

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Umlaut--Success!

2007-03-01 Thread Signe Marie Sanne

Hello Devin,

I'm afraid none of the methods can be used. I have lots of texts in  
which I use "#" for the n with umlaut. These will be fed into fields  
on the fly appearing with the correct letter instead of the "#". So  
far I have used images for various text sizes which work reasonably  
well. My problem arose when I wanted to select a line in the text,  
then having to change the colour of the image as well. So I think  
I'll stick to the images, just double the sets of images with  
selection colours as well.  Thanks for all the help from you and Mark.


Signe Marie Sanne

Den 28. feb. 2007 kl. 18:57 skrev Devin Asay:
 You *can* do this in Rev. Here's how I did it in OS X (I'm using  
rev 2.8 in OSX 10.4.8):


1. Create a field and set its textfont to a unicode font:
  set the textFont of fld "unistuff" to "Verdana,unicode"

2. Enable the Unicode Hex Input method in the International system  
prefs under the input tab. This will cause the Unicode Hex Input  
method to appear in the input menu (the one with the little flags  
on the right side of the menubar.)


3. Position the insert cursor in the field, choose Unicode Hex  
Input from the input menu, then type :

  n (then, holding alt/option key down) 0308

  the n with umlaut should appear.

Sorry, don't know how to do this via direct input in Windows.  
However, the following should work on either OS:


1. Create a UTF-8 encoded text file that includes the desired  
character. I used BBedit, making sure I chose a font that supported  
unicode (Tahoma or Lucida Grande should work) and that the document  
encoding was set to UTF-8, then created the n-umlaut character just  
as I described in #3 above.


2. Save the file to disk.

3. Read it in to your rev fld using the uniencode() function.

I've created a stack that shows how to do this.

go stack url "http://revolution.byu.edu/unicode/testUnicode.rev";

You may also want to download the utf-8 file from http:// 
revolution.byu.edu/unicode/textUni.ut8. This is the file that the  
sample stack reads from.


HTH

Devin

Devin Asay
Humanities Technology and Research Support Center
Brigham Young University

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your  
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-revolution


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Umlaut--Success!

2007-02-28 Thread Mark Schonewille

Thanks Devin,

I took the data from your file and did a few tests. Eventually, it  
turned out that the following works:


on mouseUp
  put "efff 00e6 3080" into myChars
  replace space with empty in myChars
  put binaryEncode("h*",myChars) into myBin
  set the unicodetext of fld 1 to myBin
  --set the textFont of char 1 to -1 of fld 1 to "Lucida  
Grande,unicode"

end mouseUp

You need a stack with one field and one button to run this script.  
Set the script of the button to the above.


My observations:
- this doesn't work without the signature efff
- setting the font of the characters afterwards is not possible
- it works with both Verdana and Lucida Grande, but you really have  
to set the textFont of the field in advance


Additional remarks:
- above script needs adjustment for Intel machines (both Mac and PC)
- my earlier statement saying that it was not possible is wrong.

Best regards,

Mark

--

Economy-x-Talk
Consultancy and Software Engineering
http://economy-x-talk.com
http://www.salery.biz

Get your store on-line within minutes with Salery Web Store software.  
Download at http://www.salery.biz


Op 28-feb-2007, om 21:53 heeft Devin Asay het volgende geschreven:



On Feb 28, 2007, at 1:21 PM, Mark Schonewille wrote:


Hi Devin,

This is great news. I would like to do a few tests, but can't  
download your utf file. Is the address correct?



I've created a stack that shows how to do this.

go stack url "http://revolution.byu.edu/unicode/testUnicode.rev";

You may also want to download the utf-8 file from http:// 
revolution.byu.edu/unicode/textUni.ut8. This is the file that the  
sample stack reads from.


Sorry, the url for the text file should be http:// 
revolution.byu.edu/unicode/testUni.ut8  (testUni, not textUni).


Devin

Devin Asay
Humanities Technology and Research Support Center
Brigham Young University

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your  
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-revolution


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Umlaut--Success!

2007-02-28 Thread Devin Asay


On Feb 28, 2007, at 1:21 PM, Mark Schonewille wrote:


Hi Devin,

This is great news. I would like to do a few tests, but can't  
download your utf file. Is the address correct?



I've created a stack that shows how to do this.

go stack url "http://revolution.byu.edu/unicode/testUnicode.rev";

You may also want to download the utf-8 file from http:// 
revolution.byu.edu/unicode/textUni.ut8. This is the file that the  
sample stack reads from.


Sorry, the url for the text file should be http://revolution.byu.edu/ 
unicode/testUni.ut8  (testUni, not textUni).


Devin

Devin Asay
Humanities Technology and Research Support Center
Brigham Young University

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Umlaut--Success!

2007-02-28 Thread Mark Schonewille

Hi Devin,

This is great news. I would like to do a few tests, but can't  
download your utf file. Is the address correct?


Mark

--

Economy-x-Talk
Consultancy and Software Engineering
http://economy-x-talk.com
http://www.salery.biz

Get your store on-line within minutes with Salery Web Store software.  
Download at http://www.salery.biz


Op 28-feb-2007, om 18:57 heeft Devin Asay het volgende geschreven:




You *can* do this in Rev. Here's how I did it in OS X (I'm using  
rev 2.8 in OSX 10.4.8):


1. Create a field and set its textfont to a unicode font:
  set the textFont of fld "unistuff" to "Verdana,unicode"

2. Enable the Unicode Hex Input method in the International system  
prefs under the input tab. This will cause the Unicode Hex Input  
method to appear in the input menu (the one with the little flags  
on the right side of the menubar.)


3. Position the insert cursor in the field, choose Unicode Hex  
Input from the input menu, then type :

  n (then, holding alt/option key down) 0308

  the n with umlaut should appear.

Sorry, don't know how to do this via direct input in Windows.  
However, the following should work on either OS:


1. Create a UTF-8 encoded text file that includes the desired  
character. I used BBedit, making sure I chose a font that supported  
unicode (Tahoma or Lucida Grande should work) and that the document  
encoding was set to UTF-8, then created the n-umlaut character just  
as I described in #3 above.


2. Save the file to disk.

3. Read it in to your rev fld using the uniencode() function.

I've created a stack that shows how to do this.

go stack url "http://revolution.byu.edu/unicode/testUnicode.rev";

You may also want to download the utf-8 file from http:// 
revolution.byu.edu/unicode/textUni.ut8. This is the file that the  
sample stack reads from.


HTH

Devin

Devin Asay
Humanities Technology and Research Support Center
Brigham Young University


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Umlaut--Success!

2007-02-28 Thread Devin Asay


On Feb 28, 2007, at 3:03 AM, Signe Marie Sanne wrote:


Hello
Perhaps someone of you may find a better solution to a small  
problem. I need to have the letter n with umlaut (tréma) in a text  
fld set to an ordinary textfont (verdana). So far I have used the  
imagesource, but I would like to know if there is a font (among  
those always present on both Mac and Windows) which will accomplish  
the same.


You *can* do this in Rev. Here's how I did it in OS X (I'm using rev  
2.8 in OSX 10.4.8):


1. Create a field and set its textfont to a unicode font:
  set the textFont of fld "unistuff" to "Verdana,unicode"

2. Enable the Unicode Hex Input method in the International system  
prefs under the input tab. This will cause the Unicode Hex Input  
method to appear in the input menu (the one with the little flags on  
the right side of the menubar.)


3. Position the insert cursor in the field, choose Unicode Hex Input  
from the input menu, then type :

  n (then, holding alt/option key down) 0308

  the n with umlaut should appear.

Sorry, don't know how to do this via direct input in Windows.  
However, the following should work on either OS:


1. Create a UTF-8 encoded text file that includes the desired  
character. I used BBedit, making sure I chose a font that supported  
unicode (Tahoma or Lucida Grande should work) and that the document  
encoding was set to UTF-8, then created the n-umlaut character just  
as I described in #3 above.


2. Save the file to disk.

3. Read it in to your rev fld using the uniencode() function.

I've created a stack that shows how to do this.

go stack url "http://revolution.byu.edu/unicode/testUnicode.rev";

You may also want to download the utf-8 file from http:// 
revolution.byu.edu/unicode/textUni.ut8. This is the file that the  
sample stack reads from.


HTH

Devin

Devin Asay
Humanities Technology and Research Support Center
Brigham Young University

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution