Re: unicode fraction symbol in a NSTextView

[tridiak]

> On 23/06/2016, at 5:29 AM, Steve Christensen  wrote:
> 
> Where are you specifying the text encoding of the HTML "document" passed to 
> NSMutableAttributedString(HTML:, documentAttributes:)? The default encoding 
> for HTML used to be ISO-8859-1, not UTF-8, for HTML 4 and earlier (and could 
> continue to be interpreted that way by NSAttributedString for compatibility). 
> That could explain the extra character being displayed since the string 
> you're passing as the HTML parameter to NSMutableAttributedString doesn't 
> include, for example, a charset="utf8" meta tag in its  that would 
> specify the desired encoding.
> 
> And, unless you're doing some extra formatting not shown in your code 
> snippet, is there any reason you wouldn't be initializing ats with 
> NSAttributedString(string:s)?
> 

Copied from another project which uses an html document to be inserted into the 
NSTextView.
This project did have a database which did not have an HTML layout field and I 
forgot to change to NSAttributedString(string:s).
Found another DB which has an HTML data field (after I posted the original 
email), so I will drop my hand created version and use that.

I don’t deal with HTML much (besides basic websites) and completely forgot 
about the encoding.

Thanks for all the help. 

> 
>> On Jun 22, 2016, at 9:32 AM, tridiak  wrote:
>> 
>> I am setting some text to a NSTextView which includes the ‘½’ character. 
>> 
>> s = name + “ CR "
>> switch (CR) {
>>  case 0.5:
>>  s=s+”½” // \u{00bd}
>>  case 0.33:
>>  s=s+"⅓"
>>  case 0.25:
>>  s=s+"¼"
>>  case 0.2:
>>  s=s+"⅕"
>>  case 0.17:
>>  s=s+"⅙"
>>  case 0.14:
>>  s=s+"⅐"
>>  case 0.13:
>>  s=s+"⅛"
>>  default:
>>  if CR<1 {s=s+String(format:"%.1f", CR)}
>>  else {s=s+String(format:"%.0f", CR)}
>>  }
>> s=s+"\n”
>> 
>> let d : NSData = s.dataUsingEncoding(NSUTF8StringEncoding)!
>> let ats : NSMutableAttributedString = NSMutableAttributedString(HTML: d, 
>> documentAttributes: nil)!
>> self.blab.textStorage?.setAttributedString(ats)
>> 
>> 
>> What I see is 'Aasimar CR ½’ instead of 'Aasimar CR ½’.
>> Where is the ‘Â' coming from?
>> Is it the font or some swift-obj-C confusion?
> 


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: OK - I must be missing something simple here.

[Alex Zavatone]

On Jun 22, 2016, at 4:01 PM, David Duncan wrote:
> 
> IBOutlet is just  a way to connect to instances created on the storyboard by 
> Interface Builder.

AHA.  And that is my tragic flaw.  I had assumed that it was a way to connect 
instances, not just solely instances that were created in the storyboard.

Thanks.
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: OK - I must be missing something simple here.

[Alex Zavatone]

On Jun 22, 2016, at 1:59 PM, David Duncan wrote:

> 
>> On Jun 22, 2016, at 11:54 AM, Alex Zavatone  wrote:
>> 
>> 
>> On Jun 22, 2016, at 10:51 AM, Alastair Houghton wrote:
>> 
>>> On 22 Jun 2016, at 16:38, Alex Zavatone  wrote:
> 
> Is the thing that you’re missing that IBOutlets are nothing special; 
> they’re just a property (the syntax “IBOutlet” is there just to tell 
> Xcode which things to show in the GUI editor).  So you can set the 
> property, just the same as you would any other property, from code.  Does 
> that help?
 
 I remember reading the docs that IBAction and IBOutlet are mainly 
 conventions for the viewer.
 
 What I am saying is that I DO set the property to be the instance of the 
 button.
 
 And nothing happens.  By that, there is no visual change to the screen.
