Thank you, Anash! You see, we are building a system that helps people to work with google ads, and we have a site, where we ask users to provide settings they want to see in their ads. So, before even creating an ad, we need to validate descriptions, titles and other stuff to warn users beforehand, as soon as possible, if they are invalid in any way for Google Ads. And yeah, we are using validateOnly=true before we try to create campaigns with ads, but it can be a little bit too late, and if we could warn our users a step earlier, when we ask them to provide settings for ads, it would be really awesome and that's is the problem I am trying to find solution for - to get as much detailed validation rules as possible.
On Thursday, October 22, 2020 at 12:41:45 AM UTC+3 adsapiforumadvisor wrote: > Hi Nadezhda, > > The help center thread is pretty much to the point, except that it doesn't > give you something to work on. > https://en.wikipedia.org/wiki/Halfwidth_and_fullwidth_forms has the > background on double byte system (i.e. it takes twice the width to render > on a monospace console -- so you can render only 40 of these chars on a 80 > column console. Historically, these characters were represented in the > display buffer using two bytes, hence the name "double byte character > system -- (DBCS)", not to be confused with unicode, which is also a > double-byte character system, but has an entirely different meaning.) > > I don't know all the specific char code ranges, but I think that they are > referring to the unicode pages. E.g. Indic block would be from \u0900 to > \u0d7f. Thai would be from \u0e00 to \u0e7f and so on. You could ask the > thread to share the exact unicode pages if you want to get more details. > > My suggestion would be not to focus on the exact char set, because that > would mean that you have to stay in sync with whatever rules might change > in the future, and the exact charsets aren't widely documented as far as I > know. Instead, you could specify validateOnly=true when creating a > MutateAdGroupAdsRequest > <https://developers.google.com/google-ads/api/reference/rpc/v5/MutateAdGroupAdsRequest> > and > let the API do the length validation for you. > > Hope this helps? Let me know if you have more questions. > > Cheers > Anash > > > ref:_00D1U1174p._5004Q26990N:ref > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/3e659984-43ca-4489-8342-d9281d93329cn%40googlegroups.com.
