My app is called "a Reason to Drink Today." Google rejects to publish due to alleged incorrect rating due to references to alcohol (the word "to drink"). They ask me to go through questionnaire again on the age rating (content rating). What item in that section is related to the mention of alcohol and how do I publish?
Email from Google Play
My age rating settings (interface in Russian)
Your app should be Adult rating, but you have choose any age, Before uploading app again
In store listing > app content > make it 18+
and in Content rating : example like this
Related
I'm generating some vCards for employees in my company which will be served over the web. Most of the individuals are licensed professionals. I would like to include their accreditation, associations, license numbers, etc... in their vCards.
I've been using RFC6350 and its examples as a guide. There is a specific example in sec 6.2.2 that pretty much what I want. According to the RFC's special note, the 4th and 5th elements should contain honorific prefix and suffix. I'm not sure my desired usage fits this description, however in their example, it is used in this way.
Example from RFC: N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P.
The problem I'm having:
When the vCard is imported into Outlook, Outlook seems to parse the N: field to populate its internal fields:
N:{last name};{first name};{middle names};{prefix};{suffix}
When I look at the contact properties the suffix is actually being stored as the "Generation" Property.
After saving the vCard, Outlook seems to calculate the "Display as" property by combining {first name} {middle name} {last name} {generation}, which potentially creates excessively long "display as" names. So, using the RFC's example, Outlook will generate an email addressed to "John Philip,Paul Stevenson Jr.,M.D.,A.C.P. (test#example.com)" <test#example.com>. In my case: "Example User, AIA, NCARB, SEI, LEED GREEN ASSOCIATE(test#example.com)" <test#example.com>
My question is: Is there a more appropriate vCard field to store credentials that I am missing, which will not pollute Outlook's display as field OR is there a way to supply a custom "Display as" property in the .vcf that Outlook will pick up on?
I'm testing in Outlook 2016
I have used google to obtain an address from a postcode and the like before. My problem is I want my website to have address fields such that anyone in any country can sign up properly and provide all necessary address information. I will include a feature to enter postcode and obtain all other information automatically.
Is it reasonable for me to check the postcode and force a successful google lookup before someone signs up? If so I could just store the JSON string in the database as a blob or maybe inside a class. But I still need to decide what fields, such as street name, postcode or zip, and the like to include. I'm not sure where to begin deciding what to include?
I think what I'm really asking, is what fields are associated with what google fields in general. I know the different administrative levels are different things in different countries :/
While I can't say what you should specifically do for Google, I can tell you what fields our customers use when they validate international addresses online. (Full Disclosure: I'm a programmer at SmartyStreets where we validate international addresses.)
While each country's mailing system is unique, there are a few major similarities that they all share. This element of commonality is what allows you to have people enter their address into a universal form and then validate the address, regardless of the country in question.
Address Line 1: This field is usually the house or building number and the street which the building is located. Examples of this field include: 123 Main Street, Calle Proc. San Sebastián, 15, 1019 North 1300 West, etc.
Address Line 2: This field would include apartment or suite numbers.
Locality: The most common data entered for this is the city component of the address. For example: Paris, Hamburg, Johannesburg, etc.
Administrative Area: This is the state or province name or abbreviation. Examples of this would be Texas - TX, Alberta - AB, Firenze (Italy) - FI.
Postal Code (where available): Examples of this would be 90210 (Beverly Hills in California) or 84000 (Avingon in France).
While you can always add additional fields to give additional context to a software parser or interpreter, the above fields are the most common ones that you would use for international address validation. If you're not sure, you can test a non-US address for free. We offer extensive documentation that is both free and publicly visible to help better explain the nuances and idiosyncrasies of street and mailing addresses.
I was trying to build a graph connecting actors using the movies they have worked for using IMDB ftp data.
However I only wanted to use movies (title type :- Feature Films) as connections.
I downloaded the ftp data from IMDB. However I was not able extract the title type from the files. I wanted to know if any body has tried to sort the ftp data provided by IMDB based on title type and how did they differentiate.
The title itself will tell you what kind of show you're dealing with.
If it ends with "(TV)" it's a TV movie (a single episode, produced for TV).
If it ends with "(V)" it's a video movie (straight to video).
If it's surrounded by quotes and ends with "(mini)" it's a tv mini series. (NOTE: I think that this category is no longer present, in the plain text data file).
If it's only surrounded by quotes, it's a tv series.
If the title is surrounded by quotes and ends with another titles enclosed in curly brackets, it's an episode of a tv (mini or not) series (inside the brackets there's the title of the episode - if known - or the #seasonNR.episodeNR or the air date).
anything else, is a movie.
A special case are tv series episodes marked with {{SUSPENDED}}, which means that the episode was never produced, but it was planned and maybe it will be done in the future.
Notice that these rules apply only to the plain text data files that you can download from the FTP servers. Since some years, on the web site a different of rules are followed.
I've done a lot of research on the subject, being the main author of IMDbPY (by the way: give it a look, since it may be useful to you to import these information into a SQL db).
I am working as search engine optimizer team lead in a company and facing problem in a project which name is http://www.Prooftech.com.sg...
Problem :-
The Website has 10 keywords for which my client wanted the top 10 Ranking in Yahoo Singapore search engine.
I have got top 10 ranking for the following 7 keywords Waterproofing, RC Roof ,Wall Leakages ,Ceiling Leakages , Water Leakages ,Roof Tile Coating ,Roof Tiles Repair in my 3 months work but still i am not getting the listing positions for Roof ,Concrete Repair ,Grouting ....
I have Done lot of Bookmarking ,Blog Commenting ,Blog Creations ,Press Release,Classified Ads to get these 3 keywords in listing but there is no changes in the results....
Can any help me out from this problem so i can get Good rankings for Roof ,Concrete Repair ,Grouting
Try :
More content in the lexical field of your keywords,
Some dedicated landing page on your keyword,
More diverse anchor for your out and inlink,
More outlink from social network (viral operation, videos link...),
More regular outlink (not just a blast one day...),
Pay some influent blogger on your lexical field to write a really good article,
Play with some Black/GreyHat linking tools like Xrumer/Zennoposter/Scrapebox/SenukeX
...
I am trying to create an automatic feed generation for data to be sent to Google Base using utf-8 encoding.
However I am getting errors whenever hyphens are found telling me that there is an encoding error in the relevant attribute (title, description, product_type). I am currently using:
−
but I have also tried:
−
neither of which have worked.
I am using the following declaration at the top of the document:
<?xml version="1.0" encoding="utf-8"?>
Ok to give further context to this the data is being pulled from our site's product information stored as utf-8 encoded data in a MYSQL database. The data is going into an RSS 2.0 feed, using the some standard RSS attributes as well as some custom defined Google attributes. The problem comes up whenever there is a hyphen in any field except the link field. So it is appearing in the title and description fields as well as the custom product_type field. Below is an example of a field that Google Base (merchant centre) throws an error over. It throws the same error with or without the other entities and only stops objecting when hyphens are removed.
<description><p>Your sports floor is designed primarily for sports use. Thou many facilities have to be used for other activities including things like; assemblies careers fairs drama parties and social events bring and buy sales exhibitions etc.</p>
<p>Solid hardwood sports floors are designated as "area elastic floors" to provide the spring resilience and shock absorbing qualities needed for sports and dance use to minimise injury. If the floor is too hard the athlete and user will be exposed to early fatigue and aching joints through to injury such as sprains joint and shin bone damage.</p>
<p>If too soft then ball bounce and running characteristics are compromised.
In the UK hardwood sports floors are governed by a number of recognised standards</p>
<p>All sports floors must conform to BS7044 Part 4 - this is the minimum Sport England requirement with which your floor msut comply if it is part of a Sport England sponsored project.</p>
<p>A higher more demanding standard for better quality sports and dance flooring is DIN 18032 Part 2</p>
<p>The newest - and the best - standard is the European Standard CEN 217. This standard has brought together all the best eprformance criteria from a number of current standards in the EU including BS and DIN.</p>
<p>All Junckers systems fully comply with one or more of these standards. They ALL comply with the minimum Sport England requirement of BS7044 Part 4 compliance.</p></description>
You talk about using hyphens, but the character you're trying to insert is the mathematical minus sign. Have you tried it with an actual hyphen? And not a HTML entity, either; just the character, -.