>>> 
>>> You *are* updating the items property on the UIToolbar, right?  Rather than 
>>> just altering some random IBOutlet and expecting it to magically update the 
>>> toolbar somehow?
>> 
>> Alastair, you're getting confused.  
>> 
>> Why would there be a UIToolbar?  This is just a plain old a UIButton.  
> 
> You started by mentioning that these buttons were being displayed as custom 
> views on a UIBarButtonItem, hence the question.

I'm sorry, David, I thought that I said that they worked under that condition.

What is failing is when I have a UIButton instance (that I know is good, 
because i use that UIButton's instance to create the UIBarButtonItem, but I 
keep the UIButton instance around) and I have an IBOutlet to a UIButton on a 
storyboard scene's viewController.  

This IBOutlet to a UIButton class on the viewController has a 24 x 24 pixel 
dimensions in the viewController in the scene, if it matters.

If I try to set the IBOutlet to one of the UIButton instance, nothing shows up.

If I set the nav bar's right item to the UIBarButtonItem instance, that 
displays fine.

If I have an IBOutlet that is a UIImageView and I set the image property of the 
UImageView to a UIImage instance, that also instantly displays fine.


The only reason I know that the button should display something is because 
that's what I use to initialize the UIBarButtonItem.



Basically, I have a signal strength meter and I'm just interested in swapping 
out the graphics on the fly as the signal value gets updated.

When there is a nav bar on the screen, this graphic needs to be in a 
UIBarButtonItem and the nav bar handles all the placement of where it should go.

But in screens where I have no nav bar, or if the signal strength is to be 
monitored by screens outside of the framework that this is all in, I needed to 
place the element differently.  I tried to use the UIButton instances (not 
UIBarButtonItem) but the contents simply don't display and had to resort to 
UIImages.

Thanks and sorry for the confusion.


> Outlets aren’t magic here – all IBOutlet does is allow you to connect things 
> in a storyboard. If you want to change the value of a property or instance 
> variable backed by an IBOutlet you are free to do so – but you also need to 
> implement all of the other things that might mean.
> 
> That would mean for example that you need to insert the new view and remove 
> the old view from its superview, or reset the custom view on a 
> UIBarButtonItem, or reparent a view controller, or any other thing that might 
> be relevant in the context.
> --
> David Duncan
> 


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: OK - I must be missing something simple here.

[David Duncan]

> On Jun 22, 2016, at 11:54 AM, Alex Zavatone  wrote:
> 
> 
> On Jun 22, 2016, at 10:51 AM, Alastair Houghton wrote:
> 
>> On 22 Jun 2016, at 16:38, Alex Zavatone  wrote:
 
 Is the thing that you’re missing that IBOutlets are nothing special; 
 they’re just a property (the syntax “IBOutlet” is there just to tell Xcode 
 which things to show in the GUI editor).  So you can set the property, 
 just the same as you would any other property, from code.  Does that help?
>>> 
>>> I remember reading the docs that IBAction and IBOutlet are mainly 
>>> conventions for the viewer.
>>> 
>>> What I am saying is that I DO set the property to be the instance of the 
>>> button.
>>> 
>>> And nothing happens.  By that, there is no visual change to the screen.
>> 
>> You *are* updating the items property on the UIToolbar, right?  Rather than 
>> just altering some random IBOutlet and expecting it to magically update the 
>> toolbar somehow?
> 
> Alastair, you're getting confused.  
> 
> Why would there be a UIToolbar?  This is just a plain old a UIButton.  

You started by mentioning that these buttons were being displayed as custom 
views on a UIBarButtonItem, hence the question.

Outlets aren’t magic here – all IBOutlet does is allow you to connect things in 
a storyboard. If you want to change the value of a property or instance 
variable backed by an IBOutlet you are free to do so – but you also need to 
implement all of the other things that might mean.

That would mean for example that you need to insert the new view and remove the 
old view from its superview, or reset the custom view on a UIBarButtonItem, or 
reparent a view controller, or any other thing that might be relevant in the 
context.
--
David Duncan


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: OK - I must be missing something simple here.

[Alex Zavatone]

On Jun 22, 2016, at 10:51 AM, Alastair Houghton wrote:

> On 22 Jun 2016, at 16:38, Alex Zavatone  wrote:
>>> 
>>> Is the thing that you’re missing that IBOutlets are nothing special; 
>>> they’re just a property (the syntax “IBOutlet” is there just to tell Xcode 
>>> which things to show in the GUI editor).  So you can set the property, just 
>>> the same as you would any other property, from code.  Does that help?
>> 
>> I remember reading the docs that IBAction and IBOutlet are mainly 
>> conventions for the viewer.
>> 
>> What I am saying is that I DO set the property to be the instance of the 
>> button.
>> 
>> And nothing happens.  By that, there is no visual change to the screen.
> 
> You *are* updating the items property on the UIToolbar, right?  Rather than 
> just altering some random IBOutlet and expecting it to magically update the 
> toolbar somehow?

Alastair, you're getting confused.  

Why would there be a UIToolbar?  This is just a plain old a UIButton.  
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

unicode fraction symbol in a NSTextView

[Aandi Inston]

Almost certainly not the font itself. Looks like classic mojibake. The
sequence which you seem to report, capital A circumflex, one-half might be
in the encoding ISO-8859-1 (aka Windows-1252 aka informally Latin1).

If so we have
c2 - capital A circumflex
bd - one half

But what is the UTF-8 form of one-half? It is c2bd.  So this seems the
classic case of interpreting UTF-8 as ISO-8859-1. Where that is happening
is for you to find, but my bet is that it is later than you think.

On 22 June 2016 at 17:32, tridiak > wrote:

> I am setting some text to a NSTextView which includes the ‘½’ character.
>
> s = name + “ CR "
> switch (CR) {
> case 0.5:
> s=s+”½” // \u{00bd}
> ...
> let d : NSData = s.dataUsingEncoding(NSUTF8StringEncoding)!
> let ats : NSMutableAttributedString = NSMutableAttributedString(HTML: d,
> documentAttributes: nil)!
> self.blab.textStorage?.setAttributedString(ats)
>
> What I see is 'Aasimar CR ½’ instead of 'Aasimar CR ½’.
> Where is the ‘Â' coming from?
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: unicode fraction symbol in a NSTextView

[Steve Christensen]

Where are you specifying the text encoding of the HTML "document" passed to 
NSMutableAttributedString(HTML:, documentAttributes:)? The default encoding for 
HTML used to be ISO-8859-1, not UTF-8, for HTML 4 and earlier (and could 
continue to be interpreted that way by NSAttributedString for compatibility). 
That could explain the extra character being displayed since the string you're 
passing as the HTML parameter to NSMutableAttributedString doesn't include, for 
example, a charset="utf8" meta tag in its  that would specify the desired 
encoding.

And, unless you're doing some extra formatting not shown in your code snippet, 
is there any reason you wouldn't be initializing ats with 
NSAttributedString(string:s)?


> On Jun 22, 2016, at 9:32 AM, tridiak  wrote:
> 
> I am setting some text to a NSTextView which includes the ‘½’ character. 
> 
> s = name + “ CR "
> switch (CR) {
>   case 0.5:
>   s=s+”½” // \u{00bd}
>   case 0.33:
>   s=s+"⅓"
>   case 0.25:
>   s=s+"¼"
>   case 0.2:
>   s=s+"⅕"
>   case 0.17:
>   s=s+"⅙"
>   case 0.14:
>   s=s+"⅐"
>   case 0.13:
>   s=s+"⅛"
>   default:
>   if CR<1 {s=s+String(format:"%.1f", CR)}
>   else {s=s+String(format:"%.0f", CR)}
>   }
> s=s+"\n”
> 
> let d : NSData = s.dataUsingEncoding(NSUTF8StringEncoding)!
> let ats : NSMutableAttributedString = NSMutableAttributedString(HTML: d, 
> documentAttributes: nil)!
> self.blab.textStorage?.setAttributedString(ats)
> 
> 
> What I see is 'Aasimar CR ½’ instead of 'Aasimar CR ½’.
> Where is the ‘Â' coming from?
> Is it the font or some swift-obj-C confusion?


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: unicode fraction symbol in a NSTextView

[Paul Scott]

Since the symbol is outside the ASCII range and your output encoding is UTF-8, 
that character requires 2 octets. Clearly, whatever application is reading the 
file isn't using UTF-8 encoding. Switch that application to UTF-8 and the 
character will display correctly.

Sent from my iPhone

> On Jun 22, 2016, at 9:32 AM, tridiak  wrote:
> 
> I am setting some text to a NSTextView which includes the ‘½’ character. 
> 
> s = name + “ CR "
> switch (CR) {
>case 0.5:
>s=s+”½” // \u{00bd}
>case 0.33:
>s=s+"⅓"
>case 0.25:
>s=s+"¼"
>case 0.2:
>s=s+"⅕"
>case 0.17:
>s=s+"⅙"
>case 0.14:
>s=s+"⅐"
>case 0.13:
>s=s+"⅛"
>default:
>if CR<1 {s=s+String(format:"%.1f", CR)}
>else {s=s+String(format:"%.0f", CR)}
>}
> s=s+"\n”
> 
> let d : NSData = s.dataUsingEncoding(NSUTF8StringEncoding)!
> let ats : NSMutableAttributedString = NSMutableAttributedString(HTML: d, 
> documentAttributes: nil)!
> self.blab.textStorage?.setAttributedString(ats)
> 
> 
> What I see is 'Aasimar CR ½’ instead of 'Aasimar CR ½’.
> Where is the ‘Â' coming from?
> Is it the font or some swift-obj-C confusion?
> 
> TIA
> 
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
> 
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/pscott%40skycoast.us
> 
> This email sent to psc...@skycoast.us


smime.p7s
Description: S/MIME cryptographic signature
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: unicode fraction symbol in a NSTextView

[Quincey Morris]

On Jun 22, 2016, at 09:32 , tridiak  wrote:
> 
> What I see is 'Aasimar CR ½’ instead of 'Aasimar CR ½’.
> Where is the ‘Â' coming from?

Well, the first thing you need to determine is whether this is the value of ’s’ 
itself, or the result of interpreting ’s’ as HTML.

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

unicode fraction symbol in a NSTextView

[tridiak]

I am setting some text to a NSTextView which includes the ‘½’ character. 

s = name + “ CR "
switch (CR) {
case 0.5:
s=s+”½” // \u{00bd}
case 0.33:
s=s+"⅓"
case 0.25:
s=s+"¼"
case 0.2:
s=s+"⅕"
case 0.17:
s=s+"⅙"
case 0.14:
s=s+"⅐"
case 0.13:
s=s+"⅛"
default:
if CR<1 {s=s+String(format:"%.1f", CR)}
else {s=s+String(format:"%.0f", CR)}
}
s=s+"\n”

let d : NSData = s.dataUsingEncoding(NSUTF8StringEncoding)!
let ats : NSMutableAttributedString = NSMutableAttributedString(HTML: d, 
documentAttributes: nil)!
self.blab.textStorage?.setAttributedString(ats)


What I see is 'Aasimar CR ½’ instead of 'Aasimar CR ½’.
Where is the ‘Â' coming from?
Is it the font or some swift-obj-C confusion?

TIA

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: OK - I must be missing something simple here.

[Alastair Houghton]

On 22 Jun 2016, at 16:38, Alex Zavatone  wrote:
>> 
>> Is the thing that you’re missing that IBOutlets are nothing special; they’re 
>> just a property (the syntax “IBOutlet” is there just to tell Xcode which 
>> things to show in the GUI editor).  So you can set the property, just the 
>> same as you would any other property, from code.  Does that help?
> 
> I remember reading the docs that IBAction and IBOutlet are mainly conventions 
> for the viewer.
> 
> What I am saying is that I DO set the property to be the instance of the 
> button.
> 
> And nothing happens.  By that, there is no visual change to the screen.

You *are* updating the items property on the UIToolbar, right?  Rather than 
just altering some random IBOutlet and expecting it to magically update the 
toolbar somehow?

Kind regards,

Alastair.

--
http://alastairs-place.net


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: OK - I must be missing something simple here.

[Alex Zavatone]

On Jun 22, 2016, at 4:03 AM, Alastair Houghton wrote:

> On 21 Jun 2016, at 18:54, Alex Zavatone  wrote:
> 
>> So, I thought, "well, since I build these UIBarButtonItems from the 
>> UIButtons in the first place, I'll just keep an additional dictionary of 
>> buttons around that then just swap them in and out of an iBOutlet slot in 
>> the storyboard as needed.
>> 
>> Um.  Is this even possible?  Can you assign a UIButton instance that you 
>> have in code to an IBOutlet for a UIButton in the storyboard?   This does 
>> work perfectly for the nav bar's rightButton with barButtonItems, but is 
>> this even possible in code?
>> 
>> I'm missing something here.  Or I'm not.  Any ideas?
> 
> Is the thing that you’re missing that IBOutlets are nothing special; they’re 
> just a property (the syntax “IBOutlet” is there just to tell Xcode which 
> things to show in the GUI editor).  So you can set the property, just the 
> same as you would any other property, from code.  Does that help?

I remember reading the docs that IBAction and IBOutlet are mainly conventions 
for the viewer.

What I am saying is that I DO set the property to be the instance of the button.

And nothing happens.  By that, there is no visual change to the screen.

These buttons are valid 24x24 with graphics, because they display fine with 
used to make a UIBarButtonItem.

I've set the item to redisplay.  Nothing.  

Confusing.  Anyway.  No need to spend time on this now.  I'm using the images 
and it's good enough.  

Thanks.


>> I think I must be a bit dense here, but why not just keep a dictionary of 
>> images and swap the image for the button instead of the button itself?
> 
> That may or may not make more sense, depending.  If the button does something 
> different depending on the state, it might be worth swapping the button (or 
> UIBarButtonItem) instead of just the image, if only because that will help 
> users who are using VoiceOver.  (Hint: when you’re doing this kind of thing, 
> test it with VoiceOver to make sure it’s accessible.)
> 
>> On 21 Jun 2016, at 21:23, Rick Aurbach  wrote:
>> 
>> I agree that I probably wouldn’t put the images directly in the dictionary 
>> either.
> 
> I don’t see why that would be a problem.  You might want to swap out titles 
> as well, mind.
> 
> Kind regards,
> 
> Alastair.
> 
> --
> http://alastairs-place.net
> 


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: OK - I must be missing something simple here.

[Alastair Houghton]

On 21 Jun 2016, at 18:54, Alex Zavatone  wrote:

> So, I thought, "well, since I build these UIBarButtonItems from the UIButtons 
> in the first place, I'll just keep an additional dictionary of buttons around 
> that then just swap them in and out of an iBOutlet slot in the storyboard as 
> needed.
> 
> Um.  Is this even possible?  Can you assign a UIButton instance that you have 
> in code to an IBOutlet for a UIButton in the storyboard?   This does work 
> perfectly for the nav bar's rightButton with barButtonItems, but is this even 
> possible in code?
> 
> I'm missing something here.  Or I'm not.  Any ideas?

Is the thing that you’re missing that IBOutlets are nothing special; they’re 
just a property (the syntax “IBOutlet” is there just to tell Xcode which things 
to show in the GUI editor).  So you can set the property, just the same as you 
would any other property, from code.  Does that help?

> I think I must be a bit dense here, but why not just keep a dictionary of 
> images and swap the image for the button instead of the button itself?

That may or may not make more sense, depending.  If the button does something 
different depending on the state, it might be worth swapping the button (or 
UIBarButtonItem) instead of just the image, if only because that will help 
users who are using VoiceOver.  (Hint: when you’re doing this kind of thing, 
test it with VoiceOver to make sure it’s accessible.)

> On 21 Jun 2016, at 21:23, Rick Aurbach  wrote:
> 
> I agree that I probably wouldn’t put the images directly in the dictionary 
> either.

I don’t see why that would be a problem.  You might want to swap out titles as 
well, mind.

Kind regards,

Alastair.

--
http://alastairs-place.net


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com